request for proposal (rfp) up gradation of scada & dms ... · pdf filenit:...

NIT: CMC/BY/12-13/RB/VKS/063 of 12 Bidders seal & signature

Request for Proposal (RFP)

Up gradation of SCADA & DMS Software system

INVITATION TO BIDS

Reference Number: CMC/BY/12-13/RB/VKS/063Dated: 07/12/2012

Head, C & M Dept.BSES Yamuna Power Limited

Corp. Office: BSES Bhawan, Karkardooma,New Delhi – 110032


SECTION – I: REQUEST FOR QUOTATION

1.00 Event Information

BYPL invites sealed tenders for Up gradation of SCADA & DMS Software system.The bidder must qualify the technical requirements as specified in clause 2.0 stated below.The sealed envelopes shall be duly super scribed as — “BID FOR Up gradation of SCADA &DMS Software system TENDER NOTICE CMC/BY/12-13/RB/VKS/063. DUE FORSUBMISSION ON DT: 20.12.2012.

The schedule of specifications with detail terms & conditions can be obtained from address givenbelow against demand draft/Pay Order of Rs.1000- drawn in favour of BYPL, payable at Delhi.The sale of tender documents will be issued from 19.12.2012 onwards on all working days upto20.12.2012. The tender documents can also be downloaded from the website“www.bsesdelhi.com”. However, it is advisable to inform BYPL about your interest in tender.In case tender papers are downloaded from the above website, then the bidder has to enclose ademand draft covering the cost of bid documents as stated above in a separate envelope withsuitable superscription —“Cost of Bid Documents: Tender Notice Ref:CMC/BY/12-13/RB/VKS/063.This envelope should accompany the Bid Documents.

1.01 Offers will be received at 1400 Hrs on dt.20.12.2012 as indicated earlier will be opened on thesame day at the address given below on 20.12.2012 at 1500 Hrs in the presence of authorizedrepresentatives of the bidders.. The schedule of specifications with detail terms & conditionsare enclosed. It is the sole responsibility of the bidder to ensure that the bid documents reachthis office on or before the due date.

HEAD OF THE DEPARTMENT,3rd FLOOR, ‘A’ BLOCK,

CONTRACTS & MATERIALS DEPARTMENT,BSES YAMUNA POWER LTD,SHAKTI KIRAN BUILDING,

KARKARDOOM, NEW DELHI

1.04 BYPL reserves the right to accept/reject any or all Tenders without assigning any reasonthereof and alter the quantity of materials mentioned in the Tender documents at thetime of placing purchase orders. Tender will be summarily rejected if:

(i). Earnest Money Deposit (EMD) @ 2% (Two percent) of the Tender value i.e. Rs 72,000 isdeposited in shape of bank Draft in favour of BSES YAMUNA POWER LTD, payable atDelhi or Bank Guarantee executed on favour of BSES YAMUNA POWER LTD.

(ii). The offer does not contain “FOR, NEW DELHI price indicating break-up towards alltaxes & duties“.(iii). Complete Technical details are not enclosed.(iv). Sample is not submitted along with the offer.(v). Tender is received after due time due to any reason.

3.00Bidding and Award Process

Bidders are requested to submit their questions regarding the RFQ or the bidding processafter review of this RFQ. BYPL response to the questions raised by various bidders will


be distributed to all participating bidders through an RFQ Update. Otherwise BYPL willorganize a prebid meeting to clarify all doubts on dated 20.12.2012 at 1400 Hrs.

a. Time schedule of the bidding processThe bidders on this RFQ package should complete the following within the datesspecified as under:

S. No. Steps Activity description Due date

1 TechnicalQueries All Queries related to RFQ On or before

Pre-bid meeting

2 TechnicalOffer

It includes all details mentioned in technicalspecification.

20.12.2012, 1400Hrs

3 CommercialOfficer

Price for items required in price format. Break up regarding basic price and taxes. Delivery commitment

20.12.2012, 1400Hrs -

This is a two part bid process. Bidders are to submit the bids a) Technical Bid b) PriceBid.Both these parts should be furnished in separate sealed covers superscribing specificationno. validity etc, with particulars as Part-I Technical Particulars & Commercial Terms &Conditions and Part-II “Financial bid“ and these sealed envelopes should again beplaced in another sealed cover which shall be submitted before the due date & timespecified.

The Part – I Eligibility and Technical Bid should not contain any cost informationwhatsoever.In case of Bids where the qualification requirements, technical suitability and otherrequirements are found to be inadequate, Part-II ”Financial Bid‘ will be returnedunopened.

b). Qualified bidders will be intimated after technical evaluation of all the bids iscompleted.

Not withstanding anything stated above, the Purchaser reserves the right to assessbidders capability to perform the contract, should the circumstances warrant suchassessment in the overall interest of the purchaser. In this regard the decision of thepurchaser is final.

4.00Award DecisionPurchaser intends to award the business on a lowest bid basis, so suppliers areencouraged to bid competitively. The decision to place purchase order / letter ofacceptance solely depends on purchaser on the cost competitiveness across multiple lots,quality, delivery and bidder‘s capacity, in addition to other factors that Purchaser maydeem relevant.

The purchaser reserves all the rights to award the contract to one or more bidders so asto meet the delivery requirement or nullify the award decision without any

reason.

In the event of your bid being selected by purchaser (and / or its affiliates) and yoursubsequent DEFAULT on your bid; you will be required to pay purchaser (and / or itsaffiliates) an amount equal to the difference in your bid and the next lowest bid on thequantity declared in RFQ.


In case any supplier is found unsatisfactory during the delivery process, the award willbe cancelled and BYPL reserves the right to award other suppliers who are found fit.

5.00Market IntegrityWe have a fair and competitive marketplace. The rules for bidders are outlined in theTerms & Conditions. Bidders must agree to these rules prior to participating. In additionto other remedies available, we reserves the right to exclude a bidder from participatingin future markets due to the bidder’s violation of any of the rules or obligationscontained in the Terms & Condition. A bidder who violates the marketplace rules orengages in behavior that disrupts the fair execution of the marketplace restricts a bidderto length of time, depending upon the seriousness of the violation. Examples ofviolations include, but are not limited to: Failure to honor prices submitted to the marketplace. Breach of the terms of the published in Request for Quotation.

6.00Supplier ConfidentialityAll information contained in this RFQ is confidential and may not be disclosed, published oradvertised in any manner without written authorization from BYPL. This includes all biddinginformation submitted.

All RFQ documents remain the property of BYPL and all suppliers are required to returnthese documents to BYPL upon request.

Suppliers who do not honor these confidentiality provisions will be excluded fromparticipating in future bidding events.

7.0 Contact InformationAll communication as regards this RFQ shall be made (i) in English, (ii) in writing and(iii) sent by mail, facsimile to

Technical CommercialContact Name Harsh Sharma Rakesh Bansal

Address1st Floor, A Block, Shakti KiranBuilding, Karkardooma, Delhi-

32

3rd Floor, A Block, Shakti KiranBuilding, Karkardooma, Delhi-32

Fax No. 011-39999060 011-39999230Email Id [email protected] [email protected]

Note:- Those who are downloading tender notice from website. It is advisable toinform BYPL Technical, so as they can be contacted in case of any amendmentin tender or for prebid conference.


BSES Yamuna Power LimitedCorp. Office: BSES Bhawan, Karkardooma,

New Delhi – 110032

S. No. Details of Tender Documents1. General Purchase Conditions (Section - GPC) Annexure I2. Instruction to Bidders (Section – INB) Annexure II3. Detailed Technical Specifications (Section – DTS) Annexure III4. Specifications for required Software Annexure IV5. Format for Bid Form/PBG Annexure V6. Format for Price Bid Annexure VI7 Commercial Terms and Condition Annexure VII8 No Deviation Sheet (Deviation in Technical) Annexure VIII9 Qualifying Requirement Data Annexure IX

In case you are interested, please submit your competitive offer duly supported with all theabove documents mentioned at S.No. 1 to 6 duly signed in each & every page along with relevantAppendix in a sealed envelope marked as “Part A -Technical Bid” (As per Annexure I to V ) andAnnexure VI – Format for Quoting Rates (Price Bid) (S.No.6) to be kept in a separate envelopemarked as “Part B - Price Bid”.Both the envelopes (A&B) Technical & Price Bids shall be put in a bigger envelope. The biggerenvelope should be sealed and super scribed as “Up gradation of SCADA & DMS Softwaresystem” - Due on 20/12/2012 at 1400 hrs.


ANNEXURE – I

SECTION GPC(GENERAL PURCHASE CONDITIONS)

1 SUBMISSION OF BIDS

1.1 The bid shall be typed or written in indelible ink and shall be signed by the Bidder or aperson or persons duly authorized to bind the Bidder to the Contract. All pages of thebid, except for un-amended printed literature, shall be initialed by the person orpersons signing the bid.

1.2 The bid shall contain no interlineations, erasures or overwriting except as necessary tocorrect errors made by the Bidder, in which case such corrections shall be initialed bythe person or persons signing the bid.

1.3 The bidders are required to submit the bids in two parts consisting of Part A: TechnicalBid and Part B: Price Bid in separate sealed envelopes and both the sealed envelopesduly super scribed as "Part A: Technical Bid" and" Part B: Price Bid" are to be sealed ina bigger envelope.

1.4 The envelope marked as Part A and Part B should contain following documents :Part A: Technical Bid

Should contain Annexure I to V, relevant Appendix

Part B: Price Bid should contain only the Price Bid filled in Annexure VI.

1.5 The bigger envelope containing Part A & Part B bids should be super scribed as “Upgradation of SCADA & DMS Software system - Due on 20/12/2012 at 1400 Hrs.” andto be addressed to:

Head of DepartmentContracts and Material,

BSES Yamuna Power Ltd.3rd Floor, ‘A‘ Block, BSES Bhawan,

Karkardooma, Delhi – 110 032

2 SIGNATURE OF BIDS

2.1 The bid must contain the name and place of business of the person or persons makingthe bid and must be signed and sealed by the Bidder with his usual signature.

2.2 Satisfactory evidence of authority of the person signing on behalf of the Bidder shall befurnished with the bid.


2.3 The Bidder’s name stated on the proposal shall be the exact legal name of the firm.

3 SEALING AND MARKING OF BIDS

3.1 The bids are to be sealed as described in Clause 1.3 & 1.4 above.

3.2 The bids send by Regd. Post should bear the name of Tender, the reference number,and the words “DO NOT OPEN BEFORE 20/12/2012”.

3.3 The envelope shall indicate the name and address of the Bidder to enable the bid to bereturned unopened in case it is declared “late” or “rejected”.

3.4 If the outer envelope is not sealed and marked as per above, the Owner will assume noresponsibility for the bid’s misplacement or premature opening.

4 DEADLINE FOR SUBMISSION OF BIDS

4.1 The Bidders have the option of sending the bid by registered post or submitting the bidin person. Bids submitted by fax/telegram will not be accepted. No request from anyBidder to the Owner to collect the proposal from airlines, cargo agents etc. shall beentertained by the Owner.

4.2 Bids must be received by the Owner at the address specified above, not later than thetime & date mentioned in the Invitation to Bid.

4.3 The Owner may, at its discretion, extend this deadline for the submission of bids byamending the Invitation to Bid, in which case all rights and obligations of the Ownerand Bidders previously subject to the deadline will thereafter be subject to the deadlineas extended.

5 LATE BIDS

5.1 Any bid received by the Owner after the time & date fixed or extended for submissionof bids prescribed by the Owner, will be rejected and/or returned unopened to theBidder.

6 MODIFICATION AND WITHDRAWAL OF BIDS

6.1 The Bidder may modify or withdraw its bid after the bid’s submission provided thatwritten notice of the modification or withdrawal is received by the Owner prior to thedeadline prescribed for submission of bids.

6.2 The Bidder’s modifications or withdrawal notice shall be prepared, sealed, marked anddispatched in accordance with the provisions of Clause Sealing and Marking of Bidsabove.

6.3 No bid may be modified subsequent to the deadline for submission of bids.

6.4 No bid may be withdrawn in the interval between the deadline for submission of bidsand the expiration of the period of bid validity specified by the Bidder on the Bid Form.Withdrawal/modification of a bid during this interval may result in the forfeiture ofbid security.


6.5 Oral statements made by the Bidder at any time regarding quality, quantity orarrangement of the equipment or any other matter will not be considered.

7 OPENING OF BIDS BY THE OWNER

7.1 The Bids shall be opened by the Owner on any date after the last date fixed for Bidreceipt as specified in Invitation of Bids or in the case any extension has been giventhereto, after the extended Bid submission date notified to all Bidders.

7.2 No electronic recording devices will be permitted during bid opening.

7.3 Technical Bids will be opened in the presence of the bidders’ representatives whochoose to attend on the specified date and time. Price Bids of technically qualifiedbidders will be opened in the presence of the bidders’ representatives on a separatedate and time which will be intimated separately.

7.4 No further discussion/ interface will be granted to bidders whose bids have beendisqualified. BSES reserves the right to accept or reject in part or full any or all theoffers without assigning any reason whatsoever.

8 CLARIFICATION OF BIDS

8.1 To assist in the examination, evaluation and comparison of bids the Owner may, at itsdiscretion, ask the Bidder for clarification of its bid details. The request for clarificationand the response shall be in writing and no change in the price or substance of the bidshall be sought, offered or permitted.

9 PRELIMINARY EXAMINATION

9.1 The Owner will examine the bids to determine whether they are complete, whetherany computational errors have been made, whether required sureties have beenfurnished, whether the documents have been properly signed, and whether the bidsare generally in order.

9.2 Arithmetical errors will be rectified on the following basis: If there is a discrepancybetween the unit price and the total price that is obtained by multiplying the unit priceand quantity, the unit price shall prevail and total price shall be corrected. If there is adiscrepancy between words and figures, the amount in words will prevail. If theBidder does not accept the correction of the errors as above, his Bid will be rejected

10 PRICE

10.1 The Bidder shall quote Firm prices valid till the complete execution of the order.

10.2 The Bidder shall quote on FOR Destination basis inclusive of packing, forwarding,freight, insurance charges, taxes & duties etc, if any. The Bidder shall quote item wiseunit and lot prices for all the material.

11 TAXES AND DUTIES

11.1 All the Bidders are requested to familiarize themselves with the laws, rules andregulations prevailing in India and consider the same while developing and submittingtheir Proposal.


11.2 All Customs duties, Excise Duties, Sales Tax and other levies payable by the bidder ongoods, equipments, components, Sub-assemblies, raw materials & any other items usedfor their consumption or dispatched directly to owner by the contractor or their sub-suppliers shall be included in the bid price & any such taxes, duties, levies additionallypayable will be to bidder’s account & no separate claim on this account will beentertained by the owner.

11.3 If any rates of taxes/duties/levies (hereinafter called ‘Tax’) are increased or decreased,a new Tax is introduced, an existing Tax is abolished or any change in interpretation orapplication of any Tax occurs in the course of the performance of Contract, which wasor will be assessed on the Contractor in connection with performance of the Contract,an equitable adjustment of the Contract Price shall be made to fully take in to accountany such change by addition to the Contract Price or deduction there from, as the casemay be.

12 INSURANCE

12.1 The seller at his cost shall arrange, secure and maintain all insurance as may bepertinent and obligatory in terms of law to protect his interest and interests of theOwner against all perils. The responsibility to maintain adequate insurance coverage atall times till the equipment/materials “Taken Over‟ by the Owner shall be of Selleralone.

13 BID CURRENCIES

13.1 Prices shall be quoted in Indian Rupees only.

14 MODIFICATION AND WITHDRAWAL OF BIDS

14.1 The Bidder’s modification or notice of withdrawal shall be prepared, sealed, markedand delivered with the outer envelopes additionally marked ‘MODIFICATION’ or‘WITHDRAWAL’ as appropriate.

15 PERIOD OF VALIDITY OF BIDS15.1 Bids shall remain valid and open for acceptance for a period of 120 days after the date set

for Bid opening.

16 Performance Guarantee

16.01 Supplier shall establish a performance bond in favor of BYPL in an amount not less thanTen percent (10%) of the total price of the Contract (the "Performance Bond"). The PerformanceBond shall be valid for a period of Twelve month (12) from the date of the commissioning oreighteen months (18) from the date of receipt of material (last consignment) at site/stores whichever is earlier plus 3 months towards claim period. It shall be in accordance with one of thefollowing terms:

a Depositing pay order /demand draft of the relevant amount directly with BYPL at theaddress listed above or as otherwise specified by BYPL, either of which shall constitute thePerformance Bond hereunder; or(b) Bank guarantee from any nationalized bank in favour of BYPL. The performance Bankguarantee shall be in the format as specified by BYPL

16 PROCESS TO BE CONFIDENTIAL


16.1 Any effort by a bidder to influence the Purchaser in the process of examination,clarification, evaluation and comparison of Bids, and in decisions concerning the awardof Contract, may result in the rejection of his Bid.

17 TIME SCHEDULE

17.1 The basic consideration and the essence of the Contract shall be the strict adherence tothe time schedule specified in the bidding documents and incorporated in the Contractfor supplies and services.

18 EVALUATION AND COMPARISION OF BIDS

18.1 Bidder shall state their Bid price with the payment schedules outlined in thespecifications. Bids will be evaluated on the basis of this base price.

18.2 The purchaser reserves the right to accept or reject any variation, deviations oralternative offered. Variations, deviations, alternative offers and other factors which arein excess of the requirements of the bidding documents or otherwise result in theaccrual of unsolicited benefits to the Purchaser shall not be taken into account in Bidevaluation.

19 DELIVERY/SHIPMENT TERMS

19.1 All the equipment/materials shall be dispatched to destination on FOR destinationbasis within the delivery period as stipulated in the Purchase Order/LOA.

19.2 The software shall be delivered, installed and commissioned in full at the site withinone month from the date of order/LOI. Thereafter the hardware shall be handed overto the owner as per the relevant clauses above. Partial delivery and installation, ifnecessary shall be allowed only with prior approval of the owner.

20 PAYMENT TERMS

20.1 100% of the ex-works price, plus packing, forwarding, freight and insurance charges,taxes and duties shall be payable to the supplier, for the indigenous equipment, within90 days of receipt, installation, testing, commissioning and Taking Over theequipments/materials at the desired premises of the consignee in satisfactory workingcondition. The payment will be released only after verification of the bill by theIndenting Unit.

21 LOCAL CONDITIONS

21.1 It will be imperative on each bidder to fully inform himself of all local conditions andfactors which may have any effect on the performance of the Contract covered underthese specifications and documents.

22 LIQUIDATED DAMAGES FOR DELAY IN COMPLETION

22.1 The date stipulated for delivery of GOODS shall be the essence of PURCHASEORDER.

22.2 In the event the supply/service is delayed beyond schedule, we shall levy penalty of 1%( One percent) of the basic value (ex-works value) of undelivered units per week of


delay or part thereof, subject to maximum of (TEN) 10% of the total basic value (ex-works value) of undelivered units.

22.3 BUYER may, without prejudice to any method of recovery, deduct the above amountfrom, any sum due or which may become due to the SELLER in this or any othercontract or from the Performance Bond or file a claim against the SELLER

23 SUB-LETTING

The Vendor shall not sub-let, transfer or assign any part of this order without the priorwritten consent of the Purchaser. Copies of sub-contract order shall be forwarded to thePurchaser.

24 CANCELLATION

The Owner reserves the right to cancel the order in part or in full by giving one week advancenotice thereby if:

a) The Vendor fails to comply with any of the terms of the order.

b) The Vendor becomes bankrupt or goes into liquidation.

c) The Vendor makes general assignment for the benefit of the creditors; and

d) Any receiver is appointed for the property owned by the Vendor.

25 LAW AND PROCEDURE

25.1 Applicable Law

The law which is to apply to the Contract and under which the Contract is to beconstructed shall be Indian Law. The Courts of Delhi shall have exclusive jurisdictionin all the matters arising in the Contract including execution of Arbitration Award.

25.2 ACCEPTANCE OF TERMS AND CONDITIONS

The Bidder must confirm his acceptance of the terms and conditions mentionedhereinabove and the enclosed documents. In case any clause is not acceptable to theBidder, the same should be specifically brought out in deviation schedule given in theBid Proposal Sheets with categorical confirmation that all other clauses are acceptableto the Bidder. If no mention is made in this regard, it shall be presumed that all clausesmentioned hereinabove are acceptable to the Bidder.


ANNEXURE – II

INSTRUCTION TO BIDDERS

1 GENERAL INSTRUCTIONS

1.1 BSES (hereinafter called Owner) invites Bids in respect of Supply of Up gradation ofSCADA & DMS Software system at Regd. Office at BSES Yamuna Power Ltd., BSESBhawan, Karkardooma, Delhi – 100 032 All Bids shall be prepared and submittedstrictly in accordance with these instructions

1.2 The Owner reserves the right to itself to accept any Bid or reject any or all Bids orcancel/ withdraw Invitation to Bid without assigning any reason for such decisions.Such decisions by the Owner shall bear no liability whatsoever consequent upon such adecision.

2 QUALIFYING REQUIREMENTS FOR BIDDERS

2.1 The Bidding is open to all qualified Bidders who fully meet the following qualifyingrequirements:

I. Yearly turnover is approx.1000 Crores in last financial year.

II. Bidder must have executed at least 3 (three) orders for similar work with total value ofRs. 1.5 Crs.

III. Three successfully implementation of SCADA in last 10 years.

IV. Bidder should have valid Registration No. of Sales Tax/VAT/Service Tax, whichever isapplicable;

V. Bidder should have PAN No. & should fulfill all statutory compliances.

VI. Owner reserves the right to carry out capability assessment of the Bidders and Owner'sdecision shall be final in this regard;

The bidder shall submit all necessary documentary evidence to establish that theBidder meets the above qualifying requirements.

3 COST OF BIDDING

All the costs and expenses incidental to preparation and submission of the proposals,discussions including pre-award discussions with the successful Bidder etc. shall be to theaccount of the Bidders and the Owner shall not be responsible in any way whatsoever, andshall bear no liability whatsoever, on such costs and expenses, regardless of the conduct oroutcome of the Bidding process.

Upgradationof SCADA &DMSsystem(Software)BSES Yamuna PowerLimited

2

TABLE OF CONTENTS

1 BSES OVERVIEW .....................................................................................................................................6

2 EXISTING SYSTEM DETAILS ......................................................................................................................7

2.1 OVERVIEW OF THE EXISTING SYSTEM .............................................................................................................72.3 EXISTING SYSTEM ARCHITECTURE:................................................................................................................92.3.1 MAIN & BACK-UP CONTROL CENTRE AT BALAJI & NEHRU PLACE.............................................................................. 92.4 EXISTING SERVERS & WORKSTATIONS AT BCC ..............................................................................................102.5 IO SIZING PARAMETERS...........................................................................................................................132.6 COMMUNICATION PROTOCOLS USED...........................................................................................................132.7 TIME SYNCHRONIZATION..........................................................................................................................132.8 EXISTING DISPLAY DESIGNS (EXISTING DISPLAY DESIGNS SHALL BE RETAINED ) .......................................................172.9 EXISTING NAMING CONVENTIONS (EXISTING NAMING CONVENTIONS SHALL BE RETAINED AS IT IS) ............................182.9.1 TEXT STRUCTURE............................................................................................................................................ 18

3 RFP REQUIREMENT ...............................................................................................................................18

3.1 SCOPE OF WORK ...............................................................................................................................19

3.2 CONTROL ARCHITECTURE OF SCADA/DMS (NEW UPGRADED SYSTEM) ..............................................................193.2.1 MULTI SITE ARCHITECTURE AND PROVISION FOR FUTURE INTEGRATION WITH MCC-1 ................................................ 20

4 PROPOSED SYSTEM CONFIGURATION: SOFTWARE, HARDWARE AND USER INTERFACE ..........................21

4.1 SOFTWARE STANDARDS ...........................................................................................................................214.2 DESIGN AND CODING STANDARDS FOR SCADA/DMS APPLICATIONS .................................................................214.3OPERATING SYSTEM ................................................................................................................................224.4 USER INTERFACE REQUIREMENTS ...............................................................................................................224.4.1 FUNCTION AND DATA ACCESS SECURITY ............................................................................................................. 224.4.2 WINDOWS ENVIRONMENT ............................................................................................................................... 234.4.3 DISPLAY INTERACTIONS .................................................................................................................................... 23

5 SYSTEM SOFTWARE REQUIREMENT.......................................................................................................30

3

5.1 NETWORK SOFTWARE .............................................................................................................................305.2 NETWORK COMMUNICATION ....................................................................................................................305.3 NETWORK SECURITY ...............................................................................................................................315.4 NETWORK SERVICES ................................................................................................................................315.5 OTHER ASPECTS OF SECURITY ....................................................................................................................315.5.1 APPLICATION SECURITY MONITORING ................................................................................................................ 315.5.2 ANALYSIS AND REPORTS................................................................................................................................... 315.5.3 LOG ARCHIVING.............................................................................................................................................. 315.5.4 DATA ACCESS THROUGH INTRANET .................................................................................................................... 315.5.5 SIGNATURE UPDATING REQUIREMENTS .............................................................................................................. 325.6 DATABASE STRUCTURE ............................................................................................................................335.6.1 IT SHALL BE POSSIBLE TO EASILY REVERT TO AN EARLIER DATABASE VERSION, AGAIN WITHOUT UNDUE INTERRUPTION TO

NETWORK OPERATIONS. ........................................................................................................................................... 335.6.2 SOFTWARE MAINTENANCE AND DEVELOPMENT TOOLS......................................................................................... 335.7 DATABASE DEVELOPMENT SOFTWARE .........................................................................................................355.7.1 RUN-TIME DATABASE GENERATION AND MAINTENANCE....................................................................................... 365.8 DISPLAY GENERATION AND MANAGEMENT ..................................................................................................375.8.1 DISPLAY ELEMENTS ......................................................................................................................................... 385.8.2 DISPLAY GENERATION AND INTEGRATION ........................................................................................................... 385.9 REPORT GENERATION SOFTWARE...............................................................................................................395.10 SYSTEM GENERATION AND BUILD.............................................................................................................395.11 SOFTWARE UTILITIES .............................................................................................................................395.11.1 FILE MANAGEMENT UTILITY ........................................................................................................................... 405.11.2 AUXILIARY MEMORY BACKUP UTILITY .............................................................................................................. 405.11.3 FAILURE ANALYSIS UTILITY ............................................................................................................................. 405.11.4 DIAGNOSTIC UTILITY...................................................................................................................................... 405.11.5 SYSTEM UTILISATION MONITORING UTILITY....................................................................................................... 405.11.6 OTHER UTILITY SERVICES................................................................................................................................ 40

6 SCADA FUNCTIONS ...............................................................................................................................40

6.1 CRITICAL & NON CRITICAL FUNCTIONS .........................................................................................................406.2 DATA ACQUISITION ................................................................................................................................416.2.1 POLLING METHOD ........................................................................................................................................... 416.2.2 TELEMETRY FAILURE........................................................................................................................................ 426.2.3 ACQUISITION MODES ..................................................................................................................................... 426.3 DATA EXCHANGE ...................................................................................................................................426.4 DATA PROCESSING .................................................................................................................................426.4.1 ANALOG DATA PROCESSING ............................................................................................................................. 436.4.2 DIGITAL INPUT DATA PROCESSING ..................................................................................................................... 446.4.3 CALCULATED DATA PROCESSING ........................................................................................................................ 456.4.4 SUBSTATION TOPOLOGY PROCESSING ................................................................................................................ 45

4

6.4.5 ALTERNATE SOURCE FOR DATA: ........................................................................................................................ 456.4.6 QUALITY CODES.............................................................................................................................................. 466.5 CONTINUOUS REAL-TIME DATA STORAGE AND PLAYBACK .................................................................................466.6 SEQUENCE-OF-EVENTS DATA .....................................................................................................................476.7 SCADA LANGUAGE ................................................................................................................................476.8 SUPERVISORY CONTROL ...........................................................................................................................476.9 INFORMATION STORAGE AND RETRIEVAL .....................................................................................................486.10 HISTORICAL INFORMATION (HI) DATA RETRIEVAL ........................................................................................487 DMS FUNCTION....................................................................................................................................497 .1 GENERAL REQUIREMENT ...................................................................................................................497 .2 CONTRACTOR’S STANDARD PRODUCT................................................................................................497.3 GRAPHICAL & TABULAR REQUIREMENTS FOR DMS..............................................................................497.4 NETWORK MODEL .............................................................................................................................507.5NETWORK CONNECTIVITY ANALYSIS....................................................................................................517.6LOAD FLOW APPLICATIONS .................................................................................................................557.6.1 GENERAL CHARACTERISTICS OF LFA .................................................................................................557.6.2 REAL TIME LOAD FLOW EXECUTIONS ...............................................................................................557.6.3 STUDY MODE LOAD FLOW EXECUTION ............................................................................................567.6.4 LOAD FLOW OUTPUT ......................................................................................................................567.6.5 DISPLAY & REPORTS ........................................................................................................................577.6.6 ALARMS..........................................................................................................................................577.7 VOLT-VAR CONTROL...........................................................................................................................577.7.1 MODES OF OPERATIONS..................................................................................................................577.7.2 REPORTS.........................................................................................................................................587.7.3 DISPLAYS ........................................................................................................................................587.8 FAULT MANAGEMENT & SYSTEM RESTORATION .................................................................................587.8.1 FUNCTIONAL REQUIREMENT ...........................................................................................................587.8.2 DETECTION OF FAULT ......................................................................................................................597.8.3 LOCALIZATION OF FAULT .................................................................................................................597.8.4 SYSTEM ISOLATION & RESTORATION...............................................................................................607.8.5 REPORTS.........................................................................................................................................607.8.6 DISPLAYS ........................................................................................................................................607.9 LOSS MINIMIZATION VIA FEEDER RECONFIG........................................................................................617.9.1 MODES OF OPERATION....................................................................................................................617.9.2 DISPLAY & REPORTS ........................................................................................................................627.10 LOAD BALANCING VIA FEEDER CONFIG..............................................................................................627.10.1 MODES OF OPERATIONS ................................................................................................................627.10.2 DISPLAY & REPORTS ......................................................................................................................627.11 OPERATION MONITOR .....................................................................................................................638 PROJECT MANAGEMENT .......................................................................................................................638.1 PROJECT MANAGEMENT SCHEDULE....................................................................................................639 TESTING................................................................................................................................................649.1 FACTORY ACCEPTANCE TEST ..............................................................................................................64

5

9.2 SITE ACCEPTANCE TEST.......................................................................................................................649.3 FINAL ACCEPTANCE TEST ....................................................................................................................6510 SYSTEM GUATANTEE ..........................................................................................................................6511 APPLICATIONS TO BE DEVELOPED ........................................................................................................6712 TRAINING ..............................................................................................................................................6712.1 GENERAL............................................................................................................................................6712.2 TRAINING COURSE REQUIREMENTS...........................................................................................................6812.2.1 DATABASE, DISPLAY BUILDING & REPORT GENERATION COURSE .......................................................................... 6812.2.2 COMPUTER SYSTEM HARDWARE & SOFTWARE COURSE ...................................................................................... 6812.2.3 APPLICATION SOFTWARE COURSE.................................................................................................................... 6812.2.4 OPERATOR TRAINING COURSE ........................................................................................................................ 69

13 DETAILS OF EXISTING GIS ....................................................................................................................69

14 Details of AMR……………………………………………………………………………………………………………………………….70

15 Details of Existing OMS…………………………………………………………………………………………………………..71

6

1.1 BSES Yamuna Power Limited (BYPL)BYPL distributes power to an area spread over 200 sq kms with a population density of 5953 per sqkm. Its 11.9lakh customers are spread over 14 districts across Central and East areas includingChandni Chowk, Daryaganj, Paharganj, Shankar Road, Patel Nagar, G T Road, Karkardooma,Krishna Nagar, Laxmi Nagar, Mayur Vihar, Yamuna Vihar, Nand Nagri and Karawal Nagar.

BYPL BRPLSN Particular Unit (East &

Central)(South &West)

BSESDelhi

1 Area sq. km 200 750 950

2 CustomerDensity

Cons/sqkm 5900 2201 2980

3TotalRegisteredCustomers

Lacs 11.8 16.51 28.31

4PeakDemand (FY2010-11)

MW 1217 2305 3522

5Consumptionper year (FY2010-11)

Mus 6011 10459 16470

The following operational statistics give an overall view of the strength of BSES distribution networkas of March 2011

SN ITEMS 2010 - 11

7

BRPL BYPL

BSES

1 No. of Grids 73 50 123

2 No. of Power Transformers 202 135 337

3 EHV Capacity (MVA) 4,393 2,789 7,182

4 EHV Cable Laid (KM) 1,052 742 1,794

5 No. of 66 & 33 KV Feeders 186 142 328

6 Shunt Capacitors (MVAr) 1,424 921 2,345

7 No. of Distribution Transformer 6,763 3,252 9,777

8 Distribution Transformer Capacity(MVA) 4502 2808 7310

9 No. of 11 KV Feeders 1,027 684 1,711

10 11 KV Cables laid (kms) 2,070 1,751 3,822

11 11 KV Lines laid (kms) 1,714 252 1,966

12 Total No. of LT Feeders 21,597 13,271

34,868

13 LT Lines laid (kms) 10,095 5,553

15,648

.

2 Existing system details

2.1 Overview of the existing system

ABB has implemented the SCADA DMS system for the electricity distribution network under BSESRajdhani Power Limited (BRPL) and BSES Yamuna Power Limited (BYPL) and handed over systemin December 2007. The SCADA system consists of Network Manager Rel 2.3 based SCADA & DMSsolution including computer & network hardware at Main Control Centre (MCC at Balaji) & Back-upControl Centre (BCC at Nehru Place) locations, Remote Terminal Units (RTU) at 125 substations,110 Feeder RTU’s (FRTU) at Ring Main Units. Currently, BSES Rajdhani is operating and running itsSCADA operations from the MCC at Balaji Centre and BSES Yamuna is running its operationthrough the same control room but using dedicated 3 numbers of operator workstation provided tothem. The BCC located at Nehru place acts as back-up control center for both BRPL & BYPLoperations.

8

2.2 Existing SCADA/DMS system architecture of MCC & BCC

The main objective of this RFP is to shift the existing BCC at Nehru place to BYPL Shankar Roadlocation and use the hardware and software to function as Master Control Center – 2 (MCC -2) forBYPL license area operations. Once this activity is complete and the system stabilized, the MCC -2software and hardware has to be upgraded to latest state of the art SCADA/DMS system, which isdetailed out in the further sections.

The architecture of the current MCC & BCC concept is show in the diagram above.

The MCC currently controls & monitors the polls 125 RTU’s (ABB make RTU 560) & 110 FRTU’s(ABB make RTU 211). These 125 RTU’s also report to BCC on multiple master IEC 60870 5 104salve protocol configured in it. In the current scenario the FRTU’s report only to MCC. The MCC alsohas a ICCP link that exchanges data with Delhi Transco Control Center located at Minto Road.There is also a 10 mbps link between the MCC and BCC for synchronizing the redundant SCADA &database servers of MCC & BCC.

The communication between the control centers is performed over a WAN of 10 Mbps link and thewhole power system can be controlled and supervised from Main Control Center and Back upControl Center as the RTU’s are reporting to the respective control center.

9

All the servers (2 SCADA and 2 Historian) in the Main Control Center normally execute in the Onlineand standby operational mode, at BCC (Nehru Place) one application server is in emergencystandby mode. At any particular time either MCC or BCC is Operable.

The system is configured to make it possible to select between the Main Center and the BackupCenter in the Login dialog.

When MCC application fails, then BCC application servers and historian servers are startedmanually and RTU will start reporting to the BCC

2.3 Existing System Architecture:

2.3.1 Main & Back-up Control Centre at Balaji & Nehru PlaceThe communication between the control centers is performed over a WAN of 10 Mbps link and thewhole power system can be controlled and supervised from Main Control Center and Back upControl Center as the RTU’s are reporting to the respective control center.

All the servers (2 SCADA and 2 Historian) in the Main Control Center normally execute in the Onlineand standby operational mode, at BCC (Nehru Place) one application server is in emergencystandby mode. At any particular time either MCC or BCC is Operable.

The system is configured to make it possible to select between the Main Center and the BackupCenter in the Login dialog.

When MCC application fails, then BCC application servers and historian servers are startedmanually and RTU will start reporting to the BCC. The same functionality is proposed under this upgradation proposal.

When MCC – BCC link is up, the BCC workstation can be logged into MCC Online Servers.

In case of some testing ( During RTU commissioning ) to be carried out at BCC, MCC – BCC linkneeds to be Dropped, at BCC the Application servers are started in Online and Hot Standby modeand testing is carried out.

10

2.4 Existing Servers & Workstations at BCC

S.NO

EQUIPMENT NAME SPECIFICATION QUANTITY

1 H.P DS25 APPLICATIONSERVERS

Alpha server

2 GB memory

72GB HDD

Dual 10/100 Ethernet

15” TFT Monitor/Keyboard/

2

11

Mouse UNIX O S

2 H.P DS25 HISTORICAL SERVERS Alpha server

2 GB memory

72GB HDD

Dual 10/100 Ethernet

15” TFT Monitor/Keyboard/

Mouse UNIX O S

2

3 H.P DS 25 WEB SERVER HP Compaq

1 GB memory

40 GB SATA

PS/ 2MOUSE/

Std KEYBOARD

16X/40X DVD ROM W/R

NVIDIA QUADRO 280

TFT BROARDCOM 20”2MONITOR

1

4 H.P WORKSTATIONS (3 VDU) HP COMPAQ

1GB memory

40 GB SATA

PS/2 Mouse/std Keyboard

NVIDIA Quadro 400

16X/40X DVD-ROM w/r

Broadcom NetXreme GbEthernet PCI Adapter

3x TFT 2035 20” 2 Tone FlatPanel Monitor

2


1GB memory

1

12

40 GB SATA


NVIDIA Quadro 400

16X/40X DVD-ROM w/r

Broadcom NetXreme GbEthernet PCI Adapter

3x TFT 2035 20” 2 monitor


1MB memory

40 GB SATA


NVIDIA Quadro 280

16X/40X DVD-ROM w/r

NIC-Broadcom NetXreme GbEthernet PCI Adapter

TFT 2035 20” 2 Tone FlatPanel Monitor

1

7 FRONT END PROCESSOR (RTU) ABB MAKE 4

8 FRONT ENDPROCESSOR(FRTU)

ABB MAKE 1

9 ROUTER CISCO2611-XM-WAN Router,4WAN slots with 16 MB memory

1

10 SWITCH D-LINK Switch 48 port 2

11 FREQUENCY/DATE/TIMEDISPLAY

7 SEGMENT LED 1

12 FIREWALL PIX 515E-DMZ Bundle withsoftware

1

13 GPS RECEIVER Synchronizing clock withantenna

1

14 SOFTWARE LICENSE SCADA ABB NETWORK manager 2.3 1

13

15 SOFTWARE LICENSE DMS ABB NETWORK manager 2.3 1

16 SOFTWARE LICENSE THIRDPARTY

Oracle server enterprise Edition

MATLAB Runtime

Compaq JAVA

Window XP Professional

MS Excel

Tru64 UNIX

1

2.5 IO Sizing Parameters

Sizing Parameter Present Size Proposed Size

Receiving Stations 150 150DMS stations 110 110Substations (RMU) from SCADA 8000 8000Telemetered Analog Points 60000 140000Telemetered Status Points 120000 240000Regulation Objects 4000 4000Accumulated Objects 7500 7500No. of Alarm Groups for Measurands 30 50No. of Alarm Groups for indications 30 50No. of Delay Groups for Measurands 23 30No. of Delay Groups for indications 20 30No. of Delay Groups for Measurands 23 30No. of Delay Groups for indications 20 30

2.6 Communication protocols used1. IEC60870 5 104 protocol for communication to 125 RTU’s (ABB make RTU 560)

2. IEC60870 5 104 protocol for communication to 110 FRTU’s (ABB make RTU 211)

3. Data exchange with Delhi Transco Limited on ICCP TASE.2 protocol

2.7 Time synchronization(LAN BASED GPS CLOCK) Time synchronization messages are received from external GPS Time Base Equipment.

14

The GPS Time base is connected to each one of the two SCADA application servers, usingthe serial connection. The existing SCADA software reads the input time synchronizationtelegrams and synchronizes the server via the UNIX operating system functions.

The two SCADA application servers are configured as NTP Servers and provide timesynchronization for all other servers included in the system configuration.

The UDW servers are configured as NTP clients and requests time synchronization on acyclic basis from the SCADA NTP servers.

The PC operator workstations are configured as NTP clients and requests timesynchronization on a cyclic basis from the SCADA NTP servers.

In addition, the SCADA server takes care of time synchronization of the clock in the SCADAHMI software (WS500) in the operator workstations.

RTU’s/ FRTU’s are time synchronized from the central system every 15 minutes.

2.8 Existing Display Designs (Existing display designs shall be retained ) CB Symbology and color codes

15

Isolator Symbology & Color Codes

16

Earth Switch Symbology & Color Codes

17

2.9 Existing Naming Conventions (Existing Naming Conventions shall beretained as it is)

Presently, Object identities i.e, external identity and identification texts, defined in data engineeringare constructed according to predefined rules. Characters from a four-level hierarchy are combinedto a full object identity (external identity) and identification text. The fields may contain dots, spaces,and other special characters (., /, >, $, etc.).

The existing system has two texts per power system element (breaker, alarm, measured value, etc.):

They are referred to as External Identity & Identification Text

1. The External Identity is a text that is unique for each element in the system. This text is usedwithin the system to refer objects in pictures, calculation etc. The External Identity has alength of maximum 40 characters.

18

2. The Identification Text is used for presentation to operators in event lists, alarm lists, statuslists, etc. This text can be maximum 50 characters long and therefore more explanatory.

The Station Acronym (used as the first part in the External Identity) can be of maximum 6 characterslong and the Station Text (used as the first part in the Identification Text) can be of maximum 8characters.

2.9.1 Text StructureThe following levels exist where an element can be located:

1st level

Station

Transmission Line

2nd level

Subnet (Voltage Level)

Transformers (2 Winding)

3rd level

Feeder (bay)

Busbar

Load

3 RFP requirementThe main objective of this RFP is to upgrade the existing SCADA/DMS software at MCC-2 withlatest functionalities as described in this document. DMS FEP redundancy at MCC-2 shall also bethe part of this activity.

The new software will be integrated with the existing application interfaces like Load Shedding .Apart from the migration of software & hardware; the latest industry standard concepts of De-militarized Zone with intrusion prevention & detection system for Web System.

3.1 Scope of workA. Scope of Service

The scope of service includes installation and commissioning of the software with thehardware specified in the part B.

All the Software/License Requirements shall be clearly mentioned during the biddingprocess. No request of additional licenses will be entertained at the later stages.

19

3.2 Control Architecture of SCADA/DMS (New upgraded system)

The below diagram shows the typical architecture diagram envisaged for the new upgraded system.

20

.

3.2.1 Multi site architecture and provision for future integration with MCC-1

It is intended that the MCC1 and MCC2 complement each other as a back-up control center to oneanother. This means, if one control center fails the other control center takes over the SCADAoperations of RTU/FRTU monitoring and supervisory control. Hence, it is required that the upgradedsystem of MCC2 under the Phase 2 of the project implementation should support this Multi Sitearchitecture. However, the implementation of the Multi Site architecture is not included in the presentscope of the project.

The Multi Site architecture should support the following functions/features:

One Centralized Multi Site Data Engineering for both MCC1 and MCC2

Authority Definitions at MCC1 and MCC2 to enable control transfer schemes at the time ofcontrol center changeover

Data Synchronization between MCC1 and MCC2 for the following

Manual Data Entry

Tags

Alarm Acknowledgement

4

4.1 Software StandardsAll SCADA/DMS software, including the Operating system, RDBMS and support software, shallcomply with the industry-accepted software standards produced by national and internationalorganizations, such as ANSI, ISO, IEC, IEEE, ECMA in order to facilitate maintenance andenhancement of the SCADA/DMS systems being supplied. The Contractor shall commit to meet the"open systems" objective promoted by industry standards groups by using software products that arebased on open standards.

4.2 Design and Coding Standards for SCADA/DMS applicationsAll SCADA/DMS applications shall be maintainable by employer using the supplied software utilitiesand documentation. The SCADA/DMS software design and coding standards shall also address thefollowing:

21

a) Expansion/ scalability: software shall be dimensioned to accommodate the ultimate size ofb) SCADA/DMS system envisaged.c) Modularity: software shall be modular to minimize the time and complexity involved in

making a change to a program.d) User-Directed Termination: Functions taking long execution times shall recognize and

process user requests to abort the processing.e) Programming languages: The software shall be written using ISO or ANSI or ECMA

standard programming languages like FORTRAN, C, C++, and SQL and for Unix basedsystems the APIs shall be POSIX-conforming.

f) Portability & Interoperability: The software shall be designed for hardware independenceand operation in a network environment that includes dissimilar hardware platforms to theextent possible. The use of system services software shall be built on Open standards.

4.3 Operating System The contractor shall use Linux for Application and Database Servers and Windows shall be

used for Data Engineering/Operator Workstations/Front End servers

4.4 User interface Requirements

4.4.1 Function and Data Access Security After a user has successfully logged on, access to the SCADA/DMS functions, displays,

reports, and databases shall be restricted by pre-assigned operating jurisdictions. These operating area assignments shall be made when the function, display, report, or

database element is defined. The access security function shall compare the user's assigned operating jurisdiction against

the operating jurisdictions assigned to the function, display, report, or database element eachtime a user attempts a console action, such as:

a) Calling a displayb) Entering or changing display datac) Viewing, editing, or printing a reportd) Executing a supervisory control action

There shall be no restrictions on the assignment of multiple jurisdictions to a console & useror the assignment of a jurisdiction to multiple consoles & users

The access security function shall ensure that each jurisdiction is at all times assigned to atleast one console. If a console failure or manual reassignment of jurisdiction results in one ormore jurisdictions not being assigned to at least one console, the unassigned jurisdictionsshall be automatically assigned to a pre-assigned default console and suitable alarms shallbe generated.

SCADA/DMS users shall have Different Username/password for the real-time and the ISR tokeep the system more secure.

The server and operator login password shall be changed periodically as per security policywithout affecting the system functionality.

System should prompt for a Shift change login with the option of setting the session durationtime The pop up shall be provided at periodicity of 10 minutes. Maximum three such pop upsshall be provided.

Each log-on and log-off shall be reported as an event. Unsuccessful attempts to log-on shallalso be reported as events.

Maximum number of Operators login possible= 100

22

4.4.2 Windows Environment The user interface for SCADA/DMS system shall be standalone desktop application. The SCADA/DMS system can have the user Interface based on Microsoft Windows. The

functionality in technical specification related to the GUI features of X-windows, shall be metby available features of Microsoft Windows.

It shall be possible to save window configuration in Rooms. Rooms shall allow each user toconfigure and save a preferred layout, size, and location of windows and displays.

The World Display Features shall provide two-dimensional graphic world displays that a usershall be capable of panning, zooming and rubber banding.

The world display features such as Layers, Declutter levels, Overlays shall be supported.Displays & navigation on VPS shall be same as on the operator workstations.

4.4.3 Display interactionsRapid, convenient, and reliable display requests shall be provided using the following methods:

A. Display Requests Selection of a display from a menu display Cursor target selection on any menu, graphic, or tabular display Selection of an alarm: in this case, it shall call up the one-line display containing the

alarm’s location, Selection of an alarm or event message on a summary display followed by a display

request command Selection of display by Entering a display name or number Forward and reverse paging in a page-based display. Selecting a previous display by re-call command. Selecting a point of interest from an Overview display for viewing on full screen (such as

viewing a SLD of a substation by selecting the Substation node from a Network diagram). Selecting function keys or cursor targets dedicated to displays.

B. Display navigationDisplay navigation methods shall provide a consistent approach for moving within a display. Thefollowing methods shall be provided:

Panning with cursor positioning device or scroll bars Zooming with cursor positioning device Navigation window for rapid movement between portions of a world display Rubber-band zooming. Tool tip Find & locate Drag & drop

C. Permanent IndicatorsSeveral indicators, including those listed below, shall be permanently shown on eachSCADA/DMS display screen as minimum:

Date and Time: Date shall be presented in the format DD/MM/YY. Time shall bepresented in the format HH:MM:SS with a resolution of one second, and shall be updatedonce per second.

Username: Name of the user logged in the SCADA/DMS Mode of the server (Online/Standby) as it is possible for the HMI to login to either online

or the standby server

23

Name of the SCADA/DMS display accessed Name of the display window

D. Default Screen LayoutIt shall be possible for each user to define a personal layout (Rooms) for the screens displayedon the screen(s) of the workstation, i.e. to define a personal default setup of the position, size,and contents of the screens. The user’s default layout shall appear when the user logs on to aworkstation. When a dispatcher takes over a new shift, it shall not be possible to logon to aconsole without logging out of previous user. It shall be possible to go to another room layout ofthe logged on user at any time.

E. Display Note padA user shall be able to place and edit a note on bays, devices etc on any display. A symbol shallappear on the display indicating the presence of Note on that display. The content of the noteshall be callable using a cursor target.

F. Quality Code and Tag IndicationAll displays and reports containing telemetered analog values, device status and calculatedvalues shall have a data quality code associated with each data field. The quality code shallreflect the condition of the data on the display or report. When more than one condition applies tothe data, the symbol for the highest priority condition shall be displayed. A separate indicatorshall identify the devices that have supervisory control inhibit tags. When more than one tags arepresent on a device, the highest priority tag shall be displayed.

G. User Interaction TechniquesThe user's interaction with the SCADA/DMS system for power system operations shall primarilybe accomplished using a menu item selection technique. The first step in the interaction will beselection of the item to be operated upon. The user shall then be provided a menu of operationsapplicable to the selected item. The required operation alternatives include:

Supervisory control Data entry Device status entry Scan inhibit/enable Tag placement/removal Trend

H. User GuidanceThe SCADA/DMS system shall respond to all user input actions indicating whether the actionwas accepted, was not accepted, or is pending. For multi-step procedures, the systems shallprovide feedback at each step. User guidance messages shall be English text and shall notrequire the use of a reference document for interpretation. User shall be guided for multipleoptions.

I. Overlapping user accessThe ability to queue multiple commands from different consoles shall be provided. In this regard,however, interlocks shall be provided to avoid overlapping user access to certain functions suchas data entry and supervisory control as follows:

Data Entry: Although the same data entry field, device status entry or fields (in the caseof full-page data entry) may appear concurrently in multiple windows at multiple consoles,data entry for the field or fields shall be restricted to one window at one console at a time.An attempt to initiate data entry for the field or fields from another window shall result in a

24

user guidance message. Concurrent data entry on different areas of a world display,however, shall be allowed.

Supervisory Control: Although the same power system device, such as a circuitbreaker, may appear concurrently in multiple windows at multiple consoles, control of thepower system device shall be restricted to one window at a console at a time. An attemptto initiate control of the power system device from another window shall result in a userguidance message.

J. Function Key UsageSpecial functions shall be assigned to the 12 function keys on a standard keyboard. Withextensions (e.g., Shift, Alt, Esc) this shall result in a minimum of 48 function key actions.

K. TrendTrend shall be a display of series of values of parameters on a time axis. Both graphical trendand tabular trends shall be supported.

L. AlarmsAlarms are conditions that require user attention. All alarms shall be presented to the user in aconsistent manner. Alarm conditions shall include, but not be limited to, the following:

Telemetered or calculated value limit violations Uncommanded changes of a power system device state SCADA/DMS application program results Data source communication errors resulting in loss of data SCADA/DMS system hardware or software failures.

M. Alarm CategoriesAn alarm category provides the logical interface that connects an alarm condition to a specificArea of Responsibility (AOR) or operational jurisdiction as defined and accordingly alarm shall bereported to user. Every alarm shall be assignable to a category. Each category shall, in turn, beassignable to one or more users. A means shall be provided for changing operating shifts withoutreassignment of alarm categories at a console. Each log-on and log-off shall be reported as anevent.

N. Alarm Priority levelsEach alarm shall be assigned to an alarm priority level. Up to 8 alarm priority levels shall besupported. Each alarm priority level shall be presented in separate display. For each alarm, itshall be possible for the programmer to independently configure the following actions:

Audible alarm tone type selection and its enabling/disabling Alarm messages to be displayed on an alarm summary Alarm message deleted from alarm summary when acknowledged Alarm message deleted from alarm summary when return-to-normal alarm occurs Alarm message deleted from alarm summary when return-to-normal alarm is

acknowledged Alarm message deleted by user action.This assignment shall determine how the alarm will be presented, acknowledged, deleted,and recorded.

O. User Interaction for AlarmsThe User shall be able to perform the alarm interactions described below.

1. Alarm Inhibit/Enable

25

Inhibiting alarms for a value or device, including a complete RTU /FRTU or other datasource, shall cause all alarm processing of that value or device to be suspended. Theaction shall be recorded in the event log. However, Scanning of the value or deviceshall continue and the database shall be updated.

2. Alarm AcknowledgmentAn alarm shall be acknowledged by selecting an alarm acknowledge command whenthe item in alarm is selected on:

Any display showing the item in alarm Any display showing the alarm message

User shall be able to acknowledge alarm individually, by page, user selected manner.It shall be possible for the user to distinguish persistent & reset alarms underacknowledged & unacknowledged conditions. All alarms shall be stored by thesystem.

3. Audible alarm silencingUser shall be able to silence alarm without acknowledgement and shall remain untilthe user enable the audible alarm. The silencing & enabling shall be recorded asevent. The tones shall be definable on the console basis. For each console, multipletones shall be available.

4. Change Alarm LimitsThe user shall be able to change the alarm limits. When the user selects an item tochange its alarm limits, a menu showing the alarm limits currently in use and a dataentry field for the revised limits shall appear. All changes to alarm limits shall besubjected to data entry error checking and recorded as events. The alarms shall beannunciated according to the changed alarm limits. The user shall be able to resetalarm limits to the limits set in the SCADA database. However, these shall be treatedas temporary changes & if the system is reinitialized, the original limits defined in theSCADA database shall be operationlised.

5. Alarm PresentationsAlarm presentation shall be determined by the alarm's category and priority. Displaysshall highlight every alarm condition using a combination of colour, intensity, inversevideo, blinking and audible sound. The alarm condition highlighting shall showwhether the alarm has been acknowledged. The highlighted alarm condition shallappear on all displays containing that device or value at all consoles regardless of thealarm's category. Alarm messages shall be a single line of text describing the alarmthat has occurred and the time of occurrence. The alarm message shall be Englishtext and shall not require the use of a reference document for interpretation.

P. EventsEvents are conditions or actions that shall be recorded by the SCADA/DMS system but do notrequire user action. Events shall be generated under the following conditions

User initiated actions Conditions detected by application functions that do not require immediate user

notification, but should be recorded.Events shall be recorded in the form of an event message. The event message format shallbe similar to the alarm message format. The same message format shall be used fordisplaying and printing events. Event messages shall be displayed on an events summary.Event messages shall be stored on auxiliary memory of SCADA/DMS system and archived in

26

chronological order and reverse chronological order. It shall be possible to sort, display, andprint event messages from any console.

Q. Report Generationa. All the existing report formats shall be modified and migrated as per users requirement.b. The contractor shall be required to generate the Daily, Weekly, Monthly reports formats

for SCADA/DMS system.c. The report formats shall be finalized during detailed engineering stage.d. The user shall be able to schedule periodic generation of reports, direct report to display,

print report, and archive report using report-scheduling display.e. The report scheduling display shall enable entry of the following parameters, with default

values provided where appropriate: Report name Report destination (printer or archiving device) Time of the system should produce the report.

f. The user shall be able to examine and modify the contents of reports for the currentperiod and for previous report periods using displays.

g. Any calculation associated with the revision of data in a report shall be performedautomatically after data entry has been completed.

h. The report review displays shall accommodate formatted report pages up to132characters in width and 66 lines in length and shall contain headings that correspond tothe printed report headings. For reports containing more columns or rows than thedisplay, the system shall include a means to view the entire report in a graphic format.

i. The report view and editing displays shall function with the initially supplied reports andall future reports added by employer.

R. System Configuration Monitoring and Control The user shall be provided with the capability to review SCADA/DMS computer system

configuration and to control the state of the configuration equipment using displays. Thefollowing operations shall be possible:

Failover of each server Monitoring of servers, device, including workstations, RTUs, FRTUs,FPIs, status &

loading of WAN LANs etc. Monitoring of the processor resource, hard disk & LAN/WAN utilization Control & monitor of SCADA/DMS functions

S. Dynamic Data PresentationIt shall be possible to present any item in the database on any display. All supervisory controland data control capabilities shall be supported from any window of a world display.Device status or data values shall be displayable anywhere on the screen, excluding dedicatedscreen areas such as the display heading.Status and data values shall be presented in the following formats as appropriate: Numerical text that presents analogue values shall have the provision for the format definition

of the text shall include the number of characters, number of decimal places, and the use ofpositive /negative sign or flow direction arrows, etc.

Normally the telemetered MW/Mvar values along with the sign/direction shall be displayed onthe Single line diagram and Network diagram. However the user shall also be able to displayall other telemetered and calculated/ estimated analog values (I, V, pf etc. for each phase) onthe Single line diagram (SLD) and Network diagram. All the displays shall be suitably

27

designed to view telemetered and estimated/calculated values simultaneously for eachfeeder.

Symbols, including alphanumeric text strings for an item, based upon state changes e.g.,circuit breaker (OPEN/CLOSE/ INVALID).

Symbols, including alphanumeric text strings for indicating the data quality flags. Colors, textures, and blink conditions based upon state or value changes or a change of data

quality, e.g., alarm limits.

T. Element HighlightingElement highlighting techniques shall be provided to draw the attention of Dispatcher to criticalstate of the system. The highlighting technique shall include change of colour, colour intensity,blinking, Character inversion, Line texture, appended symbols etc. This feature shall be used tohighlight alarms, power system device and measurement status, data quality, data entrylocations on a display and error conditions.

U. Display TypesThe following list describes the types of displays that are to be included in the SCADA/DMSsystem.

1. SCADA/DMS System DisplayA display shall be provided that lists all SCADA/DMS system directory displays. Thedisplays shall be listed in alphabetical order with suitable separation in the list to enhancereadability. Each entry in the list shall have a cursor target for display selection.

2. Distribution System Network DisplayA graphic overview network display of the distribution system with substations, feeders.Distribution network colour coded by voltage shall be provided. This display shall presentthe distribution system in a graphic format provided by employer. Telemetered andcalculated data like Real and reactive power flows shall be displayed as a value with adirection arrow/positive- negative signs. Lines that have exceeded their loading limitsshall be highlighted. Substations and power stations shall be depicted by symbols thatreflect the presence of alarms at that substation or power station. Cursor selection of asubstation/ power station symbol shall result in the associated Single line diagram displayfor that substation/ power station.

3. Substation SLD displays MenuA display shall be provided that lists all substations that can be viewed via a SLD display.The name of the SLD displays shall be listed in alphabetical order, according tosubstation name, with suitable separation in the list to enhance readability. Each entry inthe list shall have a cursor target for graphic display selection.

4. Substation SLD DisplaysSLD displays shall be provided for each substation, including those for which telemetrymay not be available but are required for running the DMS applications. Each displayshall present telemetered, manually entered, and calculated power system data on aSingle line diagram that shows substation layout in terms of its buses, switches, lines,and transformers. The feeder names in the SLD shall have linkage with remotesubstation end SLD, distribution network associated with that feeder. It shall be possibleto move to remote-end substations SLD by selecting this feeder. The user shall be able toperform any user interaction defined by the specification on these displays.

28

5. Substation Tabular DisplaysTabular displays shall be provided for each substation. These displays shall list therealtime values of telemetered, manually entered, and calculated data associated with thesubstation as well as related information such as alarm limits. The user shall be able toperform any user interaction defined by the Specification on these displays.

6. Alarm Summary DisplaysDisplays that list or summarize all unacknowledged and acknowledged alarms shall beprovided. The summary shall separate acknowledged and unacknowledged alarms.Capacity shall be provided for at least 200 alarm messages for each alarm summarytype. If an alarm summary display becomes full, the oldest messages shall beautomatically deleted and the newest messages shall be added. It shall be possible toperform any alarm interaction from this display. The user shall be able to select betweenviewing events in chronological or reverse chronological order.

7. Event Summary DisplaysEvent summary displays shall list the most recent events and shall be organized bycategory for those categories assigned to a given console, as one summary display for allcategories assigned to a console, or by all conditions system-wide without reference tothe categories assigned to a console, as selected by the user. The user shall be able toselect between viewing events in chronological or reverse chronological order.

8. Operating Information SummariesEvent summary displays shall list the most recent events and shall be organized bycategory for those categories assigned to a given console, as one summary display for allcategories assigned to a console, or by all conditions system-wide without reference tothe categories assigned to a console, as selected by the user. The user shall be able toselect between viewing events in chronological or reverse chronological order.

9. Manual Override SummaryThe manual override summary shall list all telemetered and calculated device status anddata values for which a user has substituted a value.

10. Off-Normal SummaryThe off-normal summary display shall list devices and values that are found to beabnormal, i.e., are not in their normal state. Telemetered, calculated, and manuallyentered status and data values shall be included.

11. Out-of-Scan SummaryThe out-of-scan summary display shall list device status and data values that are notcurrently being processed by the system. If an entire telemetry source such as anRTU/FRTU is out-of-scan, the out-of-scan summary shall display the source without anyof the individual device status or data values associated with the source

12. Alarm Inhibit SummaryThis display shall list devices and data values for which the user has suspended alarmprocessing.

13. Tag SummaryThis display shall list and describe all active device tags.

14. Tabular Trending Summary Displays

29

The display shall have trending summary displays from where various trends can benavigated.

15. Computer system Configuration and Monitoring DisplaysGraphic and tabular displays shall be provided that allow the user to:

Monitor and revise the configuration of the computer system Monitor the system's resource utilization statistics.

16. RTU/ FRTU Communication Channel Monitoring and Control DisplayThis display shall show information on the status of the system's communication interfacedevices (including communication channels), the accessibility of each RTU/FRTU in agraphical form. The user shall be able to Enable/Disable any communication channelfrom this display.

17. SCADA/DMS Application Program DisplaysApplication program displays shall be provided to satisfy the user interface requirementsof the system functions stated throughout this Specification. Application program displaysshall be based on a standard user interface design across all applications to provide acommon look and feel. The application's information shall be presented in such a way asto facilitate user operations. The required displays for all DMS Applications shall also bemade available to the user.

18. GIS integrationThe SCADA/DMS dynamic distribution network with GIS land base at the back groundshall be available for navigation. Operator shall be able to perform all functions & havefeatures as envisaged in the specification. Suitable GIS adaptor shall be provided toimport the distribution network model & GIS information from GIS system. The details ofexisting GIS are attached in the Annexure-2.

19. Help DisplaysHelp displays shall be provided to aid the user in interpreting displayed information and toguide the user through a data entry or control procedure.

5 System Software Requirement

5.1 Network SoftwareThe network software for SCADA/DMS system shall include software for networkcommunication, security and services.

5.2 Network CommunicationUsers and various applications shall be able to communicate within the SCADA/DMS localarea network and operate as described in this Specification. The network communicationssoftware shall use a standard network protocol such as TCP/IP. The software shall linkdissimilar hardware nodes, including local and remote workstations, application servers,communication servers, and various peripherals (such as printers) into a common datacommunication network allowing communications among these devices.

30

5.3 Network SecurityA user authentication scheme consisting at least of a user identification and password shall berequired for the user to request a connection to any network node.

5.4 Network servicesThe following network services shall be provided for the users of SCADA/DMS system:

Network file management and transfer, for files containing text, data, and/or graphicsinformation

Network printing management Network time synchronization Network backup over LAN Task-to-task communications to external computers LAN global naming facilities. Remote procedure call Remote terminal session

5.5 Other aspects of security

5.5.1 Application Security MonitoringThe standard operating system shall support the monitoring of security on host installedapplications.The system shall support or allow the creation of monitoring for:

Application Software Error Conditions Application Software Performance Issues Application Configuration Changes Application Logins, etc.

5.5.2 Analysis and Reports The system with the stored information, shall be able to produce analyses and reports

to meet security compliance requirements. The system shall be equipped with bestpractices ad-hoc reports widely used in the industry.

The employer’s personnel shall be trained to be capable of creating new customanalysis and reports, and revising existing, without requiring external consultation.

5.5.3 Log ArchivingThe security system shall archive, record, and store all security related events in raw form forat least one year. As a minimum, the event logger shall record all security related events fromthe perimeter security devices and the host IPS.

5.5.4 Data Access through intranetThe Web server at Control Center is to function as source of information on the distributionnetwork. It will be accessed by BYPL intranet user. Any additional client software, if required,at external clients/users ends, the same shall be made dynamically available from Webserver for its downloading by these external clients. There shall not be any restriction to thenumber of clients downloading this software (i.e. Unlimited number of client downloads shallbe provided). The external users shall be licensed users of the employer. The followingfeatures are required:

31

a. The Web servers shall be sized to support at least 25 concurrent external intranetclients/users for providing access to real-time data.

b. External intranet clients/users shall be connected to the web servers through secureauthentication. These users shall be denied direct access to the SCADA/DMS protectedLAN.

c. Internal SCADA/DMS users shall not have any dependency on the availability of the Webservers.

d. Interface between Web server and clients shall be established through Firewall. It shall beensured that clients shall have view only access to the SCADA system information.

e. The web server shall provide access to allowable real time data and displays, at definedperiodicity, for viewing by external clients/users.

5.5.5 Signature Updating RequirementsThe system shall be able to accept timely updates. The updates shall keep the threatsignatures current, providing the latest detection and protection. The updates shall alsoincorporate the latest security enhancements into the Security Management System. Theseenhancements shall increase security and functionality, without requiring redesign orreengineering efforts.

5.6 Database structure The SCADA/DMS RTDB (Real Time Data Base) shall be an active process model. i.e.

It shall initiate actions or events based on the input it receives. The RTDB shalldescribe the state of the power system at a given point in time and the events thatmove the system to a new state at the next point in time. This database is required tosupport the data access to real time information and to allow efficient integration andupdate.

A library of event routines may encapsulate or interface the RTDB with othercomponents of the system. These event routines shall be the preferred means forapplication programs to interact with RTDB. This way, application programs (andprogrammers) only need to concern themselves with callable interface (API) of theseroutines. Each application shall interact with the RTDB through the event library. Theseevent routines shall serve as generic APIs for database access thereby eliminatingproprietary database function calls at the application level.

The SCADA/DMS shall include a single logical repository for all data needed to modelthe historical, current, and future state of the power system and SCADA/DMS – theSource Database (SDB). All information needed to describe the models on which theSCADA/DMS operates, shall be defined once in the SDB and made available to allSCADA/DMS applications, real-time database, and user interface maintenance toolsthat need the information.

Any database update, whether due to local changes or imported network modelchanges, shall be able to be placed online in a controlled manner without causingundue interruption to network operations, including without losing any manually entereddata. For example, a network model update to introduce a new substation shall notinterrupt the ability to perform supervisory control actions or receive telemetry to viewthe network state.

32

5.6.1 It shall be possible to easily revert to an earlier database version, againwithout undue interruption to network operations.

5.6.2 Software Maintenance and Development Tools1) General requirements

A set of software shall be provided to enable maintenance of application software anddevelopment of new software in software development mode wherever applicable. Allhardware and software facilities shall be provided to allow creation, modification anddebugging of programs in all languages that are supplied. The following shall thus bepossible:

a) Program and data editingb) Program compiling and assemblingc) Linkingd) Loading, executing and debugging program.e) Version managementf) Concurrent development

The following features shall be provided:a) Library managementb) Programs allowing to copy and print any data or program filesc) Backup and restored) File comparisone) Sort and mergef) Programs that allow to partially save and recover volumesg) Core and memory dump.

In addition tools shall have the following:2) Command language

A complete command language shall be provided that allows interactive use of any consoleto interactively create, modify and debug programs in all languages provided. It should alsobe possible to create and save command procedure file and to execute it sequentially.

3) Linkage Editor and LoaderCompilers and assemblers, linkage editor and loader shall be provided to link object modulesfrom an assembly or compilation to produce an executable module and load it in system. Asfar as possible, the loader shall accept object modules issued from various languagecompilers.

4) Symbolic DebuggerA language-independent, interactive symbolic debugger shall be provided to enable the userto test new software and inspect the characteristics of existing software. The execution of aprogram shall be under the control of the debugger according to parameters entered by theuser. The following features shall be supported:

a) Program execution breakpoint controlb) Program execution sequence tracingc) Display and modification of program variablesd) Attachment of specifically written debug code to the program under test. The

debugger shall allow halting execution of a program at predefined points, reading andmodifying the registers and memory locations and executing step by step a program.

5) System IntegrationSystem integration services shall be provided for adding new programs to the set of activesoftware after the programs have been tested. These services shall include commands tosubstitute one program for another, to set up or modify operating system tables, and to

33

schedule and activate a new program with a minimum of interference with the normal runningof the SCADA/DMS functions. The capability to restore the system to its status prior to thenew program integration shall be provided.

6) System GenerationSystem generation software and procedures shall be provided to generate an executableobject code of all software, databases, displays, and reports. Employer personnel shall beable to perform a system generation on site, using only equipment, software, procedures,and documentation supplied with the SCADA/DMS. It shall not be necessary to return to theContractor's facility or rely on the assistance of Contractor personnel. The proceduresnecessary to perform a complete system generation shall be provided as interactive or batchcommands maintained on auxiliary memory and on archive storage, source listings, anddetailed manuals. System generation shall be accomplished without programming; onlydirectives or control commands described in the procedures shall be required.

7) Code ManagementA code management utility shall be provided for documenting and controlling revisions to allSCADA/DMS application programs. The utility shall maintain a library of source, object, andexecutable image code and provide a controlled means for changing library files containingthis code.The code management utility shall include inventory, version, and change control andreporting features. Program dependencies shall be included in the library for user reference.The code management facility shall retain a complete history of additions, deletions, andmodifications of library files. An integrated source code development subsystem supportingC, Fortran, Java, and C++, other programming languages used in the SCADA/DMS shallprovide a software configuration management system to define the elements and theassociated attributes of the applications provided in the SCADA/DMS. Source definitions forall elements of an application shall be maintained in disk files under a code managementsystem. As a minimum, the code management system shall:

a. Manage source code and binary imagesb. Allow tracking of code changes by date, author, and purposec. Manage documentation modules and associate them with source code, binary

images, and other documentationd. Support multiple teams of programmers working concurrently on the same modulese. Provide an efficient link between modules

5.7 Database Development softwareThe databases organization shall be designed to meet the following major functionalrequirements:

a) Data consistencyb) Compliance with the system performance requirements including both response timesc) Expansion capabilities

o A Database development software shall be provided which shall containdatabase structure definitions and all initialisation data to support the generationof all relational, real time database (RTDB) non-relational run-time databasesrequired to implement the functions of SCADA/DMS system.

o All the facilities required for generating, integrating and testing of the databaseshall be provided with the SCADA/DMS system.

o The delivered SCADA/DMS database shall be sized for the ultimate system asdescribed in this Specification.

o The database development facility shall be available on development systemcomprising of server & workstation.

o Once the database creation/ modification activity is over, the compiled runtimeexecutables shall be downloaded to all respective machines.

34

o Executing the database generating functions shall not interfere with the on-lineSCADA/DMS functions.

o The database development function shall locate, order, retrieve, update, insert,and delete data; ensure database integrity; and provide for backup andrecovery of database files.

o The database development function shall generate and modify all SCADA/DMSdata by interfacing with all database structures.

o The location of database items shall be transparent to the user performingdatabase maintenance. Extensive reasonability, integrity, and referentialintegrity checks shall be made on user entries to detect errors at the time ofentry. Invalid entries, such as entering an invalid data type or attempting todefine contradictory characteristics for a database item, shall be detected andreported to the user in an error message.

o All error messages shall be in plain English. Help displays shall be available toprovide additional, detailed information to the user on request. All newly definedpoints shall be initially presented to the user with default values for allparameters and characteristics where defaults are meaningful.

o It shall also be possible to initialise a new database point description to anexisting database point description. The user shall be guided to enter new data,confirm existing data, and change default values as desired.

All required entries for any database item selected for changes shall be presented tothe user. When parameters are entered that require other parameters to be specified,the additional queries, prompts, and display areas required to define the additionalparameters shall be presented automatically.

a) Add, modify, and delete telemetered, non-telemetered, or calculated databaseitems and data sources such as RTUs/ FRTUs / FPI, data links, and local I/O.

b) Add, modify, and delete application program datac) Create a new database attribute or new database typed) Resize the entire database or a subset of the databasee) Redefine the structure of any portion of the database.

The database tool for creation, editing, generation, export, import of ICCP databaseincluding complete definition, association, bilateral tables, objects etc shall be provided.

5.7.1 Run-Time Database Generation and MaintenanceThe database development software shall generate incremental database changes as well asruntime (loadable) databases from the global source database (user entered database)Incremental structure changes in the source database such as addition of a bay or asubstation shall not require regeneration of the entire run-time database. Based on the natureof the change, the database development software shall determine which portion of thedatabase must be regenerated and which displays, reports, and software functions must bere-linked. All errors that were not detected during data entry time but are encountered duringrun-time database generation shall be flagged. The database generation routines shallcontinue processing the database in an effort to detect all errors present in the databasebefore terminating the generation task.

1) Data RetentionThe database generation process shall retain and utilize data from the current SCADA/DMSdatabase in the newly generated database, even when a newly generated database contains

35

structure changes. Data to be retained across database generation cycles shall include, butnot be limited to, quality codes, manual entries, tags, historical data, and tuning parameters.

2) Making Database OnlineAfter an error-free database generation, the user shall be able to test the data-base in an off-line server prior to its use in an on-line server. The previous run-time database of the servershall be archived such that it is available to replace the new database upon demand. Thearchived database shall be deleted only when directed by the user. Newly generated run-timedatabases shall only be placed on-line by user command. Following the assignment of a newdatabase to a server and on user demand, the database management software shall accesseach SCADA/DMS server to ensure that all databases are consistent. Inconsistencies shallbe annunciated to the user.

3) On-Line Database EditingSelected database management functions and changes to a run-time database shall bepossible without requiring a database generation. These shall be limited to viewing functionsand changes to the contents, but not the structure of the database. On-line changes shall beimplemented in all applicable SCADA/DMS run-time databases without system downtime.On-line database editing shall not affect the SCADA/DMS system's reaction to hardware andsoftware failures nor shall it require suspension of exchange of data among servers forbackup purposes.

4) Tracking Database ChangesThe database manager utility shall maintain Audit trail files for all changes made by all users.The audit trails shall identify each change including date and time stamp for each change,and identify the user making the change. An audit trail of atleast last 2 months shall bemaintained and another audit trail maintaining records of who/when performed the editoperation shall be maintained for a period atleast 2 months.

5) Initial Database GenerationThe initial database shall contain all data required by the SCADA/DMS systems. Defaultvalues shall be used in consultation with the employer for data that is not provided byemployer. Population and maintenance of the distribution network model should be possibleby using the database maintenance tools to build the database from scratch. In addition ifrequired data already exists within the Employer’s corporate Geographic Information System(GIS), the SCADA/DMS database functions should leverage this effort by providing aninterface/adaptor to extract GIS data and automatically generate the complete NetworkOperations Model. The data extracted should include network device information,connectivity, topology, nominal status and non-electrical data such as cable ducts, land basedata etc. Further Land base data can be sourced from GIS in Shape files or DXF.

5.8 Display Generation and ManagementSCADA/DMS displays shall be generated and edited using interactive display generationsoftware delivered with the system. The display generator shall be available on developmentsystem & once the display/ displays creation/ modification activity is complete, the compiledruntime executables shall be downloaded on all workstations/servers. The display editor shallsupport the important construction options like:

a) Copy/move/delete/modify,b) Building at different zoom level,c) Linking of any defined graphics symbol to any database point,d) Pop-up menus,e) Protection of any data field on any display against user entry based on log-on

36

f) Identifiersg) Activation of new or modified displays for any application or across all applications of

the system by a simple command that causes no noticeable interruption of on-lineDMS system activity.

All displays, symbols, segments, and user interaction fields shall be maintained in libraries.The size of any library and the number of libraries shall not be constrained by software. Thedisplay generator shall support the creation, editing, and deletion of libraries, including copyingof elements within a library and copying of similar elements across libraries. A standard set oflibraries and libraries of all display elements used in the delivered SCADA/DMS system shallbe provided. Displays shall be generated in an interactive mode.The user shall be able to interactively:

a) Develop display elementsb) Link display elements to the database via symbolic point namesc) Establish display element dynamics via database linkagesd) Define linkages to other displays and programse) Combine elements and linkages into display layersf) Combine display layers into displays.

The display generation, compilation & loading shall not interfere with the on line SCADA/DMSfunctions. All user interface features defined in this Specification shall be supported by thedisplay generator.

5.8.1 Display ElementsThe elements available to create a display shall consist of graphic primitives symbols,segments, User Interaction Field and layers. These elements shall be available to be linkedto the SCADA/DMS functions and dynamically transformed on the display as governed bylinkages to the database.

1) Dynamic Transformation LinkagesDynamic transformations shall be performed on symbols and display segments based upondynamic linkages to database variables. All linkages to the database shall be defined viasymbolic point names. Each symbol or segment stored in a library shall include its dynamictransformation linkages, although the specific point names shall be excluded. Dynamictransformation linkages shall support the dynamic data presentation.

5.8.2 Display Generation and Integration The displays shall be constructed from the display elements described above. The

display definition shall allow displays to be sized to meet the requirements of theSCADA/DMS application for which they are used; displays shall not be limited by thesize of the viewable area of the screen.

The display generation software shall allow unbroken viewing of the display imagebeing built as the user extends the size of the display beyond the screen size limits.Each display shall include the display coordinates definition that will permit a user tonavigate successfully to the portion of the display that is of interest.

It shall be possible for a user to build a new display starting with a blank screen or anexisting display. The definition of each layer shall include a range of scale factors overwhich the layer shall be visible. The display generator shall also support manual controlof layer visibility, where the user of the display shall determine the layers on view. Eachdisplay may incorporate manually and automatically (by scale factor) displayed layers.

37

The user shall also define the called before or after presentation of the display. Thedisplay generator shall support the integration of new and edited displays into theactive display library. During an edit session, the display generation software shallallow the user to store and recall any display.

A copy of previous display library shall be saved & protected and it shall be broughtback on line or can be deleted upon user request. It shall not be necessary toregenerate any display following a complete or partial system or database generationunless the database points linked to the display have been modified or deleted.

1) Imported CADD DrawingsThe display generator shall support the import of drawings, including power systemone-line diagrams, developed by BYPL on Computer Aided Drafting and Design(CADD) systems. The drawings may be used in the SCADA/DMS system as the staticbackground for displays. The display generator shall provide the capability to add,delete, and modify the dynamic information supplied to the drawings using the specifiedfeatures of the display generation and management software. As necessary, employerwill replace the static background by importing a new drawing from the CADD systemand re-linking associated database elements. The display generator shall allow a userto update the dynamic information to reflect any changes required by the updateddrawing.

5.9 Report Generation Software The SCADA/DMS system shall include report generation software to generate new

report formats for SCADA/DMS and edit existing report formats. The user shall beguided in defining the basic parameters of the report, such as the report databaselinkages as symbolic point names, the report format, the report activation criteria, thereport destination (workstation, printer, or text file), and the retention period for thereport data.

The user shall be able to construct periodic reports and ad-hoc queries via interactiveprocedures.

The capability to format reports for workstations shall be provided. The user shall be able to specify the presentation format for periodic reports and ad-

hoc query reports as alphanumeric display format, graphical display format, oralphanumeric printer format.

The user shall be able to specify that processing functions, such as summations andother arithmetic functions, be applied to portions of the report data when the report isprocessed for display, printing, or file storage.

The software shall provide for generation of reports that are the full character width ofthe printers and that use all of the printer's capabilities, such as font sizes and stylesand print orientation.

For report data editing, the user shall be able to obtain the data from a retained report,modify the data, repeat the inherent data calculations, reprint the report, and save it ina report retention file on auxiliary memory without destroying the original report.

The user shall also be able to access a retained report, modify its point linkages to thedatabase, modify its format, and save it in a report retention file on auxiliary memory asa new report without destroying the original report. Executing the report generatingfunctions shall not interfere in any server of the system with the on-line SCADA/DMSfunctions.

38

5.10System Generation and BuildSystem generation includes the activity of generating an executable object code of alldatabases, displays, and reports as required for SCADA/DMS system. System build is theprocess under which all the above executables and the executables provided for SCADA/DMSapplication software are ported to the SCADA/DMS system hardware and configuring to makeit operational. The contractor shall do the complete system generation and build as required forsuccessful operation of the SCADA/DMS system. The contractor shall also provide thecomplete backup of the SCADA/DMS system in electronic media such as tapes, CDs, MOdisks etc. Employer personnel shall be able to restore the SCADA/DMS system at site byusing above backup tapes/CDs etc. The contractor shall provide the procedures necessary torestore the system from the backup tapes/CDs etc. The Backup control centre system shallalways have updated set of system build. It shall be synchronised with the SCADA/DMScontrol centre.

5.11Software UtilitiesAll software utilities used to maintain SCADA/DMS software, whether or not specificallyrequired by this Specification, shall be delivered with the system. The software utilities shalloperate on-line (in background mode) without jeopar-dizing other SCADA/DMS applicationfunctions that are running concurrently. This utility software shall be accessible fromworkstations, programming terminals, and command files on auxiliary memory. Multiple usersshall have concurrent access to a utility program task, provided there are no conflicts in theuse of peripheral devices.

5.11.1 File Management UtilityFile management utilities shall be provided that allocate, create, modify, copy, search, list,compress, expand, sort, merge, and delete program files, display files, and data files onauxiliary memory and archive storage.

5.11.2 Auxiliary Memory Backup UtilityA utility to backup auxiliary memory of server and workstation files onto a user-selectedauxiliary memory or archive device shall be supplied. The backup utility shall allow for userselection of the files to be saved based on: (a) Server and workstation (b) File names(including directory and wildcard designations) (c) File creation or modification date and time(d) Whether or not the file was modified since the last backup. A backup utility that canbackup all server and workstation auxiliary memories on to a single target auxiliary memoryor archive device shall be provided. The backup utility must ensure that the source auxiliarymemory files are captured properly regardless of caching activity.

5.11.3 Failure Analysis UtilityFailure analysis Utility shall be provided to produce operating system and applicationprogram status data for analysing the cause of a fatal program failure. The failure informationshall be presented in a condensed, user-oriented format to help the user find the source ofthe failure. The information shall be presented on displays and recorded for historical recordsand user requested printed reports.

5.11.4 Diagnostic UtilityThe system shall have suitable auto diagnostic feature, on line & offline diagnostic Utility foron-line and off-line monitoring for equipments of SCADA/DMS system shall be provided.

39

5.11.5 System utilisation Monitoring UtilitySoftware utility shall be provided in each server and workstation to monitor hardware andsoftware resource utilisation continuously and gather statistics. The monitoring shall occur inreal-time with a minimum of interference to the normal SCADA/DMS functions. The periodover which the statistics are gathered shall be adjustable by the user, and the accumulatedstatistics shall be reset at the start of each period. The statistics shall be available for printoutand display after each period and on demand during the period.

5.11.6 Other Utility ServicesOn line access to user and system manuals for all software/Hardware products (e.g.,Operating System and Relational Database Software/hardware) and SCADA/DMSapplications shall be provided with computer system.

6 SCADA Functions

6.1 Critical & non critical functionsThe functions defined in this specification shall be classified as Critical or as Non-critical. Everycritical function must be supported by sufficient hardware & software redundancy to ensurethat no single hardware & /software failure will interrupt the availability of the functions for aperiod exceeding the automatic transfer time defined in the specification.Non-critical function may not be supported by hardware & software redundancy and can besuspended in case of non-availability of corresponding hardware.Generally the following are to be classified as Critical functions

a) All SCADA applicationsb) Information Storage and Retrieval (ISR)c) All DMS applicationsd) Data exchange of SCADA/DMS system with IT system, ABT, ICCP.e) Web server applications, Security applicationsf) Network Management system (NMS)

The following are Non-Critical functions

a) Database modification and generationb) Display modification and generationc) Report modification and creationd) Data exchange with Remote VDUs, if any

The following SCADA functions are envisaged under this specification.

1. Data Acquisition from RTUs at S/S , FRTUs at RMUs2. Time synchronization of RTUs & FRTUs3. Data Exchange among the SCADA/DMS system, GIS system, State load dispatch

centre.4. Data Processing5. Continuous real-time data storage and playback6. Sequence of event processing7. Supervisory Control8. Fail soft capability

40

9. Remote database downloading, diagnostics & configuration11. GIS adaptor (GIS Land base data, network model using GIS engines/adaptorssupporting Native Adapters , , using Model Exchange12. Information Storage & Retrieval (ISR)

6.2 Data AcquisitionSCADA system shall acquire data from Remote Terminal Units (RTUs) and FRTUs.

6.2.1 Polling method Digital status data from RTU shall be reported by exception and shall be updated and

displayed within 4 seconds. Digital status data from FRTU shall be also be reported by exception and shall be

updated and displayed within 6 seconds. Digital status data shall have higher priority than the Analog data. The system shall have dead band for data by exception. All analog values except energy values shall be reported by exception from the RTU &

FRTU. The analog value, when reported by exception, shall be updated & displayed within

5sec from R/S & 10sec from substations at the control centre. An integrity scan of all status & Analog values shall also be made every 10 minutes

(configurable). The provision shall also be made to report analog values periodically atevery 10sec (user configurable), if required by the user.

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

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

i. Upon start up of the systemii. RTU/ FRTU status change is detected such as RTU/ FRTU restart,

Communication Link restorationiii. On demand by SCADA/DMS functionsiv. On request by the user

6.2.2 Telemetry Failure If data is not received from an RTU/FRTU after a user-adjustable number of retries,

each affected point in the SCADA system shall be marked with a ‘telemetry failurequality code’ and an alarm shall be generated.

Telemetry failure of data can be due to failure of communication link, failure ofcomplete RTU/FRTU or RTU/ FRTU module or MFT etc.

Only a single alarm shall be generated if an entire RTU/ FRTU or its communicationchannel fails. In the event of telemetry failure, the last good value/status shall beretained in the database for each affected point.

When telemetry returns to normal, the associated SCADA system shall automaticallyresume updating the database with the scanned data.

The user shall be able to substitute a value in the database for any point that isexperiencing telemetry failure which shall be marked with ‘manual replaced’ qualitycode’ in addition to the ‘telemetry failure’ quality code.

41

The user shall also be able to delete any point (or entire RTU/FRTU) from scanprocessing. All deleted points shall be marked with a ‘delete-from-scan’ quality code.

6.2.3 Acquisition ModesThe following modes of data acquisition shall be supported:

a. Enable - When RTU/FRTU is enabled, the data is scanned in normal fashion andcontrol command execution is allowed.

b. Disable - When RTU/FRTU is disabled, the data scanning & control execution isdisabled. This is equivalent to” delete from scan “of complete RTU.

c. Test /Maintenance

6.3 Data Exchange

6.4 Data ProcessingData processing involves a value which has been converted to internal form and analyzed forviolations of limits. The data processing shall set various data attributes depending on theresults of the checks and shall trigger any additional processing or calculation. The SCADA/DMS system shall prepare all the acquired data for use by the power system applications. TheSCADA system shall have capability to accept data from the following sources:

Real-time (also referred as telemetered) data received from control centers /IT systemand RTUs/FRTU etc)

Calculated data Manually entered data Sequence of events data Alternate data sources

6.4.1 Analog Data Processingi. Conversion to Engineering Units

Analog points that are transmitted to SCADA system in raw data format shall be converted toengineering units before being stored in the database. This conversion function shall include,as a minimum, the capability to perform the following conversion algorithm:Value = (A * scanned valued) + B,Where, A and B are programmer-adjustable constants assignable as database attributes ona per point basis.

ii. Zero dead band processingThe SCADA system at control centre shall process each analog input for dead band zoneprocessing. The acquired value, if falls between the dead band range around zero then itshall be considered as clamped zero value else the actual value shall be considered.

iii. Reasonability Limit CheckThe reasonability limits shall represent the extremes of valid measurements for the point'svalue. All analog values shall be compared against defined high and low reasonability limits.The comparisons shall be performed at the scan rates of the analog values. An alarm shallbe generated the first time a reasonability limit violation is detected. The last valid value of

42

the variable shall be maintained in the database When data returns to a reasonable value,the new value shall be accepted .

iv. Limit MonitoringFor bi-directional quantities (positive or negative) there shall be a set of five limits for eachdirection. For unidirectional quantities there shall be a set of three limits in one direction.These limits will represent increasing levels of concern. These five limits shall be set withinthe boundaries of reasonability limit. Generally, any alarm can be assigned as audible alarmbut emergency limit shall necessarily be assigned as audible alarm. All telemetered andcalculated analog point shall be compared against above sets of high and low limits eachtime the value is scanned or calculated. Whenever a monitored point crosses a limit in theundesirable direction a limit violation alarm message shall be generated. Whenever amonitored point crosses a limit in the desirable direction, an exit event message shall begenerated. If multiple limits have been crossed since the last check, each limit crossed shallbe reported. All limit monitoring shall preclude annunciation of multiple alarms when a valueoscillates about an alarm limit by utilizing a programmer-adjustable alarm dead-band for eachpoint. The user shall be able to temporarily override any of the above limits (which are in use)by entering a new value. When the user overrides a limit, it shall be marked on all displays.The override value shall be recognized, and any display, report, or log containing the value ofthe overridden limit shall include it as such. An override value shall be used instead of thepermanent value until the user removes the override condition or system is re-initialized. Anychange in alarm states resulting from a change in limit value shall be reported. Contractorshall finalize & take approval from R-Infra for limit values.

v. Rate of change /Gradient All telemetered and calculated analog points shall be alsoprocessed for rate of change of / Gradient processing , if defined that point for suchprocessing in the database . An Alarm for over shoot & event message for return to normalshall be generated. The rate of change shall be calculated periodically for each assignedpoint, by dividing the point’s values at the beginning and the end of the period into the lengthof the period.. ..

vi. Sign Conventions The sign conventions for the display, data entry and reporting of activeand reactive power flow shall be used universally by all SCADA/DMS functions. All imports tobus bars shall be represented with + sign and all exports from bus bars shall be with –vesign.

vii. Accumulator Processing The system shall be able to store accumulator history. Storingaccumulator history shall be provided with a method in which that stores data only once perhour and in other method that stores data each time new data enters the system. It shall bepossible to use the two methods concurrently for any pulse accumulator, making it possibleto maintain two records for data that are read more than once an hour.

6.4.2 Digital Input Data processingEach state of a digital input point shall be associated with the state of an actual device. Thenumber of bits that will be used to define the state of a device is defined in the RTU/FRTUSpecification.A status point shall be defined as being either legal or illegal, and normal or abnormal:

Illegal state: The first check on a new input to a digital status point is the legalitycheck. If the new state is illegal, then the old value shall be left in the database andmarked old with relevant quality code such as telemetry failure etc.

43

Abnormal state: If the new state is legal, it shall be checked to see if it is among thenormal states defined for the point. If not, the status point shall be marked as abnormal.While abnormal, it shall appear in the summary display of abnormal conditions/ off-normal summary

Alarm checking: Each new value shall be checked to see if transitions into that stateare to be alarmed. If so, and if no control action is pending on the status point, then analarm action shall be triggered. The following digital input data types shall beaccommodated as a minimum:

a. Two-state points: The following pairs of state names shall be provided as minimum:1) Open/Closed2) Tripped/Closed3) Alarm/Normal4) On/Off5) Auto/Manual6) Remote/Local7) On Control/Off Control

b. Three-state points: Any of the state combinations listed in (a) above shall besupported with a third, typically, in-transit state which is the case for slow operatingdevices such as isolator. If a device remains in this state for a period more than athreshold value, the same shall be alarmed.

Momentary change Detection (MCD): The input to capture the states of fast actingdevices such as auto recloser.

Commanded changes initiated by supervisory control shall not be alarmed but shallgenerate an event message. All other status changes in the state of telemetered,calculated digital input points & uncommanded changes shall be alarmed. Each CB,isolator switching device etc shall have normal & off normal positions states defined. Inthe event of off normal positions, the same shall be reflected in the off normal summarylist.

6.4.3 Calculated Data processing SCADA system shall be capable of performing calculations and storing the result in the

database as calculated data available for display. The database variables to be used for arguments and the

mathematical/statistical/logical functions to be used as operations shall be definableinteractively at a console as well as by the programmer using database creation andmaintenance procedures.

Calculated analog values shall use database points as the arguments andmathematical and statistical functions as the operations.

Functions such as addition, subtraction, multiplication, division, maximum value,minimum value and average value, count, integration, square root extraction,exponentiation, trigonometric functions, logarithms and logical & comparative operatorsetc shall be provided.

It shall be possible to calculate running maximum value, minimum value and averagevalue over a time interval (time interval configurable from 5 minutes to 60 minutes). Thevalue shall be reset after the elapse of defined time interval. These values shall bestored with time of occurrence for maxima and minima and the time for averaging.

Calculated status values shall use database points as arguments and combinationallogic functions that include the logical, comparative operators such as AND, inclusiveOR, exclusive OR, NOT, Less Than, Greater Than, Less Than or Equal To, GreaterThan or Equal To, and Equal To ,If , else if etc. Suitable rules or operators (such as

44

multi-level parentheses) shall be provided to indicate the sequence of operations in thecalculation.

6.4.4 Substation Topology Processing The SCADA /DMS system shall be provided with a Substation topology processor

function. This function shall be capable of analyzing the open/closed status of switchingdevices, such as breakers and disconnectors, in order to define the configuration of thesubstation for display.

The energization of lines, transformers, bus sections and generating units shall bedetermined so that the associated displays may correctly show the status of thesepower system elements.

The configuration shall be re-evaluated and updated whenever a switching devicestatus change & analog value change beyond deadband is detected.

6.4.5 Alternate source for data: The system shall have capability to accept multiple data sources by defining as main &

secondary. Normally, data from normal source will be considered. In the event of nonavailability of primary source, data from secondary source shall be considered & onceprimary source is healthy, it shall switch back to primary source.

There shall be an indication for primary /secondary source in displays, reports etc.Suitable alarm shall be generated in the event to change from primary to secondary &vice versa.

Alternate source of data can be defined for certain critical points in the database.

6.4.6 Quality Codes Quality codes indicate the presence of one or more factors that affect the validity of a

data value. All quality codes that apply to a data value shall be maintained in thedatabase for that data value.

The quality of the calculated value shall be the quality of its "worst" component of itsarguments. The presence of a quality code on any of the component data values shallnot disrupt the calculation using that value.

Results of calculations that are manually overridden by the user shall be denoted with aquality code that can be differentiated from the propagation of a manual replacedquality code from one of its component values.

At least the following data quality codes preferably as the following single letter codeshall be provided. However, distinct symbols /shapes after approval from employer mayalso be used.

Quality code Code Reason

Telemetry Failure (RTULink) T Telemetry has failed

Manual Replaced M Manual updation

Delete fromScan(RTU/point) D User disabled the scan of the data/point

45

Questionable data Q Analog values of the de-energized elements

Calculated C Calculated data

Estimated E Estimated data from State estimator

Limit Override L Limits are overridden

Primary/SecondarySource P/S Primary & Secondary source

Reasonability limitExceeded R Value beyond reasonability limit

Alarm inhibit A Alarm processing in inhibited

Test or Maintenancemode X Point is in test/maintenance mode

6.5 Continuous Real-time data storage and playback It shall be possible to playback the ISR stored data on single line diagram and network

diagram for a time window of at least 10 minutes (configurable in seconds /minutes) bydefining Start and End date and time.

It shall be possible to have tabular and graphical trends of the stored data. It shall be possible to set a different sampling rate for playback than the sampling rate

for data storage. The users shall be able to select the time window of interest for archival of data in the

ISR system for future retrieval and playback in SCADA system. This archived data shallbe transferable in RDBMS database tables of ISR system for generation of tabulardisplays and reports.

6.6 Sequence-of-Events data Sequence-of-events (SOE) data shall be chronological listings of “status change events

with time stamp” acquired from RTUs /FRTUs. The SOE data shall be collected from all RTUs/FRTU either in normal polling or

periodically/on demand. SOE data collection shall have lower priority than supervisory control actions and

normal data acquisition. The SOE data collected from different RTUs/FRTU shall be merged for chronological

listings and stored for subsequent review. At least latest 1000 SOE data shall be available for display.

6.7 SCADA language The SCADA system shall have capability to write various programs using IEC 61131-3

SCADA language or C/C++ or any non proprietary language. It will facilitate user(programmer) to write various programs/ logics using points defined in the database.

46

6.8 Supervisory Control The operator shall be able to request digital status control, set-point control and

raise/lower control on selected points and analogs using Select check before operate(SCBO) Sequence.

Functional requirements for the various types of supervisory control are given below. Asupervisory control request shall be sent from control centre only after the controlledpoint was checked for proper conditions. The request shall be rejected by the Systemif:

(a) The requested control operation is inhibited by a tag placed on the device;(b) The device or S/S in local manual control mode(c) An Uninitialized, Telemetry failure, delete from scan, manual replaced,

Test/maintenance, or Manually Entered data quality indicator is shown for thedevice;

(d) The Operating Mode/ user permission of the workstation/console attemptingcontrol does not permit supervisory control

(e) The device is already selected for control request or control execution is fromanother workstation / user/window /console or control request is progressing

(f) Time out after selection(g) The device is not subject to supervisory control of the type being attempted

6.9 Information Storage and Retrieval Information Storage and Retrieval (ISR) function shall allow collection of data from real-

time SCADA/DMS system and storing it periodically in a Relational databasemanagement system (RDBMS) database as historical information (HI) data.

This includes storing of data such as SOE, status data, Analog values, calculatedvalues, Energy values etc.

Programmer shall also be able to set storage mode as by exception in place of periodicstorage. Subsequently, the data shall be retrieved for analysis, display, trending andreport generation.

All stored data shall be accessible from any time period regardless of changes made tothe database after storage of that data (e.g., it shall be possible to retrieve stored datafor a variable that no longer exists in the SCADA/DMS computer system through backups on storage medias viz. tapes /MO disks etc and initialize study-mode DMSfunctions with stored data on the corresponding power system model).

It should be able to compress data, and should have 100% retrieval accuracy.However, the retrieval of compressed historical streams should be of the sameperformance levels as normal SCADA retrieval.

SQL-based language shall be used for selecting, retrieving, editing, sorting, analyzing,and reporting ISR data stored. The selection and sorting criteria shall include time tagsand ranges, station names, point names, equipment types, status values, text stringmatches on selected data fields etc and combinations of these criteria.

The ISR shall have retention of minimum 1 year data (events & measurands) foranalysis, display, trending and report generation

The ISR system shall also be used for mass storage of data/files such as DMSapplication save-cases, Output results of DMS applications, Continuous real-time dataof selected time window etc. Following reports shall be available in ISR function:

(a) Circuit breaker status report

47

(b) Real-time Database Snapshot report s(c) Hourly Data report s(d) Missed Hourly Data Storage(e) Hourly Data Calculations(f) Daily Energy Data report(g) Load priority report(h) SOE data table

6.10Historical Information (HI) Data Retrieval The data stored in the ISR system shall support the following retrieval capabilities: The user shall be able to view and edit HI data on displays/Forms and reports. The

user shall be able to edit HI data, request recalculation of all derived values, andregenerate and print any daily, weekly or monthly HI report for the current and previousmonth.

The user shall be able to view tabular trend and graphical trend of multiple data pointssimultaneously by specifying the start date and time, the end date and time, and thetime period between displayed samples. The duration of viewable tabular trend andgraphical trend could be up to 24 hours. The features of Tabular/graphic trend ismentioned in the specification for User interface.

The HI retrieval shall expose the ISR Data over ODBC Interfaces / Adapters. The retrieval shall provide 100% accuracy and fidelity of data.

System Message Log Storage and Retrieval System message log, which shall consist of the chronological listing of the

SCADA/DMS computer system event messages and user messages shall be stored forarchival and analysis. Each entry shall consist of time tag and a text containing userand device identification as displayed on the Alarm Summary or Event Summarydisplays.

The System message log data storage shall be sized for up to 20,000 entries permonth. Message log data shall be stored in daily tables & shall be available forminimum two months on auxiliary memory.

System message log data for previous months shall be configured for automaticbackup on Magnetic tapes/ MO disks and any errors can be reported. Option of TakingManual backups shall be provided as per requirement of the system Admin.

Facilities to sort and selectively display and print the contents of the system messagelog shall be provided. The user shall be able to select the display of system messagelog entries based upon Alarm type, Events, User generated messages, Device, andTime period.

7 DMS functions

7.1 General RequirementsDistribution management System Software shall include the following applications. Network Connectivity Analysis (NCA) State Estimation (SE) Load Flow Application (LFA)

48

Voltage VAR control (VVC) Load Shed Application (LSA) Fault Management and System Restoration (FMSR) Loss Minimization via Feeder Reconfiguration (LMFR) Load Balancing via Feeder Reconfiguration (LBFR) Operation Monitor (OM)

7.2 Contractor’s Standard productThe bidders are encouraged to supply standard, unmodified products that meet orexceed the Specification requirements. These products may be provided from thebidder's in-house baseline offerings as standard products from other establishedsuppliers. Bidders shall describe all standard, unmodified products proposed and shallhighlight those features that exceed the Specification requirements. Although thebidder is encouraged to use as much standard hardware and software as possible, theproposal will be judged by its conformance to the Specification. Hence, a minimumlevel of customization in order functional requirement is permitted.

7.3 Graphical & Tabular display requirements for DMS functions A network overview display of the distribution system with substations, feeders colour

coded by voltage shall be provided. This display shall present the distribution system in a graphic format. Telemetered and calculated values like active and reactive power flows etc shall be

displayed with direction arrow. Lines, Loads, transformers etc that have exceeded their loading limits shall be

highlighted. Stations shall be depicted by suitable symbols which reflect the presence of alarms. Cursor selection of a station symbol shall result in display of the associated Single line

diagram for that station. “ What if “analysis shall be included to visualize network & verify the impact before an

action is taken by dispatcher. This facility shall be provided using Study database. For all switching actions which dispatcher have to execute manually/step by step shall

have the option to simulate switching operations in order to visualize the effect on thedistribution network using what if analysis.

All DMS result tabular displays shall have capability for sorting by name and calculatedparameters. The solution prescribed by DMS application shall consider & identify & sortthe following as minimum

1. Remote controllable circuit breaker with capability to interrupt fault currents2. Non-remote controllable circuit breaker with capability to interrupt fault currents3. Remote controllable circuit breaker with no capability to interrupt fault currents4. Non-remote controllable circuit breaker with no capability to interrupt fault currents.5. Remote controllable disconnector6. Non remote controllable disconnector .7. Fuse8. Ground/ Earth switch etc Sectionizer

7.4 Network Model The DMS applications shall have a common model for the project area comprising of

primary substation feeders, distribution network and devices with minimum 10 possibleislands, which may be formed dynamically.

49

All DMS applications shall be able to run successfully for the total distribution systemwith future expandability as envisaged under the specification. The following devicesshall be represented in the model as a minimum:a. Power Injection pointsb. Transformersc.Feedersd. Load (balanced as well as unbalanced)e. Circuit Breakersf. Sect ionizersg. Isolatorsh. Capacitor banksi. Reactorsj. Generatorsk.Bus barsl. Meshed & radial network configurationm. Line segments, which can be single-phase, two-phase or three-phase and make up

a distribution circuit.n. Conductorso. Grounding devicesp. Fault detectorsq. Operational limits for components such as lines, transformers, and switching

devices. All DMS applications shall be accessed from graphic user interface through Operator

consoles as defined in this specification. Reports, results and displays of all DMSapplication shall be available for printing at user request.

Population and maintenance of the distribution network model should be possible byusing the database maintenance tools to build the database from scratch.

In case the required data already exists within the Employer’s corporate GeographicInformation System (GIS), the DMS database functions should leverage this effort byproviding an interface/adaptor to extract GIS data and automatically generate the completeNetwork Operations Model. The data extracted should include network device information,connectivity, topology, nominal status and non-electrical data such as cable, land base dataetc.

Further Land base data can be sourced from GIS in Shape files or DXF.. Any GIS model should be extractable to build the network model regardless of the

supplier or internal schema. The extraction should also allow incremental updates & global transfer with no need to

bring the system down or even fail over. The model should support extraction on a per-station basis and must be fully scalable

from a single zone substation to the largest distribution networks. SCADA/ DMS should be able to present geospatial data even when the link to the

source GIS at the data center/DR is not available. The user interface supporting the database will provide updated data directly to display

geographic and/or schematic views of the network. The model should support multiple geographic coordinate sets for each device so that,

if available, the network can be displayed in custom geo-schematic formats. The network views may also include various levels of detail depending on the zoom

level. Information such as land-base data (provided as a dxf file, shape file etc) mayalso be displayed as required.

An interface with the already existing Geographical Information Systems shall bedeveloped using interoperability features between the DMS and the installed GIS.

50

Each of the two systems shall keep its own specificity, and shall be used for what it hasbeen designed: the SCADA for the real-time data acquisition, control and processing,the GIS for the maintenance of the network construction and geographic data.

The interface shall be developed in order to obtain a maximum benefit of the twosystems use.

It shall be implemented while maintaining the SCADA/DMS and GIS integrity as individualsystems. It is of the utmost importance that the two systems remain able to operateseparately.

Data exchanges shall be made through the Control Center LAN/WAN. Bidder shall demonstrate its incorporation capability to the main GIS Vendors through a

dedicated reference list or provide and support standard interfaces to GIS.

7.5 Network Connectivity Analysis (NCA) The network connectivity analysis function shall provide the connectivity between

various network elements. The prevailing network topology shall be determined from the status of all the switching

devices such as circuit breaker, isolators etc that affect the topology of the networkmodeled.

NCA shall run in real time as well as in study mode. Real-time mode of operation shalluse data acquired by SCADA. Study mode of operation will use either a snapshot ofthe real-time data or save cases.

NCA shall run in real time on event-driven basis. In study mode the NCA shall run onoperator demand. The topology shall be based on

a) Tele-metered switching device statusesb) Manually entered switching device statuses.c) Modeled element statuses from DMS applications

It shall determine the network topology for the following as minimum.a) Bus connectivity (Live/ dead status)b) Feeder connectivityc) Network connectivity representing S/S bus as noded) Energized /de-energized state of network equipmentse) Representation of Loops (Possible alternate routes)f) Representation of parallelsg) Abnormal/off-normal state of CB/Isolators

The NCA shall assist operator to know operating state of the distribution networkindicating radial mode, loops and parallels in the network.

Distribution networks are normally operated in radial mode; loops and/or parallel maybe intentionally or inadvertently formed.

A loop refers to a network connectivity situation in which there exist alternative powerflow paths to a load from a single power source.

A parallel refers to a topological structure in which a load is fed from more than onepower source. Parallel paths often result in circulating currents and such operatingconditions need to be avoided. All loops/parallels in an electrical network shall beshown by different colors in such a way that each is easily identifiable.

Abnormal state of CB/Isolators means these devices are not in their Normal OPEN orCLOSED position.

Alarms shall be generated when presence of abnormal switches, De-energizedcomponents of network and of Network loops / parallels is detected

51

7.5.1 Tracing NCA function shall also have the capabilities of network tracing when requested by the

dispatcher. Dedicated colors shall be used for feeder and circuit tracing and also wheninformation available is not complete or inconsistent.

The trace shall persist through subsequent display call-ups, until the operator explicitlyremoves it or requests another trace.

In addition, at the bottom of the geographic view the number of transformers andcustomers passed by the trace are shown.

a) Feeder tracing - This feature shall aid dispatcher to identify the path from a source to allconnected components by same color.

b) Circuit tracing- This feature shall enable operator to select any device and identify thesource and path by which it is connected through the same color.

c) Between Tracing: This feature shall enable the operator to select any two components ofthe network and shall able to trace all components connected in between them.

d) Downstream Trace – from a selected circuit element the trace identifies all devices thatare downstream of the selected element. In the case where a downstream trace isperformed on a de-energized section of the network, the trace highlights all deviceselectrically connected to the element.

7.5.2 Temporary Modifications:The NCA will allow temporary modifications at any point in the distribution network tochange the network configuration, to isolate faults, restore services or performmaintenance. A Summary shall list the jumpers, cuts and grounds that are currentlyapplied. The function is performed by the NCA and is implemented locally within the clientsoftware and has no effect on the operations model or other clients viewing the network.

CutsCuts facilitated in any line segment in the network. The cut may be applied to one ormore available phases of the conductor. The cut could also be applied as a temporaryswitch inserted in the line.The cut must be given a name or id number for identification, which is displayed as alabel on the geographic network view. It should be possible to select the position of thelabel relative to the cut symbol. The position can be altered after the cut has beenplaced. Once placed the cut symbol can be selected and switched on and off by theoperator in the same way as a standard disconnect switch. Cuts can also be tagged.

JumpersJumpers are a means of providing a temporary, switchable connection between twopoints on the network. The operator should be able to select two points and place thejumper with relevant details. The initial state of the jumper may be set to open or closed.The jumper popup automatically defaults to show the phases available for connectionbetween the two points but other partial or cross-phase connections may be made ifrequired. The popup shall warn the operator about abnormal connections such as not allphases being connected or the nominal voltage being different at the two connectionpoints. Once the jumper has been placed the switch symbol in the center can beselected and switched open or closed. The topology of the network model is updatedaccordingly. There is no restriction on the placement of jumpers between linesconnected to different feeders or different substations. Temporary connections betweenphases on the same line segment, known as a phase jumper shall be supported. This

52

can be used in conditions where one phase is de-energized and it is desired to restorecustomers by energizing the dead conductor from one of the live phases.

Temporary GroundsTemporary grounds should only be placed, for obvious reasons, on de-energizedsections of a line. These grounds represent the mechanical grounding of lines for safetypurposes during maintenance or construction.A temporary ground may be placed on one or more of the available phases. It must begiven a name and addition information can be included in the description field. If a linesegment is reenergized while a temporary ground is still applied, the ground shall bemanually removed.

7.5.3 Reports and DisplaysThe reports and displays shall be generated indicating the followings as a minimum:a) Abnormal switches in tabular displayb) De-energized components of network in tabular displayc) Presence of loops & parallels on network displaysd) Un-served/ disconnected loads (loads affected due to tripping of CBs) in tabular displayse) List of temporary jumpers/cuts /grounds

7.5.4 State Estimation The primary function is to determine network state where SCADA system monitoring is

directly envisaged. The State Estimation (SE) shall be used for assessing (estimating)the distribution network state. It shall assess loads of all network nodes, and,consequently, assessment of all other state variables (voltage and current phasors ofall buses, sections and transformers, active and reactive power losses in all sectionsand transformers, etc.).

Firstly, the symmetrical (per phase) and asymmetrical (three-phase) load of all nodes inthe radial or weakly meshed MV network, which are not remotely monitored, that is notdirectly covered by the SCADA System shall be using evaluated Load Calibration. SErepresents the basic DMS function, because practically all other DMS AnalyticalFunctions are based on its results. This is the unique function dealing with theunobservable load of the actual network, which is not directly covered by the SCADASystem.

Function is used for balanced and unbalanced networks. The function is based on analgorithm specially oriented towards distribution networks, with low redundancy of realtime, remotely monitored data.

The deficiency of real time data has to be compensated with historical data. Beside theparameters of network elements, the real time data consists of:

1) Actual topology, transformers tap changer position, etc.2) Voltage magnitudes of supply point and other nodes in the network.3) Current magnitudes (active and reactive power) at feeder heads.4) Current magnitudes (active and reactive power) from the depth of the network.

The historical data of the network consists of:1. Daily load profiles – current magnitudes and power factors, or active and

reactive powers for all load classes (types, for example: industrial, commercial,residential), for all seasons (for example: winter, spring, summer, autumn), fore.g. four types of days

53

2. Peak-loads for all distribution transformers and/or consumers (peak-currentsand/or peak powers) and/or monthly electric energy transfers across alldistribution transformers (consumers).

SE function shall run in all cases from the range of networks where all historical dataare known, but also in networks with no historical data available (based on parametersof the network elements). Also according to users setting, the SE function shall be ableto run:

With or without verification of telemetered measurements. With manual or automatically processing unobservable parts of network. With or without fixed measurements.

This shall have real time & Simulation mode both. In the first one, the function shall beused for estimation of the current state. In the Simulation mode, the function is used forestimation of the desired state (e.g. any state selected from the saved cases).

The SE algorithm shall consider into account the non availability of real time data andcompensates them with historical data, pseudo and virtual measurements, to achievethe minimal set of input data necessary for running a consistent Load Flow.

The SE algorithm shall consist of the next important steps:1. Pre-estimation – It shall be based on the historical data of the network: daily load profiles,

peak-loads for all distribution transformers and/or consumers, etc. This step shall give pre-estimated states of considered MV networks.

2. Verification of measurements– It shall be obtained from artificially redundancy ofmeasurements (too small number of measurements and notable main number of pseudomeasurements obtained from first approximation). This step shall consider two sub-steps: (a)in sighting evidence bad measurements(b) verification and/or correction all permanent measurements. In this step, incorrectmeasurements shall be corrected or discarded.

7.6 Load Flow Application (LFA)The LFA shall utilize information including real-time measurements, manually entered data,estimated data together with the network model supplied by the topology function, in order todetermine the best estimate of the current network state. The Load Flow Application (LFA)shall determine the operating status of the distribution system including buses and nodes.The LFA shall take the following into consideration:

a) Real time datab) Manual entered datac) Estimated datad) Power source injectionse) Loops and parallelsf) Unbalanced & balanced loadsg) Manually replaced valuesh) Temporary jumpers/ cut/ groundsi) Electrical connectivity information from the real-time distribution network modelj) Transformer tap settingsk) Generator voltages, real and reactive generationsl) Capacitor/reactor bank ON/OFF status value.

7.6.1 General Characteristics of LF application:The following general characteristics/ capabilities shall be provided as minimum:

54

1) The LF model shall support the different kind of lines such as cable feeders, overheadlines and different kind of transformers having various vector groups & windingconfigurations.

2) Unbalanced & balanced three phase loads connected in radial and non-radial modes.3) Compute voltages and currents and power factor for each phase for every node, feeder

and network devices.4) Compute each phase active and reactive loads and technical losses for the distribution

system as a whole, for individual substations and feeder wise with in telemetered zone.5) Use previous save-case to make new save case or use new snapshots to set the base

case for LF.6) The results of the LF application shall reasonably match with the operating condition in

which the distribution system is stable.7) The LFA function shall be executed in real time & study mode.8) It shall be possible to model load either as a percentage of system load or profile base

load modeling9) It shall be possible to model individual component of load i.e. Active and Reactive parts

7.6.2 Real Time Load Flow Execution:The Real-Time LF function shall be executed:a) on event triggerb) on periodic basisc) on demand basisd) on initiation by other DMS Applications functionse) on placement of Temporary Jumper, Cuts and GroundThe Event Triggered LF execution shall always have the highest priority. The study mode LFfunction shall be executed on a snapshot or save case with user defined changes made tothese cases. The study mode execution of LF Function shall not affect the Real-time modeexecution of LF function. Event Triggered Real Time LF Execution: The LF function shall be executed by

predefined events that affect the distribution system. Some of the events the dispatchermay choose for triggers shall include:8) Power system Topology Change i.e. Alteration in distribution system configuration.9) Transformer Tap Position Change / Capacitive/reactor MVAR Change10) Feeder Over loadings11) Sudden change in feeder load beyond a set deadband

Periodic Real Time LF Execution: The real-time distribution system load flowapplication shall be executed periodically as configured by the dispatcher. The functionshall be executed periodically even if there are no significant changes in the operatingconditions, as some of the power flow outputs shall be required to provide aggregatesummaries (losses, etc.)

On Demand Real Time LF Execution: Dispatchers may initiate the real-time LF functionat any time through dispatcher command.

Real Time LF Execution initiated by other DMS Applications: Other DMS functionsmay initiate the real-time LF function at any time as desired for the execution of therespective functions.

7.6.3 Study Mode Load Flow Execution: It shall provide dispatchers with estimates of kW, kVar, kV, Amps, power losses and

the other information on the distribution system, but not necessarily reflecting its real-time state.

55

In study mode the application should use the same data model and have direct accessof the real time data as necessary.

Study mode load flow shall be used to study contingency cases. It shall provide dispatchers with estimates of kW, kVar, kV, Amps, power losses and

the other information on the distribution system, but not necessarily reflecting its real-time state.

In study mode the application should use the same data model and have direct accessof the real time data as necessary.

Study mode load flow shall be used to study contingency cases.

7.6.4 Load Flow Output:The following output capability shall be provided:a) Phase voltage magnitudes and angles at each node.b) Phase and neutral currents for each feeder, transformers, sectionc) Total three phases and per phase KW and KVAR losses in each feeder, section,

transformer, DT substation & for project aread) Active & reactive power flows in all sections, transformers List of overloaded feeder, lines,

busbars, transformers loads etc including the actual current magnitudes, the overloadlimits and the feeder name, substation name

e) List of limit violations of voltage magnitudes, overloading.f) Voltage dropsg) Losses as specified above

7.6.5 Display and Reports All input and output data shall be viewed through tabular displays and overlay on the

one line network diagram. Tabular displays shall consist of voltages, currents (including phase angles), real and

reactive powers, real and reactive losses as well as accumulated total and per phaselosses for each substation, feeder and project area.

All the overloaded lines, busbars, transformers, loads and line shall start flashing orhighlighted.

The LF outputs shall be available in the form of reports. The report formats along withits contents shall be decided during detailed engineering.

7.6.6 Alarms The LFA shall warn the Dispatcher when the current operating limits are exceeded for

any element or when lines are de-energized. It shall also warn the Dispatcher when any abnormal operating condition exists. Alarms generated during Study Mode shall not be treated as real-time alarms but shall

be displayed only at Workstation at which the LF application is running in study mode.

7.7 Volt –VAR control (VVC) The high-quality coordination of voltages and reactive power flows control requires

coordination of VOLT and the VAR function This function shall provide high-quality voltage profiles, minimal losses, controlling

reactive power flows, minimal reactive power demands from the supply network. Thefollowing resources will be taken into account for voltage and reactive power flowcontrol:1. TAP Changer for voltage control

56

2. VAR control devices: switchable and fixed type capacitor banks. The function shall propose the operator solution up on change in the topology of the

network switching. The function shall consider the planned & unplanned outages, equipment operating

limits, tags placed in the SCADA system while recommending the switching operations. The functions shall be based on user configurable objectives i.e. minimal loss, optimal

reactive flow, voltage limits, load balancing. These objectives shall be selectable on the basis of feeder, substation & group of

substations or entire network. The dispatcher shall have the option to simulate switching operations and visualize the

effect on the distribution network by comparisons based on line loadings, voltageprofiles, load restored, system losses, number of affected customers.

The solution shall identify /sort the different type of switches that are required foroperation i.e. remote /manual etc.

7.7.1 Modes of operationThe VVC function shall have following modes of reconfiguration process:(a) Auto mode(b) Manual mode

The dispatcher shall be able to select one of the above modes. These modes are describedbelow:

1) Auto modeIn auto mode, the function shall determine switching plans automatically and performswitching operations upon dispatcher validation automatically.

2) Manual modeIn manual mode, the function shall determine switching plans automatically and performswitching operations in step-by-step manner. A filter for remote operable & manual switchesshall be provided with switching plan.

7.7.2 ReportsDetailed reports of complete switching sequence for VVC operation, including voltage / VARlevels before switching & after switching shall be presented.

7.7.3 DisplaysThe User interface for VVC function shall have following summary displays as minimum:

Network & tabular display to VVC switching Tabular display giving chronological sequence for VVC operation

7.8 Fault Management & System Restoration (FMSR) ApplicationThe Fault Management & System Restoration application software shall provide assistanceto the dispatcher for detection, localization, isolation and restoration of distribution systemafter a fault in the system. The FMSR function shall be initiated by any change in the networkconnectivity due to any fault. It shall generate automatic report on switching sequence

57

depicting analysis of fault, location of fault & recommendations for isolation of faulty sections& restoration of supply.

7.8.1 Functional RequirementThe FMSR function shall include the following characteristics:1) FMSR shall be capable of handling phase-to-ground and phase-to-phase faults and shall

not be restricted by their time of occurrence on one or more feeders. Thus, the ability tohandle multiple faults of different types, on multiple feeders, shall be provided. It shall becapable to carry out restoration of large area after a occurrence wide spread faultsamounting to substantial outages in the town.

2) FMSR shall be capable of allowing the substitution of an auxiliary circuit breaker or linerecloser that may temporarily function in place of a circuit breaker or line recloser that isundergoing maintenance.

3) The Operator shall be able to suspend FMSR restoration capabilities by activating asingle control point. Otherwise, FMSR shall continue to operate for fault detection andisolation purposes. The Operator shall be able to resume FMSR's normal operation bydeactivating the same point.

4) FMSR shall be capable of isolating faulty sections of network by opening any availableline Circuit Breaker that may be necessary, however operating limitations on device suchas control inhibit flag shall be respected.

5) FMSR application shall utilize the results of LF for recommendations of switching stepsfor restoration where in it should guide the operator for amount of overloading in lines,bus voltage violations and amount of load that can be restored for various options ofrestorations ,the operator shall have the privilege of selecting the best restoration optionsuggested by FMSR before it starts restoration .The operator shall also be to simulate theLF for the recommended switching actions ,so that the necessary violations can bedisplayed on graphical display also. If an overload condition is expected as a result of theproposed switching, it shall be displayed to the operator on a graphical display andproposed alternative switching sequence to avoid or minimize the overload.

6) FMSR shall be capable of using data derived from substation RTUs/FRTUs /FPIs torecognize faults in substation transformer banks, any fault on the primary side of thesebanks that cause loss of outgoing feeder voltage and current or any fault occurred on11KV network.

7) FMSR shall be capable to make Restoration plans with identification name andrespective merit orders & its execution of Restoration plan using network Display andsingle line diagram of substation.

8) FMSR shall be capable to find delay in the restoration of network beyond specified time(Despatcher configurable) and shall be able to report separately in the form of pendingrestoration actions.

7.8.2 Detection of fault FMSR function shall detect the faulty condition of the network causing CB tripping due to

protection operation or FPI indication. The Circuit breakers having auto-reclose feature, the FMSR application shall wait for

programmer specified (settable for individual feeders) duration before declaring the networkas faulty.

On detection of fault in the network, an alarm shall be generated to draw attention of thedispatcher. Switching device tripping caused by SCADA/DMS applications shall not beconsidered as a faulty condition.

58

FMSR application shall also not be initiated if the quality flags such as, manually replacedvalue, Out of scan are set for a switching device.

To avoid potential difficulties during severe storm conditions, the Operator shall be able tosuspend FMSR switching sequence of restoration capabilities by activating a single controlpoint. Otherwise, FMSR shall continue to operate for fault detection and isolation purposes.

The Operator shall be able to resume FMSR's normal operation by deactivating the storm-mode control point. When this occurs, FMSR shall be ready to restore power as well asdetect and isolate faults following the next outage event. The same shall be recorded as anevent.

7.8.3 Localization of Fault: Wherever protection signal or FPI indication is not available, FMSR function shall

determine the faulty section by logically analyzing the telemetered data (status of CBs,analog values etc) as acquired through SCADA system.

Besides this, for such cases an iterative method for determining fault shall be used e.g.In case of fault, upstream breaker is tripped & long stretch of multiple sections arehaving no intermediate fault indicators & intermediate switches are not capable to tripon fault up to the closest NO(Normal open) point, the dispatcher can open the lastswitch before NO point & try to close breaker , if trips again fault is on further upstream& the same method is to be repeated else fault is located in the downstream sectiononly.

For the sections where protection signal or FPI indication is available, the same shallbe derived through these telemeterd signals.

Network diagram identifying the faulty sections/components shall be displayedidentifying the relevant section and various configurations of switch type etc.

Minimum of following switch types shall be considered by FMSR system:1. Remote controllable circuit breaker with capability to interrupt fault currents2. Non-remote controllable circuit breaker with capability to interrupt fault currents3. Remote controllable circuit breaker with no capability to interrupt fault currents4. Non-remote controllable circuit breaker with no capability to interrupt fault currents.5. Remote controllable disconnector6. Non remote controllable disconnector7. Fuse8. Ground/ Earth switch etc

7.8.4 System isolation & restoration Once faulty section is identified, the FMSR function shall determine the switching plan

to isolate healthy area from unhealthy area. FMSR function shall suggest switching plans for restoration of power to the de-

energized healthy sections of the network. It may be done by closing NO switch to allow the power from alternate source. In case more than one feasible switching plans exist, the dispatcher shall be guided for

most optimum plan based on the merit order ie minimum switching operations,minimum loss path, system operation within the safe limits of various networkelements.

The dispatcher shall have the option to simulate switching operations and visualize theeffect on the distribution network by comparisons based on line loadings, voltageprofiles, load restored, system losses, number of affected customers.

The FMSR function shall have feature to attain the pre-fault configuration ondispatcher’s request after repair of faulty sections. The FMSR function shall havefollowing modes of restoration process:

59

a. Auto mode of restorationb. Manual mode of restoration

The dispatcher shall be able to select one of the above modes. These modes aredescribed below:

a. Auto mode of restoration In auto mode, the FMSR shall determine switching plansautomatically upon experiencing fault & proper isolation of unhealthy network fromhealthy part of the network and perform restoration actions upon dispatchervalidation automatically.

b. Manual mode of restoration In manual mode, the FMSR shall determine switchingplans upon experiencing faulty state & proper isolation of unhealthy network fromhealthy part of the network. The switching plans shall be presented to dispatcher forstep by step restoration. Dispatcher shall be allowed to introduce new steps. A filterfor remote operable & manual switches shall be provided with switching plan

7.8.5 ReportsDetailed reports of complete switching sequence from outage to restoration, feeder-wise outage duration with Date & Time stamp, quantum of served & un-served load,number of consumers interrupted & restored and network parameters limits violationsshall be generated by FMSR application

7.8.6 DisplaysThe User interface for FMSR function shall have following summary displays as minimum:

Network & tabular display to identify faulty network Network & tabular display to identify remotely controllable devices Network Display to show plan for Isolation of faulty sections from the network using

single line diagram of substation or network as selected by the dispatcher. Tabular display for Restoration plans with identification name and respective merit

orders & execution of Restoration plan using network Display, and single line diagramof substation

Delay in the restoration of network beyond specified time (Dispatcher configurable)shall be reported separately in the form of pending restoration actions in Tabulardisplay.

List of sections not restored with the reasons for non-restoration such as overloadingand voltage limit violations etc shall be shown in tabular display.

7.9 Loss Minimization via Feeder Reconfiguration (LMFR) This function shall identify the opportunities to minimize technical losses in the

distribution system by reconfiguration of feeders in the network for a given loadscenario.

The technical losses are the losses created by characteristic of equipments & cablesuch as efficiency, impedance etc.

The function shall calculate the current losses based on the loading of all elements ofthe network. The telemetered values, which are not updated due to telemetry failure,shall be considered by LMFR application based on recommendations of LF Application.

Function shall advise the transfer of load to other elements of the network with an aimto minimize the loss.

All such advises shall indicate the amount of loss reduction for present load condition. The LMFR application shall consider the planned & unplanned outages, equipment

operating limits, tags placed in the SCADA system while recommending the switchingoperations.

60

The dispatcher shall have the option to simulate switching operations and visualize theeffect on the distribution network by comparisons based on line loadings, voltageprofiles, load restored, system losses, number of affected customers.

LMFR application shall run periodically at every 15 minutes and on demand. Shortduration Power Interruption to the consumers during suggested switching operationsmay be permitted.

7.9.1 Modes of operationThe LMFR function shall have following modes of reconfiguration process:2) Auto mode3) Manual modeThe dispatcher shall be able to select one of the above modes. These modes aredescribed below:a) Auto modeIn auto mode, the function shall determine switching plans automatically for minimalloss condition in the network and perform switching operations upon dispatchervalidation automatically.b) Manual modeIn manual mode, the function shall determine switching plans automatically forminimal loss condition in the network based on which dispatcher can performswitching operations in step-by-step manner. A filter for remote operable & manualswitches shall be provided with switching plan.

7.9.2 Displays & Reports At the defined periodicity or on demand, the dispatcher shall be presented with

the tabular & graphical displays indicating feeder-wise, substation-wise, projectarea wide technical losses in % before & after the feeder reconfiguration.

The summary report shall also be generated periodically to display technicallosses and possible reduction in losses if dispatcher follows the LMFRrecommended switching operations.

The report shall also highlight violations that are occurring in the network withdisplay layers before and after reconfiguration."

7.10Load Balancing via Feeder Reconfiguration (LBFR) The Load Balancing via Feeder Reconfiguration function shall optimally balance the

segments of the network that are over & under loaded. This function shall help in better utilization of the capacities of distribution facilities such as

transformer and feeder ratings. The Feeder Reconfiguration Function shall be activated either by an overload condition,

unequal loadings of the parallel feeders and transformers, periodically or on demand by thedispatcher.

It shall generate the switching sequence to reconfigure the distribution network fortransferring load from some sections to other sections.

The LBFR application shall consider the planned & unplanned outages, equipment operatinglimits, tags placed in the SCADA system while recommending the switching operations.

The function shall distribute the total load of the system among the available transformersand the feeders in proportion to their operating capacities, considering the discreteness of theloads, available switching options between the feeder and permissible intermediate overloadsduring switching.

61

The dispatcher shall have the option to simulate switching operations and visualise the effecton the distribution network by comparisons based on line loadings, voltage profiles, loadrestored, system losses, number of affected customers.

7.10.1 Modes of operationThe function shall have following modes of reconfiguration process:a) Auto modeb) Manual modeThe dispatcher shall be able to select one of the above modes. These modes aredescribed below:

1. Auto modeIn auto mode, the function shall determine switching plans automatically forload balancing in the network and perform switching operations upondispatcher validation automatically.

2. Manual modeIn manual mode, the function shall determine switching plans automatically forload balancing in the network based on which dispatcher can performswitching operations in step-by-step manner. A filter for remote operable &manual switches shall be provided with switching plan.

7.10.2 Displays & ReportsThe summary report shall cover the followings: Loadings of feeders and transformers before and after reconfiguration. Voltage profile of the feeders before and after reconfiguration.

The report shall also highlight violations that are occurring in the network with displaylayers before and after reconfiguration.

7.11 Operation Monitor The Operations Monitoring function shall track the number of operations made by every

breaker, capacitor switch, reclose, OLTC, isolator and load break switch that is monitored bythe System. Devices shall be identified by area of responsibility, substation, feeder, anddevice ID to provide the necessary information for condition-based maintenance of thesedevices.

Each monitored device shall be associated with a total operations counter. This counter shallbe incremented whenever the associated device changes state.

When a multiple change (such as a trip-close-trip sequence) is reported by an RTU/FRTU,each transition shall be counted separately. In addition, a fault operations counter is required.This counter shall be incremented only for uncommented trip operations.

The date and time of the last operation shall be saved for each device when one of thecounters is incremented.

An Operator with proper authorization shall be able to enter total operations and faultoperations limit for each counter.

An alarm shall be generated when a counter exceeds its limits. No additional alarms shall begenerated if the counter is incremented again before it is reset.

For each counter, the System shall calculate the present number of operations expressed asa percent (which may exceed 100%) of the corresponding limit.

The ability to reset individual counters shall be provided. In addition, a user shall be able toinhibit operations counting for individual devices. Such devices shall be included insummaries based on areas of responsibility.

62

Resetting and inhibiting counters shall be permitted only for devices that belong to the areasof responsibility and resetting shall require the console to be assigned to an appropriatemode of authority.

The user info, date and time, when each counter was last reset shall be saved. The counters and other related information shall be available for display and inclusion in

reports. The user shall be able to view the date and time of a device’s last operation togetherwith its accumulated operations data by simply selecting the device on any display where itappear.

8 Project Management

8.1 Project Management ScheduleVendor shall submit a detailed work plan (Gantt chart) within one week of award of contractindicating Start / End dates of the following milestones

Site survey Initial system design Submission of critical documents for BYPL’s review Detail system design Submission of detailed design documents for BYPL’s review and Approval Manufacturing Testing Shipment Requirement completion date for BYPL’s scope of work Submission of final

technical documentation Site acceptance test. Training. Final acceptance test. Handover of system.

BYPL must approve the schedule before the Project is started. Vendor shall specify theschedule of work to be carried out by BYPL to achieve the milestones as planned. Vendorshall update the work plan incorporating progress highlighting delays, the reasons thereofand the steps to make up the delay.

8.2 Project Organization Vendor shall appoint a Project Manager who is a capable of carrying out the project and

having previous experience of handling similar projects. The project manager shall remainfocal point for communication and coordination between vendor and BYPL

Vendor shall employ on the project experienced workers with high technical knowledge andrelevant experience.

Vendor shall submit the manpower deployment plan along with the bids, describing the keyroles of each persons.

63

9 Testing

9.1 Factory Acceptance Test (FAT) Vendor shall propose, for approval by BYPL, the intended format for the FAT. If multiple

FATs are proposed, vendor shall specify how this system integration and bandwidth capacitywill be tested.

BYPL shall witness the FAT of sample system of each type or each unit. Three weeks prior to proceeding with the testing, vendor must submit for review the system

log, pretest records, and show certificates for test equipment to be used. Vendor shall also submit a detailed schedule of the FAT showing assigned personnel and

location to enable BYPL and BYPL to plan their personnel requirements Vendor and BYPL personnel at successful conclusion of testing shall sign off the FAT results. BYPL personnel shall further ensures that all the functional requirements are met may

perform unstructured tests.

9.2 Site Acceptance Test (SAT) The SAT procedures for the complete integrated system shall be derived from the FAT

procedures, and shall be developed by vendor in consultation with BYPL. The testingprogram shall include contingencies to minimize delays due to any system problems.

Failure of any of these tests will result in an expansion of coverage, of the random tests,when testing resumes following fault solution. The worst-case scenario due to repeated testfailures would result in a requirement for 100% testing subsequent to all remedial action. Thisfeature of the SAT procedure shall be clearly defined in the SAT test program prepared byvendor. The SAT shall be witnessed and signed off by vendor and BYPL / BYPLrepresentative.

Provided there are no software problems, the SAT shall be completed in a logical manner toexpedite the commissioning of the sub-systems and the system as a whole.

9.3 Final Acceptance Test On completion of the above System Operation period, vendor shall submit the system for a

Final Acceptance Test by BYPL during which BYPL shall check the overall performance ofthe system as per the specifications

Only after BYPL is fully satisfied that the system had performed as per the guidelines laiddown and without many malfunctions and problems, shall the system be taken as FinallyAccepted.

The system shall then be handed over by vendor to BYPL.

64

10 System Guarantee10.1 System Guarantee: System guarantee / warranty period will be for 1 year and shall beapplicable from the date of issue of the Handing Over / system completion certificate by BYPL.

10.2 Annual Maintenance Contract: Vendor will also provide Annual Maintenance Contract(AMC) services for the period of 4 years (after OEM warranties).

10.3 Software Updates: Vendor shall ensure software maintenance and version updateswithout any addition to the cost for this as long as the system is operational.

10.4 Special Terms & conditions

o The project implementation schedule shall be not exceed 1 month from the date ofaward

o Vendor shall ensure installation and commissioning of the software with the hardwaresupplied by BYPL.

o Vendor shall provide a letter of support indicating that there will be no hardwareupgrades required for the software supplied for next 10 years.

o During the course of warranty and maintenance apart from guidance, trouble shootingand other standard support, Vendor should ensure availability of updates andupgrades of the product as and when released, Vendor is also responsible for portingall such updates/versions in the servers as required by the BYPL.

o The vendor will supply along with each Software, all the related documentation andsoftware. These will include but not restricted to user manual, operation manual.

o The Software to be supplied will be insured by the vendor against all risks of loss ordamage from the date of shipment till such time it is delivered at the BYPL site.

o The vendor should guarantee that the Software delivered to the BYPL are brand new,including all components. In the case of software, the vendor should guarantee thatthe software supplied to the BYPL is licensed and legally obtained. Software must besupplied with their original and complete printed documentation

o The vendor will be responsible for commissioning all application, software & licenseswith new hardware as details given in Annexure 2 (Hardwares).

o The vendor will be responsible to rectify any bug related issue in the system after orduring the commissioning up to the life period(10 Years) within 8hrs.

Local Support Service

The vendor should be capable of meeting the service & support standards as specified in thisRFP.

65

Vendors are also required to submit along with their offer a detailed support plan providingcomplete details like address of the support center, number of service engineers availablealong with their names, telephone/mobile numbers, fax number.Any issue get addressed to vendor should get rectified with in 6hours from its reported. Afterescalation matrix will be followed at every level of escalation with every 6hours till call getsrectified.

MaintenanceThe bidder should provide dedicated help desk consisting of engineers for Software at centrallocation for problem resolution from 00.00 hrs to 23.59 hrs and on call 24*7 basis overtelephone and Email.

Responsibility Matrix

Item Task BYPL Vendor

1 SOFTWAREPROBLEMRESOLUTION

A R

1.1 Report problem andassist with problemidentification

A R

1.2 Provide or recommendcorrections, temporarypatches,workarounds or otherfixes to systemproblems

A R

1.3 Install and testcorrections, temporarypatches,workarounds or otherfixes to systemproblems

A R

R indicates who has primary responsibility to perform this function.A indicates who will provide assistance.

11 Applications To be Developed SCADA –GIS Integration SCADA-OMS Integration SCADA-Sap Integration

66

Load Shedding Application Under Frequency Load Shed Application SCADA-AMR Integration Peak Load of each feeder on Daily/Monthly/Yearly Basis Fault location Integration through Numerical Relays & GIS.

12 TrainingThis section describes general requirements that apply to all training courses. The Contractorshall submit the training proposal along with the bid. The training content, schedule and locationshall be finalized during project execution.

12.1Generala) Training will be conducted by Contractors personnel, who are experienced instructors and

speak understandable English.b) All necessary training materials shall be provided by the Contractor. Each trainee shall

receive individual copies of all technical manuals and all other documents used for training.c) Class materials, including the documents sent before the training courses as well as class

handouts, shall become the property of BYPL. Employer/BYPL reserves the right to copysuch materials, but for in-house training and use only.

d) Hands-on training shall utilize equipment similar to that being supplied under the contract.e) For all training courses, the travel and per-diem expenses will be borne by the BYPL.f)The Contractor shall quote training prices under project management cost. & shall be

included in the bidg) The schedule, location, and detailed contents of each course will be finalized during

employer and Contractor discussions shortly after placement of the award. TheConsultant/Employer shall review and approve the contents of the overview training prior tothe start of the training.

12.2 Training Course RequirementsEmployer's training course requirements are described below in terms of the contents of eachcourse to be provided. Training shall be provided on actual database for the applicationsoftware course and the associate training courses.

12.2.1 Database, Display Building & Report generation Course The database and display building course shall be the first course to be given in the overall

training sequence. It shall be a hands-on course using the hardware and software to be supplied by the

contractor. The course shall be designed to train BYPL personnel in how to develop the databases,

displays, reports, and logs for the offered system. Course objectives shall include:d) How to set up a database & display development systeme) How to identify database fields, entries, records, tables, and contentsf) How to structure RTU /FRTU table definitionsg) How to build tables, arrays, and report formats and displays.h) How to perform database maintenancei) How to generate the database from source informationj) How to maintain symbol libraries, display colour groups, and display string lists.

67

On course completion, all participants shall be able to prepare the necessary input data todefine the system operating environment, build the system database and displays, andprepare the database administrator to maintain and modify the database and its structures.

12.2.2 Computer System Software CourseThe computer system Software course shall be offered, at the system level only. The trainingcourse shall be designed to give BYPL software personnel sufficient knowledge of the overalldesign and operation of the system so that they can correct obvious problems, performpreventive maintenance, run diagnostic programs. The following subjects shall be covered:

1. Operating System: Including the user aspects of the operating system, such asprogram loading and integrating procedures; scheduling, management service,and R-Infra functions; and system expansion techniques and procedures

2. System Initialization and Fail over: Including design, theory of operation, andpractice

3. Diagnostics: Including the execution of diagnostic procedures and theinterpretation of diagnostic outputs,

4. Operational Training: Practical training on preventive and corrective maintenanceof all equipment, including use of testing tools.

12.2.3 Application Software CourseThe Contractor shall provide training on Application software courses covering allapplications other than those already covered above. The training shall include:

a) Overview: Block diagrams of the application software and data flows.Programming standards and program interface conventions.

b) Application Functions: Overview of Functional capabilities, design, and algorithms.Associated maintenance and expansion techniques.

c) System Programming: An introduction to software architecture, Effect of tuningparameters (OS software, Network software, database software and ApplicationSoftware etc.) on the performance of the system. Administration of Database(both real-time and RDBMS),

d) Software Documentation: Orientation in the organization and use of systemsoftware and Application software documentation.

e) Hands-on Training: shall be provided with allocated computer time for traineeperformance of unstructured exercises and with the course instructor available forassistance as necessary.

12.2.4 Operator Training CourseThis training course shall provide training to BYPL’s operators on SCADA/DMS Systems sothat operators can manage the system effectively. The training shall include:

a) System Overview: Configuration of the system, a functional overview, and anoverview of system capabilities and performance.

b) General Operating Procedures: Hierarchical structure of displays, displaycapabilities and features, user procedures, log-on and user access restrictions,and error messages.

c) System Applications: Theory of operation, capabilities, and operating proceduresfor each application function.

d) Handling of Equipment: Minor maintenance operations, such as removal of stuckpaper in printers etc., which do not require spares/specialized skills.

e) Operator Documentation: Orientation in the organization and application of alluser documentation for Operator and verification of the information containedtherein. The course shall focus on hands-on training on the system.

68

13 Details of Existing GIS

GIS in BSES Yamuna Power Ltd. (BYPL) Distribution Business:

BSES Yamuna Power Ltd. has implementing Enterprise wide Geographic InformationSystem (GIS) for managing its distribution business electrical network efficiently. The mainobjective of GIS implementation was to provide a workspace through which the organizationat large could easily access the vast amount of asset and facilities information necessary tomanage, operate and maintain its electric distribution system.

The GIS implementation was planned in a way to achieve greater operational efficiency infacility management & reduced emergency response time. GIS system keeps track ofphysical assets (@ 2.8 million features covering entire LT & HT Network), dynamic electricalnetwork topology/connectivity right from Grid Station to Consumer delivery Points.

The prime objective of the GIS is to provide data to users in more interactive manner usingsimple user interface, it will acts as central database for all department. The GIS provideflexibility to the user to carry out various analyses and create different scenarios virtuallywithout physically going to the site.

Now GIS has become one of the mainstream IT systems in day to day life BYPL distributionbusiness. Beside Facility management & network representation, GIS addresses specific setof problems/needs of users from various departments. Following are few applications whereGIS has been integrated in mainstream business operations/processes.

o U/G Cable Fault Locating / Managemento Proposal/Estimate Creationo Energy Auditing & Accountingo Network analysis, network planning and designo Outage Managemento Web based interface for data access

GIS is integrated with the rest of IT systems like ISU-CCS (Consumer/Billing InformationSystem), SCADA system (ABB, Network Manager), AutoCAD Map (AutoDesk) & ERPsystem (SAP). Interface has been developed with third party Analysis software (Cymdist fromCYME International) enabling planning engineer to perform following analysis on GISexported feeder network.

o Load Flow Analysiso Short Circuit Studieso Contingency Analysiso Switching Optimizationo Optimal Capacitor Placemen

69

BYPL GIS Software include following:

ESRI suite of Application: ArcSDE 9.3.1, ArcGIS 9.3.1 SP 2, ArcSchematics 9.3.1, NetworkAdapterTM&M suite of applications: ArcFM 9.3.1 SP1, Conduit Manager, Responder 9.3.1 (OMS).Database: RDBMS: Oracle 9.2.0.5 running on Sun Solaris 8Web Application: ESRI Arc IMS, ARC GIS Server 9.3.1Network Analysis Software: CymDIST 5.0

14 Details of AMR

Automatic Meter Reading (AMR) system introduces online Computerized data monitoringand logging system for all the Grid stations under BSES Yamuna Power Ltd.

This System provides the following features:1. Monitoring and logging of the following parameter is respect of all incoming and outgoingfeeders integrated on 15 minute basis:

2. Alarm feature to draw attention of the operator to any breach of various parametersbeyond specified limits.

3. Facility to generate spread sheet and MIS reports for the followinga. System Outage / Down time of the feeders,b. Energy Audit,c. Daily Peak loadsd. Voltage Profiles,e. Daily Log Sheets

4. The system to have capability for time synchronizing for each and feed meters from thecentralized base station.

5. Event information e.g. voltage failures, exceeding of threshold, error message or be

made available.

6. The availability based Tariff (ABT) based reports consisting of demand and frequency

average for 15 minutes.

Sub modules of AMR

Raw Data Process System Control Automation Energy Management System

70

Grid Balancing

BSES AMR Includes the following :

Front end: Designed in Visual Basic 6.0 and JavaScript Back End: Oracle 9i Operating System: This application is designed on Windows operating system XP,

but application can run on any of operating system. Database Connectivity: Automatic Meter Reading (AMR) access data from AMRDB Database Server. AMR performs all transactions with AMRDB Database

server. Login Details: There is a user login requirement to access the application. User id

and password is authenticated through Admin Console.

15 Details of OMS

The Outage Management System monitors and analyzes the whole process of faultrestoration, from the receipt of consumer’s complaint to the normalization of supply includingtracking of resources, in the power distribution and power supply system.This system has been divided in two parts

11 KV and Below EHV (Extra High Voltage)

There are seven modules related to OMS as following-:

CMS- COMPLAINT MANAGEMENT SYSTEM DOMS-DISTRIBUTION AND OPERATION MANAGEMENT SYSTEM EMS-EHV MANAGEMENT SYSTEM ORM-OPERATION REPORT MANAGEMENT SLMS-STREETLIGHT MANAGEMENT SYSTEM MND-MAPS AND DRAWINGS GIS-GRAPHICAL INTERFACE SYSTEM

Features of outage management system

• The process of operation and maintenance of 11KV and below is at present centralizedat the circle level.

• The consumer makes a complaint at the centralized Call Center / complaint center, forlodging his complaints.

• As soon as the complaint is registered in the system, the complaint gets sorted outCircle-wise and is forwarded to the respective Circle-Control.

71

• The Circle-Control passes on these complaints to the respective Complaint Centersdivision Offices for attending to them.

• It further monitors and analyzes these complaints through the outage managementsystem installed with them.

• There is further a Central Monitoring Cell located at Nehru Place where the complaints ofall the circles are monitored using the OMS.

• The system is further installed at higher management level for viewing the status.

Application Status• Front End: Microsoft Visual Basic 6.0• Back End: Oracle 9i.• Operating System: This application is designed on Windows operating system but

Application can run on any of windows operating system.• Network Connectivity: OMS application is standalone application, which runs on any

of Windows operating system. The connectivity requirement for OMS is LAN because thedatabase server is on network.

CPU : Intel Xeon Four Core E5-2609 better should be configured as

Proposed Hardware for BCC to be provided by BSES Yamuma Power Ltd

Annexure 1 Specification for Server Chassis

S.No. Item Specification Qty.

1 Server Chassis

Form Factor : Max 10U Rack mounted Chassis to house at least 14 Compute Nodes. Processor Supported :Chassis should support all Intel E5-2600 and E5-4600 series processor. IO Modules : Min Four high-speed switch bays capable of supporting I/O architectures in Ethernet, Fiber Channel, FCoE and Infiniband. Ethernet IO Module (1GB) : 2 x 1/10 GBPS Ethernet switch with L2 and L3 capabilities, VM ready support for 802.1Qbg standards. Each Switch should be configured with a minimum of 10 x 1G uplinks and should be scalable to provide at least 60GB uplink capability or vendor should be able to configure enough available ports to provide for 60Gb uplink bandwidth with redundancy. Midplane : Chassis should have a highly reliable mid plane for providing connectivity of the shared resources to the compute nodes in a highly reliable manner. Power Modules : Redundant power modules the provide N+N or N+1 redundancy. Chassis Management Module : Integrated two redundant chassis Management Modules providing IP based management of the compute nodes and vital elements like FC and Ethernet Switches. Should also provide for controlling Power, Fan management, Chassis and compute node initialization, Switch management, Resource discovery and inventory management, Resource alerts and monitoring management, Chassis and compute node power management and diagnostics for elements including Chassis, I/O options and compute nodes. System Panel : LEDs on the front information panel that can be used to obtain the status of the chassis Identify, Check log and the Fault LED. Support for Multiple Platform :Should provide support for multiple platforms in x86 and RISC servers within the same enclosure.

2

Annexure 2: Specification for Blade Server


1 Blade Server

CPU : Intel Xeon Four Core E5-2609 CPU @ 2 4 GHz or better should be configured as CPU @ 2.4 GHz or per the schedule given in Annexure 1. The server should have minimum 2 CPU sockets. Cache L3 per processor : 10 MB of L3 Cache. Chipset : Intel Chipset C600. Memory :

To be 23

Annexure 3: Specification for Rack Server


1 Rack ServerCPU : Intel Xeon Four Core E5-2407 CPU @ 2.2 GHz or better should be configured as per the schedule given in Annexure 2 of Hardware BOM. The server should have minimum 2 CPU sockets. Cache L3: 10 MB of L3 Cache per processor. Chipset : Intel Chipset C600.

5

Specification for Firewalls


1 FirewallSecurity Features : Symmetric Multiprocessing-based data forwarding.Hardware-based control and data plane separation.Six on-board 10/100/1000Base-T Gigabit Ethernet ports. Four on-board SFP Gigabit Ethernet ports.Support for dual AC or dual DC power suppl

4

Specification for L3 Switch


1 L3 SwitchPerformance : 32-Gbps switching fabric Stack-forwarding rate of 38.7 mpps for 64-byte packets Forwarding rate 35.7 mpps 128 MB DRAM and 32 MB Flash memory Configurable up to 12,000 MAC addresses Configurable up to 20,000 unicast routes Configurable up to

4

For Tape Auto Loader


1 Tape Auto Loader Drive options 6 full-height: 8 Gbps Fibre Channel : 6 half-height: 6 Gbps SAS ; 8 Gbps

Fibre Channel 5 full-height: 6 Gbps SAS ; 8 Gbps Fibre Channel 5 half-height: 6 Gbps SAS ; 8 Gbps Fibre Channel 4 full-height: Low Voltage Differential (LVD) SCSI ; 3 G

2

For Storage System


1 Storage SystemUp to 24 TB of physical storage per enclosure using 2 TB Redundant dual-active intelligent RAID controllers 16 GB cache memory per control enclosure (8 GB per internal RAID controller) as a base feature For each control enclosure: Eight 8 Gbps Fibre Chann

2

For Work Stations


1 Work StationsOperator, Engineering Workstations and NMS server each comprising Intel Xeon W3520 2.66 8MB/1066 QC CPU 4GB (2x2GB) DDR3-1333 ECC RAM NVIDIA Quadro NVS 450 512MB Graphics 250GB SATA 7200 1st HDD USB Standard Keyboard USB Optical Scroll Mouse 16X DVD+-RW S

5

For Monitors


1 MonitorMonitor : 24-inch S-IPS LCD Monitor

12

For SFP Cards


1 Gigabit Interface Converter (GBIC) Module and Small Form-Factor Pluggable (SFP) As to be compatible with Server Chassis.

12


Fiber Patch Cord As to be compatible with SFP Cards12


LAN Based GPS System1

NIT: CMC/BY/12-13/RB/VKS/063 Page 1 of 8 Bidders seal & signature

Annexure No:V

BID FORM

Up gradation of SCADA & DMS Software system

ToHead of the DepartmentContracts & MaterialsBSES Yamuna Power LtdBSES Bhawan, KarkardoomaNew Delhi– 110032Sir,

1 We understand that BYPL is desirous of procuring”Upgradation of SCADA & DMSSoftware System ‘in it‘s licensed distribution network area in Delhi.2 Having examined the Bidding Documents for the above named works, we the undersigned,

offer to deliver the goods in full conformity with the Drawings, Conditions of Contract andspecifications for the sum of.........................................

(figures........................................................................) or such other sums as may be determined inaccordance with the terms and conditions of the contract .The above Amounts are in accordancewith the Price Schedules attached herewith and are made part of this bid.3 If our Bid is accepted, we under take to deliver the entire goods as per delivery schedulegiven by you from the date of award of purchase order/letter of intent.4 If our Bid is accepted, we will furnish a performance bank guarantee for an amount of 10%(Ten) percent of the total contract value for due performance of the Contract in accordance with theGeneral Conditions of Contract.5 We agree to abide by this Bid for a period of 120 days from the date fixed for bid openingunder clause 9.0 of GCC, and it shall remain binding upon us and may be accepted at any timebefore the expiration of that period.6 We declare that we have studied the provision of Indian Income Tax Law and other IndianLaws for supply of equipments/materials and the prices have been quoted accordingly.7 Unless and until Letter of Intent is issued, this Bid, together with your written acceptancethere of, shall constitute a binding contract between us.8 We understand that you are not bound to accept the lowest, or any bid you may receive.9 There is provision for Resolution of Disputes under this Contract, in accordance with theLaws and Jurisdiction of Contract, Clause 19 of GCC .

Dated this............................... day of................................................. 20 ...............Signature.............................................. In the capacity of ………………………………

..................................................................duly authorized to sign for and on behalf of(IN BLOCK CAPITALS) ...............................................................................


FORMAT FOR BID SECURITY BANK GUARANTEE

(To be issued in a Non Judicial Stamp Paper of Rs.50/-purchased in the name of the bank)

Whereas [name of the Bidder](hereinafter called the Bidder“) has submitted its bid dated [date ofsubmission of bid] for the supply of [name and/or description of the goods] (hereafter called ‘’theBid”).

KNOW ALL PEOPLE by these presents that WE [name of bank]at[Branch Name andaddress],having our registered office at[address of the registered office of the bank](herein aftercalled —the Bank“),are bound unto BSES Yamuna Ltd., with it‘s Corporate Office at BSES BhawanKarkarduma, New Delhi -110032 ,(herein after called —the Purchaser“)in the sum of Rs.…………….for which payment well and truly to be made to the said Purchaser, the Bank bindsitself, its successors, and assigns by these presents. Sealed with the Common Seal of the said Bankthis_____ day of________ 20____.

THE CONDITIONS of this obligation are:

1. If the Bidder withdraws its Bid during the period of bid validity specified by theBidder on the Bid Form ;or

2. If the Bidder, having been notified of the acceptance of its Bid by the Purchaserduring the period of bid validity:

(a) Fails or refuses to execute the Contract Form, if required; or (b) Fails or refuses to furnish the performance security, In accordance with the Instructions to Bidders/GENERAL condition;

We undertake to pay to the Purchaser up to the above amount upon receipt of its first writtendemand, without the Purchaser having to substantiate its demand, provided that is its demand thepurchaser will note that amount claimed by it is due to it, owing to the occurrence of on e or both ofthe two condition s, specifying the occurred condition or condition s.

This guarantee will remain in force up to and including One Twenty (120) days after the period ofbid validity, and any demand in respect thereof should reach the Bank not later than the above date.

(Signature of the bank)

Signature of the witness


Annexure –VI

Price FormatAnnexure-1 Bill Of Material(Software)

S.No Item Description Unit Quantity BasicPrice

Taxapplicable

Taxes Total(perunit)

Total

1 SCADA SOFTWARE for Hardware mentioned inAnnexure -2 of sever BOM (Latest version)

Set 1

1.1 DMS Software with following Modules Set 11.1.1 Network Connectivity Analysis (NCA) Set 11.1.2

State Estimation (SE)Set 1

1.1.3 Load Flow Application (LFA) Set 11.1.4 Voltage VAR control (VVC) Set 11.1.5 Load Shed Application (LSA) Set 11.1.6 Fault Management and System Restoration

(FMSR)Set 1

1.1.7 Loss Minimization via Feeder Reconfiguration(LMFR)

Set 1

1.1.8 Load Balancing via Feeder Reconfiguration(LBFR)

Set 1

2 ICCP Server License for hardware mentioned inAnnexure -3 of server BOM

set 1

3 Web Server(30 clients) license for hardwarementioned in annexure-3 of server BOM

Set 1

3.1 Software Application

3.1.1 Load Shed Application (LSA) Set 13.1.2 SCADA – GIS integration Set 13.1.3 SCADA-OMS integration Set 13.1.4 SCADA-SAP integration Set 13.1.5 Under Frequency Load Sheds Application Set 13.1.6 SCADA-AMR Integration Set 13.1.7 Peak Load on each feeder Daily/

Monthly/Yearly basis.Set 1

3.1.8 Fault location integration through numericrelays & GIS

Set 1

4 SCADA FEP Licenses with 150 communicationlines

Set 1

5 Work Station Licenses Set 76 Data Migration from Unix to Linux Set 17 Training Set 17.1 Database, Display Building & Report

generation trainingSet 1

7.2 Computer system software training Set 17.3 Application software Training Set 17.4 Operator Training Set 17.5 System Administration Training Set 18 Development of Applications Set 1


9 AMC Cost for 4 Years(after OEM warranties) Set 110 Multi site architecture & integration with MCC-

1set 1

Grand Total Rs:………………………………………………..(In Figures & Words)

Name :…………………………………….

Tel/Mobile No:……………………………

Email ID:…………………………………..

Date: ………………. Signature with Seal

Place :…………………….


Annexure-VIICOMMERCIAL TERMS AND CONDITIONS

S/NO ITEM DESCRIPTION AS PER BYPL CONFIRMATION OFBIDDER/BIDDER terms

1 Validity of prices 120 days from the date of offer

2 Price basis

a) Firm, FOR Delhi store basis. Prices shallbe inclusive of all taxes & duties, freightupto Delhi stores.b) Unloading at stores shall be in vendor'sscopec) Transit insurance in BYPL scope

3 Payment terms

100% of the ex-works price, plus packing,forwarding, freight and insurance charges,taxes and duties shall be payable to thesupplier, for the indigenous equipment,within 90 days of receipt, installation,testing, commissioning and Taking Overthe equipments/materials at the desiredpremises of the consignee in satisfactoryworking condition. The payment will bereleased only after verification of the billby the Indenting Unit.

4 Delivery schedule Within One month

5 Defect Liability period12 months after commissioning or 18months from the last date ofdespatch,whichever is earlier

6 Penalty for delay1% per week of delay of undelivered unitsor part thereof subject to maximum of 10%of total PO value of undelivered units

7 Performance Bank Guarantee

10% of total PO value valid for 12 monthsafter commissioning or 18 months from thelast date of despatch,whichever is earlierplus 3 months towards claim period


ANNEXURE VIII

NIT NO & DATE : ……………………….. DT: ………….

NO DEVIATION SHEET

SL NO SL NO OF TECHNICAL SPECIFICATION DEVIATIONS,IF ANY

SIGNATURE & SEAL OF BIDDER

NAME OF BIDDER


Annexure - IX

Sno Qualification Criteria Description by bidder withqulifying the fulfillment

Documentary Evidenceattached paghe no.detail

1Yearly Turnover is approx 1000 Crores inlast FY

23 sucessful implementation of SCADA inlast 10 years.

3

Valid registration no of salestax/VAT/Service tax, whichever isapplicable

4

Firms who are debarred/blacklisted inother utilities in India will not beconsidered.

Owner reserves the right to carry out capability assessment of the bidder and owners decision shall befinal in this regards.


CHECK LIST

Sno Item Description Yes/No

1 INDEX Yes/no

2 COVERING LETTER Yes/No

3 Bid FORM (UNORICED) DULY SIGNED Yes/no

4 Bill of Material (UNPRICED) Yes/No

5 TECHNICAL BID Yes/no

6ACCEPTANCE TO COMMERCIAL TERMAND CONDITIONS Yes/No

7 FINANCIAL BID (IN SEALD ENVELOPE) Yes/no

8 EMD IN PRESCRIBED FORMET Yes/No

9DEMAND DRAFT OF RS 1000/- DRAWN INFAVOUR OF BSES………POWER LTD

10POWER OF ATTORNEY/AUTHORISATIONLETTER FOR SIGNING THE BID Yes/No