Scada RFP Rev Doc-9 Nov 2022 Final
Scada RFP Rev Doc-9 Nov 2022 Final
Scada RFP Rev Doc-9 Nov 2022 Final
FOR
<Utility>
1.0 <- name of Utility -> invites on-line bids on Single Stage Two Envelope Basis (i.e.
Envelope-I: Techno-Commercial and Envelope-II: Price) from eligible Bidders for
SCADA/DMS Implementation for RDSS works in the <Utility>, as per the scope of
work briefly mentioned hereinafter.
The Brief Scope of work for subject Package shall comprise of Design, engineering,
manufacture, shop fabrication, preassembly, shop testing/ type testing at manufacturer’s
works, packing, transportation, unloading, handling and conservation of equipment at site,
complete services of construction including erection, supervision, pre-commissioning,
commissioning and FMS for 5 years .
The SIA in coordination with utility (as per the requirement to be given in the detailed RFP)
shall carry out field survey, design ,engineering, supply, integration, installation, testing &
commissioning of SCADA/DMS/OMS software applications, Dispatcher Training Simulator
(DTS) , hardware (including PCs, Servers, Routers, Switches, VPS, RTU, FRTUs, Multi
function Transducers (MFTs), Communication equipment , Auxiliary power supply etc),
software (including operating system, databases, network management system etc.), network
(LAN, WAN ), etc
The detailed scope of work shall be as per specifications and scope defined in the Bidding
Document for SCADA/DMS Implementation for RDSS works in the <Utility>,
3.0 <Utility> intends to finance the aforesaid Package through GoI Grant and internal resources as
per RDSS Guidelines.
4.0 Detailed specification, scope of work and terms & conditions are given in the Bidding
Documents, which are available at e-procurement portal website- <- Utility to mention->
and as per the following schedule::
*No Queries from Bidders, whatsoever, shall be entertained by the Employer beyond the last
date of receipt of Queries/ Pre-Bid Conference as specified above.
5.0 All bids must be accompanied by “Bid Security” in lieu of Bid Security in the form as
stipulated in the Bidding Documents.
5.1 Acceptable ‘Bid Security’ and Tender Fee payment proof shall be uploaded by all the bidder
in the e-tendering portal utility to mention specifics with regard to tendering portal.
7.0 "<Utility>” shall allow purchase preference, as indicated in the bidding documents, to bids
from local suppliers as defined in the bidding documents. The bidders may apprise themselves
of the relevant provisions of bidding documents in this regard before submission of their
bids."
7.1 Any ‘Bidder from a country which shares a land border with India’, as specified in the Bidding
Documents, will be eligible to bid in this tender only if bidder is registered with the Competent
Authority as mentioned in the Bidding Documents.
However, the said requirement of registration will not apply to bidders from those
countries (even if sharing a land border with India) to which the Government of India has
extended lines of credit or in which the Government of India is engaged in development
projects.
8.0 Transfer of Bidding Documents purchased by one intending Bidder to another is not permissible.
9.0 Issuance of Bidding Documents to any bidder shall not construe that bidder isconsidered qualified.
10.0 <Utility> reserves the right to reject any or all bids or cancel/withdraw the Invitation for Bids
(IFB) for the subject package without assigning any reason whatsoever and in such case no
bidder/intending bidder shall have any claim arising out of such action.
11.0 A complete set of Bidding Documents may be downloaded by any interested Bidder from the
website <- Utility to mention->. The tender is invited under e-tendering process. The bidders
can enroll themselves on the website <- Utility to mention->. The said website also has
the detailed guidelines on enrollment and participation in the bidding process including
Bidder Manual for online fee payment (utility to check for the online fee payment
provision of tendering portal).
A. General
1. Mode & Type The bidding shall be done online through e-tender portal
of bidding -utility to specify----- on Domestic Competitive Bidding (DCB), Single
Stage Two Envelope bidding. Bidders are advised to go through the
guidelines provided at e-tender portal for online bidding.
2. Scope of Bid 2.1In support of the Invitation for Bids indicated in the Bid Data Sheet (BDS),
the Utility, as indicated in the BDS, issues this Bidding Document for the
supply of Goods and Related Services incidental thereto as specified in the
Scope of Work at Section VI. The name and identification number of the
Domestic Competitive Bidding (DCB) are provided in the BDS.
3. Source of 3.1. The Employer named in the Bidding Documents intends to use the
Funds capital subsidy {60% (90% in case of special category states) of cost of the
infrastructures in the project} under Revamped Reforms-based and Results
linked, Distribution Sector Scheme (RDSS), a Government of India flagship
program for bringing down the costs and improve the efficiency of supply
of the electricity in the states, 40% (10% in case of special category states)
to be arranged by the State Government/Employer through loans from
REC/PFC/or other FIs/own resources. However, the payment as per the
contract payment terms will be released timely by the Employer, without
any linkage to disbursement of the funds under RDSS scheme
4. Corrupt 4.1 Utility requires bidders to observe the highest standard of ethics
Practices during the procurement and execution of such contracts.
(a) The following definitions apply:
“Corrupt practice” means the offering, givingreceiving,
or soliciting, directly or indirectly, of anything of value
to influence the action of any party in the procurement
process or the execution of a contract;
“Fraudulent practice” means a misrepresentation or
omission of facts in order to influence a procurement
process or the execution of a contract;
“collusive practices” means a scheme or arrangement
between two or more bidders, with or without the
knowledge of the Utility, designed to influence the
action of any party in a procurement process or the
execution of a contract;
“coercive practices” means harming or threatening to
harm, directly or indirectly, persons, or their property
to influence their participation in a procurement
process, or affect the execution of a contract;
(b) Utility will reject a proposal for the award of Contract if it
determines that the bidder recommended for award has,
directly or through an agent, engaged in corrupt, fraudulent,
collusive, or coercive practices in competing for the Contract
(c) Utility will declare a firm ineligible, either indefinitely or for a
stated period of time, to be awarded a contract if it at any time
determines that the firm has engaged in corrupt or fraudulent
practices in competing for or in executing a contract of the
Utility.
4.2 In continuance of ITB clause 4.1 above, the <Name of Utility> will cancel
the portion of the fund allocated to a contract for goods, works or
services if it at any time determines that corrupt or fraudulent
practices were engaged in by representatives of the Utility or a
beneficiary of the fund, during the procurement or the execution of
that contract, without the Utility having taken timely and
appropriate remedial action satisfactory to the <Name of
Utility>.
4.3 Any communication between the bidder and the Utility related to
matters of alleged fraud or corruption must be made in writing.
By signing the contract, the bidder shall represent that it is either the
owner of the Intellectual Property Rights (IPR) in the hardware,
software or materials offered, or that it has proper authorization
and/or license to offer them from the owner of such rights. For the
purpose of this clause, IPR shall be defined in the GCC Clause 15.
Willful misrepresentation of these facts shall be considered a
fraudulent practice subject to the provisions of Clauses 4.1 to 4.3
above, without prejudice to other remedies that the Purchaser may
take.
5. Eligible Bidders 5.1 Bidders meeting the eligibility criteria as outlined in Section-IV
Eligibility Criteria of this document.
5.2 Bidding is open to bidders from within the Utility's country, subject to
fulfillment of conditions specified in ITB Clause 46 “Restrictions on
procurement from a Bidder of a country which shares a land border
with India”.
5.3 Bidders debarred as per Office memorandum No F.1/20/2018-PPD
Dated 02.11.2021 issued by Department of Expenditure, Ministry of
Finance or any amendments thereof shall not be eligible to
participate.
6. Eligible Goods 6.1 For the purpose of this Clause, the term “Goods” includes hardware,
and Related software, networking equipment and cables; and “Related services”
Services includes services such as insurance, transportation, associated
documentation, installation, customization, integration, field survey,
testing and commissioning, training, technical support, maintenance,
repair and other necessary services to be provided by the selected
bidder and necessary for successful implementation of the project as
specified in the contract.
6.2 In case Bidder that does not manufacture or produce the Goods it offers
to supply shall submit the Manufacturer’s Authorization using the
form included in Section V Form F-4, Bidding Forms todemonstrate
that it has been duly authorized by the manufactureror producer of
the Goods to supply these Goods.
B. Contents of Bidding Document
7. Sections of the 7.1 The Bidding Document consists of the section as indicated below and
Bidding should be read in conjunction with any Addenda issued in accordance
Document with ITB Clause 8.
Section I. IFB
Section II. Instructions to Bidders (ITB)
Section III. Bid Data Sheet (BDS)
Section IV. Eligibility Criteria
Section V. Bidding Forms; Attachments; & Formats
Section VI. Scope of Work incl Model Technical Specification
Section VII. General Conditions of Contract (GCC)
Section VIII. Special Conditions of Contract (SCC)
7.2 The Invitation for Bids (IFB) issued by the Utility is a part of the Bidding
Document.
7.3 The Utility is not responsible for the completeness of the Bidding
Document and its addenda, if they were not obtained directly from
the Utility.
7.4 The Bidder is expected to examine all instructions, forms, terms, and
specifications in the Bidding Document. Failure to furnish all
information or documentation required by the Bidding Document
may result in the rejection of the Bid.
8. Clarification of A prospective Bidder requiring any clarification of the Bidding Document
Bidding shall put the query under Clarification tab of the on-line bid prior to the
Document clarification end date. UTILITY will respond to any request for clarification
or modification of the bidding documents that it receives within the time
line specified.
C. Preparation of Bids
10. Cost of Bidding 10.1 Tender Fee as mentioned in IFB.
10.2 The Bidder shall bear all costs associated with the preparation and
submission of its Bid, and the Utility shall not be responsible or liable
for these costs, regardless of the conduct or outcome of the bidding
process.
11. Language of Bid 11.1 The Bid, as well as all correspondence and documents relating to the
Bid exchanged by the Bidder and the Utility, shall be written in the
English. Supporting documents and printed literature that are part of
the Bid may be in another language provided they are accompanied
by an accurate translation of the relevant passages in English, in which
case, for purposes of interpretation of the Bid, such translation shall
govern.
The English Translation of the documents shall be carried out by
professional translators and the translator shall certify that he is
proficient in both languages in order to translate the document and that
the translation is complete and accurate. Further, translation shall be
authenticated by the Indian Consulate located in the Country where
the documents have been issued or the Embassy of that Country in
India.
1
For e-tendering website please refer IFB
12. Single Stage-Two Envelope Bidding procedure shall be followed
through e-tendering portal for the subject package as under:
Envelope-I: Techno-Commercial
Envelope-II: Price Bid
The Envelope-I ("Techno-Commercial Bid") shall be evaluated for
completeness and in regard to fulfilment of the qualification
requirements and eligibility conditions. The Envelope- II ("Price Bid")
shall be considered for opening from those bidders who have been
considered qualified and whose Techno-Commercial Bids have been
found to be responsive and shall be opened as per the IFB.
The Bidder shall include in its bid details of all major items
of supply or services that it proposes to purchase or sublet
and shall give details of the name and nationality of the
proposed Subcontractor, including vendor, for each of those
items. Bidders are free to list more than one
Subcontractor/Vendor against each item of the facilities.
Quoted rates and prices will be deemed to apply to
whichever Subcontractor/Vendor is appointed, and no
adjustment of the rates and prices will be permitted.
13. Bid Submission 13.1. The Bidder shall submit the Technical Proposal and the Price
Sheets and Price Proposal using the appropriate Submission Sheets provided
Schedules in RfP. These forms must be completed without any
alterations to their format, and no substitutes shall be
accepted. All blank spaces shall be filled in with the
information requested.
13.2. The Bidder shall submit, as part of the Price Proposal, the Price
Schedules for Goods and Related Services, using the forms
furnished in Section V, Bidding Forms and Supplier response
format, Appendix C
13.3.2. Please refer to GCC Clause [14] and the SCC for Price
adjustments due to change in Tax rates (including local taxes),
duties, levies, cess, charges etc.
14. Alternative Bids 14.1. Alternative (alternate technology / architecture / design /
functionality or proposals with multiple options) bids shall be
rejected.
15. Bid Prices and 15.1. Unless otherwise specified in the Technical Specifications, Bidders
Price Basis shall quote for the entire facilities on a “single responsibility” basis such
that the total bid price covers all the Contractor’s obligations mentioned in
or to be reasonably inferred from the bidding documents in respect of the
design, manufacture, including procurement and subcontracting (if any),
delivery, construction, installation, commissioning, civil & steel structural
works (as applicable), Completion of the facilities and conductance of
Guarantee tests for the facilities including supply of mandatory spares (if
any). This includes all requirements under the Contractor’s responsibilities
for testing, pre-commissioning and commissioning of the facilities,
conducting Guarantee tests and, where so required by the bidding
documents, the acquisition of all permits, approvals and licenses, etc.; the
operation, maintenance and training services and such other items and
services as may bespecified in the bidding documents, all in accordance
with therequirements of the General Conditions of Contract and Technical
Specifications.
15.2. Bidders are required to quote the price for the commercial, contractual and
technical obligations outlined in the bidding documents.
17. Documents 17.1. To establish their eligibility in accordance with ITB Clause 5,
Establishing the Bidders shall:
Eligibility and
(a) complete the eligibility declarations in the Bid Submission
Qualification of
Sheet, included in Section V, Bidding Forms
the Bidder
18. Documents 18.1. To establish the conformity of the Goods and Related Services to
Establishing the the Bidding Document, the Bidder shall furnish as part of its
Conformity of Technical Proposal the documentary evidence against Goods and
the Goods and related Services provided in Appendix C3.
Related Services 18.2. The documentary evidence may be in the form of literature,
to the Bidding drawings or data, and shall consist of a detailed description of the
Document essential technical and performance characteristics of the Goods
and Related Services, demonstrating substantial responsiveness of
the Goods and Related Services to those requirements, and if
applicable, a statement of deviations and exceptions to the
provisions of Appendix C;
18.3. Standards for workmanship, process, material, and equipment, as
well as references to brand names or catalogue numbers specified
by the Utility in the Scope of Work, are intended to be descriptive
only and not restrictive. The Bidder may offer other standards of
quality, brand names, and/or catalogue numbers, provided that it
demonstrates, to the Utility’s satisfaction, that the substitutions
ensure substantial equivalence or are superior to those specified
in the Scope of Work.
19. Period of 19.1. Bids shall remain valid for the period of 180 days after the bid
Validity of Bids submission deadline date prescribed by the Utility. A Bid valid for
a shorter period shall be rejected by the Utility as non-responsive.
19.2. In exceptional circumstances, prior to the expiration of the bid
validity period, the Utility may request Bidders to extend the period
of validity of their Bids. The request and the responses shallbe made
in writing. The Bid Security furnished in accordance with ITB Clause
20, it shall also be extended for a corresponding period. A Bidder
may refuse the request without the proceedings as outlined in Bid
Security Format being initiated. A Bidder
granting the request shall not be required or permitted to modify
its Bid.
20. Bid Security 20.1. The Bidder shall furnish, as part of its Bid, a Bid Security in original
form, and in the amount specified in IFB / BDS in a separate
envelope.
20.2. Bid Security shall be a demand guarantee, and in any of the
following forms at the Bidder’s option:
(a) an unconditional guarantee issued by a nationalized/
scheduled commercial bank located in India;
(b) a cashier’s or certified check or demand draft from a
Nationalized/ Scheduled commercial bank located in India;
or
(c) another form security, if specified in the BDS.
In the case of a bank guarantee, the Bid security shall be
submitted using the Bid Security Form included in Section 4,
Bidding Forms – Technical Part of the Bid. The form must include
the complete name of the Bidder. The Bid Security shall be valid
for ninety (90) days beyond the original validity period of the Bid,
or beyond any period of extension if requested under ITB 19.2
20.3. Wherever Bids under Joint Venture route are permitted as per the
Qualifying Requirements in the Bidding Documents, the Bid Security
Declaration by the Joint Venture must be on behalf of all the
partners of the Joint Venture.
20.4. The Bid Security in Original shall be submitted in a separate
sealed envelope before the stipulated bid submission closing
date and time.
20.5. In case acceptable Bid Security is not received then online Bid shall
be rejected by UTILITY as being non-responsive andshall not be
opened.
20.6. Bid Security of unsuccessful Bidders shall be returned as promptly
as possible upon the successful bidder’s signing the contract and
furnishing the Performance Security pursuant to ITB 41 and ITB 42
20.7. The Bid Security of the successful bidder shall be returned as
promptly as possible once the successful bidder has signed the
Contract and furnished the required Performance Security
20.8. The proceedings as outlined in Bid Security Format shall be
initiated:
(a) if a Bidder withdraws /modifies/substitutes its Bid during the
period of bid validityas specified in ITB Clause 19.1, except
as provided in ITB Sub- Clause 19.2 or 25 ; or
21. Format and The Bids shall be digitally certified (using the appropriate class of
Signing of Bid digital signature prescribed at e-tender portal) by a duly authorised
representative of the Bidder to bind him to the contract. The
authorization shall be indicated by written power of attorney, duly
notarized by a Notary Public, indicating that the person signing the bid
has the authority to sign the bid and that the bid is binding upon the
Bidder during the full period of its validity in accordance with ITB
Clause titled ‘Period of Validity of Bids’ and shall be submitted in
hard copy prior to the deadline for submission of bid.
D. Submission and Opening of Bids
22. Sealing and The Techno-Commercial Bid (comprising the Bid Form (Techno-
Marking of Bids Commercial Bid), together with its Attachments) and Price Bid
(comprising the Bid Form (Price Bid), together with its Attachments
and the Excel BOQ template shall be submitted simultaneously at the
e-tender portal and no manual/ hard copy of these documents shall
be acceptable. The documents comprising Tender Fee, Bid Security
Declaration, Power of Attorney, Integrity Pact etc in accordance with
ITB sub-clause 12.1.1 shall be submitted in physical form after being
sealed and marked in the manner specified below:
(a) be addressed to the Utility at the address given in the Bid Data
Sheet, and
(b) bear the Package name indicated in the Bid Data Sheet, the
Invitation for Bids number indicated in the Bid Data Sheet, and the
statement "DO NOT OPEN BEFORE [date]," to be completed with the
time and date specified in the Bid Data Sheet, pursuant to ITB clause
titled ‘Deadline for Submission of Bids’.
The inner envelopes shall also indicate the name and address of the
Bidder. If the outer envelope is not sealed and marked in the manner
specified above, the Utility will assume no responsibility for
its misplacement.
23. Deadline for 23.1. Bids must be received by the Utility no later than the date andtime,
Submission of and at the address indicated in the BDS. The physical documents
Bids shall be submitted before stipulated bid submission time at the
address specified in BDS and Utility shall not be liablefor loss/non-
receipt/late receipt of above documents in postal transit.
23.2. The Utility may, at its discretion, extend the deadline for the
submission of Bids by amending the Bidding Document in
accordance with ITB Clause 9, in which case all rights and obligations
of the Utility and Bidders previously subject to the deadline shall
thereafter be subject to the deadline as extended.
24. Late Bids 24.1. The Utility shall not consider any Bid that arrives after the deadline for
submission of Bids, in accordance with ITB Clause 23. Any Bid
received by the Utility after the deadline for submission of Bids shall
be declared late, rejected, and returned unopened to the Bidder.
25. Withdrawal, 25.1. A Bidder may withdraw, substitute, or modify its Bid after it has been
Substitution, and submitted by sending a written Notice, duly signed by anauthorized
Modification of representative, and shall include a copy of the authorization in
Bids accordance with ITB Sub-Clause 21. The corresponding substitution
or modification of the bid must accompany the respective written
notice. All Notices must be:
(a) submitted in accordance with ITB Clauses 21 and 22 (except
that Withdrawal Notices do not require copies), and in
addition, the respective inner and outer envelopes shall be
clearly marked “Withdrawal,” “Substitution,” “Modification”;
and
(b) received by the Utility prior to the deadline prescribed for
submission of bids, in accordance with ITB Clause 23.
25.2. Bids requested to be withdrawn in accordance with ITB Sub- Clause
25.1 shall be returned unopened to the Bidders.
25.3. No Bid shall be withdrawn, substituted, or modified in the interval
between the deadline for submission of bids and the expiration of
the period of bid validity specified in ITB Clause 19.1 or any extension
thereof.
26.1.1. The Utility will first open Techno-Commercial Bid in the presence of
bidders' representatives who choose to attend the opening at the time, on the
date and at the place specified in the Bid Data Sheet (BDS). In the event of
the specified date for the opening of bids being declared a holiday for Utility,
the bids will be opened at the appointed time on the next working day. All
important information and other such details as Utility, at its discretion, may
considerappropriate, will be announced at the opening.
26.1.2. In case requisite bid security, Tender Fee, and/or Integrity Pact (IP) as per
provision of Integrity Pact pursuant to ITB Clause 12 are not submitted
before the stipulated bid submission closing date and time then Bid shall be
rejected by Utility as being non- responsive and shall not be opened.
26.1.3. Clarification on Bids
During bid evaluation, Utility may, at its discretion, ask the Bidder for a
clarification of its bid including documentary evidence pertaining to the
reference plants declared in the bid for the purpose of meeting Qualifying
Requirement specified in Bid Data Sheet (BDS). Therequest for clarification
and the response shall be in writing, and no change in the price or substance
of the bid shall be sought, offeredor permitted.
26.3.1. If so permitted in the Bid Data Sheet (BDS), Reverse Auction shall
be carried out on the evaluated price as per methodology defined inthe BDS.
Arithmetical Correction
Arithmetical errors will be rectified on the following basis. In the Excel
BOQ template, if there is a discrepancy between the unit price and the
total price, which is obtained by multiplying the unit price and
quantity, or between subtotals and the total price, the unit or subtotal
price shall prevail and the total price shall be corrected accordingly. If
there is a discrepancy between words and figures, the amount in
words will prevail. All errors in totalling in the amount column of the
Excel BOQ template and in carrying forward totals shallbe corrected.
The discount (if any) mentioned in Conditions field of General
Data/Item Data in Main Screen of Bid Invitation shall be applied on
such corrected price. The bid sum so altered shall, for the purpose of
bid, be substituted for the sum originally bid and considered for
evaluation and comparison of the bids and also for acceptance of the
bid, instead of the original sum quoted by the
Bidder. If the Bidder does not accept such correction of errors, its bid
will be rejected and the proceedings as outlined in Bid Security
Format shall be initiatedin accordance with ITB Clause titled ‘Bid
Security’.
32. Examination of 32.1. The Utility shall examine the Bids to confirm that all terms and
Terms and conditions specified in the GCC and the SCC have been accepted by
Conditions; the Bidder without any material deviation or reservation.
Technical 32.2. The Utility shall evaluate the technical aspects of the Bid submitted in
Evaluation accordance with ITB Clause 19, to confirm that all requirements
specified in the Scope of Work at Section VI, of the Bidding Document
have been met without any material deviation or reservation.
32.3. If, after the examination of the terms and conditions and the
technical evaluation, the Utility determines that the Technical
Proposal is not responsive in accordance with ITB Clause 30, it shall
reject the Bid.
41. Signing of 41.1. Promptly after notification, the Utility shall send to the successful
Contract Bidder the Agreement, a copy of SLA and the General and Special
Conditions of Contract.
41.2. Within fourteen (14) days of receipt of the Agreement, the successful
Bidder shall sign, date, and return it to the Utility.
41.3. The successful Bidder shall provide an undertaking that the key staff
identified for the project (as submitted in its bid proposal) shall be
available for the respective proposed work requirement, anytime
during the duration of the project, till its successful completion. The
same is intended to be published by the Nodal Agency on their
website for the information of other utilities who intend to appoint
SIA, for avoiding any duplicity in resource deployment.
42. Performance 42.1. Within fourteen (14) days of the receipt of notification of award from
Security the Utility, the successful Bidder shall furnish the Performance
Security in accordance with the GCC, using for that purpose the
Performance Security Form as provided in the documents.
42.2. Failure of the successful Bidder to submit the above-mentioned
Performance Security or sign the Contract shall constitute sufficient
grounds for the annulment of the award and the proceedings as
outlined in Bid Security Format shall be initiated. In that event the
Utility may award the Contract to the next successful Bidder whose
offer is responsive and is determined by the Utility to be qualified to
perform the Contract satisfactorily.
43. Local It will be imperative on each bidder to fully inform himself of all local
Conditions conditions and factors which may have any effect on the execution of
the works covered under these documents and specifications. The
Utility shall not entertain any request for clarifications from the
bidders, regarding such local conditions. It must be understood and
agreed that such factors have properly been investigated and
considered while submitting the proposals. No claim for financial
adjustment to the contract awarded under these specifications and
documents will be entertained by the Utility. Neither any change in
the time schedule of the contract nor any financial adjustments arising
thereof shall be permitted by the Utility, which are based on the lack of
such clear information or its effect on cost of the works to the bidder.
44. Annulment of Failure of the successful Bidder to comply with the requirements of ITB
award Clause titled ‘Signing the Contract Agreement’ or ITB Clause titled
‘Performance Security’ shall constitute sufficient grounds for the
annulment of the award and initiation of the proceedings as outlined
in Bid Security Format.
45. Ineligibility for Notwithstanding the provisions specified in ITB Sub-Clause for
participation in ‘Forfeiting of Bid Security’ and ITB Clause titled ‘Annulment of award’, if
re-tender a bidder after having been issued the Notification of Award/ Purchase
Order, either does not sign the Contract Agreement pursuant to ITB
Clause titled ‘Signing the Contract Agreement’ or does not submit an
acceptable Performance Security pursuant to ITB Clause titled
‘Performance Security’, and which result in tender beingannulled then
such bidder shall be treated ineligible for participation inre-tendering of
this particular package.
Ineligibility for participation in future tenders
If a bidder after opening of tenders where EMD is ‘NIL/Not applicable’
or exempted for bidders as per policy guidelines, withdraws its offer
within the validity period of the offer, then such bidder shall be treated
as ineligible for participation in the future tenders issued from
Respective Utility (Tender inviting Utility) for a period of 6 months from
the date of withdrawal of the bid.
46.4. “Bidders from a country which shares a land border with India” / “Sub-
contractor from a country which shares a land border with India”
mentioned in para 46.1 above means;
a) An entity incorporated, established or registered in such a
country; or
b) A subsidiary of an entity incorporated, established or
registered in such a country; or
c) An entity substantially controlled through entities
incorporated, established or registered in such a country; or
d) An entity whose beneficial owner is situated in such a
country; or
e) An Indian (or other) agent of such an entity; or
f) A natural person who is a citizen of such a country; or
g) A consortium or joint venture where any member of the
consortium or joint venture falls under any of the above.
46.5. The beneficial owner for the purpose of clause “46.4” above will be
as under;
(a) In case of company of Limited Liability Partnership, the beneficial
owner is the natural person(s), who, whether acting alone or
together, or through one or more juridical person, has a controlling
ownership interest or who exercises control through other
means.
Explanation-
i. “Controlling ownership interest” means ownership of or
entitlement to more than twenty-five per cent of shares or capital
or profits of the company;
ii. “Control” shall include the right to appoint majority of the directors
or to control the management or policy decisions including by
virtue of their shareholdings or management rights or
shareholders agreements or voting agreements;
47. Independent In respect of this package, the Independent External Monitors (IEMs) would
External be monitoring the bidding process and execution of contract to oversee
implementation and effectiveness of the Integrity Pact Program.
Monitors
The Independent External Monitor(s) (IEMs) as mentioned at UTILITY
(IEM)s WEBSITE (Mention web address) have been appointed by Utility, in terms
of Integrity Pact (IP) which forms parts of the Name of Utility
Tenders/Contracts.
G. Interpretation
48. Interpretation 48.1 This Bid Document, inclusive of the MTS document, Schedules,
of the Model annexure(s), the statements, exhibits and sections, if any, comprises
Technical the whole and complete Document
Specifications
(MTS) and the 48.2 This RFP document should be read in consonance with the MTS
document. In the RFP document references to the MTS have been
RFP document
provided. In case there is no reference relating to a particular clause(s)
of the MTS, it should be deemed as the said reference has been
provided. The bidder is required to read both the documents and
would be deemed to be in knowledge of the provisions of both the MTS
and the RFP document. No claim of any nature whatsoever shall be
entertained in this regard.
48.3 In case of any conflict with any provision relating to the MTS document
and the RFP document, the provisions of the RFP document shall
prevail for all intents and purposes
H. Conflict of Interest
49.1 A Bidder shall not have a conflict of interest. Any Bidder found to have
a conflict of interest shall be disqualified. A Bidder may be considered
to have a conflict of interest for the purpose of this Bidding process, if
the Bidder:
B. Bidding Document
ITB 8.4 Details of Pre-Bid conference:
Date: <To be filled by utility>
Venue: <To be filled by utility>
Time: <To be filled by utility>
C. Preparation of Bids
ITB 12.1 For formats of the attachments Bidder needs to submit with its Technical
Proposal Refer to Section V
ITB 12.2 All prices to be quoted by the bidders will be in Indian Rupees only
ITB 12.2 For formats of the attachments Bidder needs to submit with its Price Proposal
Refer to Section V
ITB 14.1 Alternative Bids shall not be permitted.
Incoterms Incoterms means international rules for interpreting trade terms published by the
International Chamber of Commerce (latest edition), 38 Cours Albert 1er, 75008
Paris, France.
ITB 15.4 The prices quoted by the Bidder shall be: Firm (subject to GCC 14.5)
ITB 19.1 The bid validity period shall be 180 days after the bid submission deadline
date prescribed by the Purchaser.
ITB 20.1 Bidders are required to submit the Bid Security in line with the Order No
F.9/4/2020-PPD dtd 30.12.2021 issued by Ministry of Finance, Govt. of Indiaor
any amendments thereof. (Refer Annexure-I to BDS)
The bid identification No. shall be mentioned by the Bidder prominently on the
top of envelope for the lots in the following manner :
(a) Bidding process for the bid is : “Single stage Two envelope”
(b) Bid identification No. “<>”
Wherever reference to “Time” has been made, the same shall be taken as Indian
Standard Time. If time is mentioned in “P.M”, the same shall be converted into
Hours by adding 12 Hours e.g. 2 P.M equal to 2 + 12 i.e. “14.00 Hours IST”
ITB 26.1 The bid opening shall take place at:
F. Award of Contract
ITB 39.1 The percentage by which number of towns may be increased is: 30 percent of
the total number of towns
The percentage by which number of towns may be decreased is: 30 percent of the
total number of towns
ITB 41.2 If the successful bidder fails to sign the Contract Agreement within 14 days from
the date the successful bidder’s receipt of the Contract Agreement, the Purchaser
reserves the right to terminate the award by forfeiting Bid Security without any
notice.
ITB 42.1 If the successful bidder fails to furnish the required Performance Security within
28 days of the receipt of notification of award, the Purchaser reserves the right to
terminate the award by forfeiting Bid Security without any notice.
G. Others
ITB 46 Restrictions on a Bidder of a country which shares a land border with India.
Please Refer Annexure-III to BDS
Annexure-I to BDS
Annexure-II to BDS
(Declaration of Local Content)
(TO BE SUBMITTED ALONGWITH TECHNO-COMMERCIAL BID)
Dear Sirs,
We have read the provisions of “Preference to Make In India and granting of purchase preference to local
suppliers” enclosed with SCC. In terms of the requirement of the aforesaid provisions, we hereby declare the
following:
1. In order of avail purchase preference, we confirm that we are at Local Supplier, and the local content
included in the package is ------ % of our total bid price for complete scope of work for NAME OF THE WORK
as per details given below.
S.No Description of Quality/qty Local Content Details of the Location(s) at which the
Goods & Weight (as % of Total local value addition is made
Services bid Price)
2. We undertake that a certificate from the statutory auditor or cost auditor (in the case the bidder is
a company) or from a practicing cost accountant or practicing chartered accountant (in respect
of bidders other than companies) certifying the percentage of local content shall be submitted
by us prior to submission of our last bill for payment.
Whether the bidder is presently debarred /banned by the other procuring entity Yes* / No*
for violation of “Public Procurement (Preference to Make In India), Order 2017”
(PPP-MII Order) dated 15.06.2017 issued by Department of Industrial Policy
and Promotion (DIPP)
4. We agreed to furnish any information as a proof of the above to your satisfaction as and when
required.
Note:
1. Continuation sheet of like size and format may be used as per Bidder’s requirement and shall be
annexed to this Attachment.
2. Certificate pertaining to percentage of local content from statutory auditor or cost auditor/ practicing
chartered accountant or cost accountant is to be furnished in case where the total bid price is more
than INR 10 Crores.
Annexure-III to BDS
Power Finance Corporation
SCADA/DMS, system under RDSS - Govt. of India
Model Technical specification
Section IV of SBD
Power Finance Corporation
SCADA/DMS, system under RDSS - Govt. of India
Model Technical specification
Utility may float tender individually or combined for Group-A & B together and may also
divide Group A & B into multiple packages to derive optimal volume of work and enhance
competition. Utility preferably may tender Group U towns separately.
Group-A /U towns
Only those bidders which meets the below mentioned minimum Qualifying Requirements shall
be considered for further evaluation of Technical Proposal. The bidder or members of the
consortium & their holding company shall not be based in prior referenced countries as notified
by MHA, GoI at the time of bidding at the time of award.
The Bidder can be a Sole Bidder or a Consortium (of not more than two members) who shall
meet the following: -
I. Financial (Both lead & Consortium partner shall meet the requirement
individually)
i. Average Annual financial turnover during the last 3 years, ending 31st March of the previous
financial year, should be at least 30% of the estimated cost (to be specified by utility).
(Proof: Annual Audited Financial Statements for last three financial years shall be submitted.
In case Audited Financial Statements for the previous year is not prepared then certificate
from statutory auditor shall be submitted certifying the annual financial turnover.)
ii. The bidder should have a net worth not less than paid-up equity, in each of the last three
audited financial years.
(Proof: Annual Audited Financial Statements for last three financial years shall be submitted.
In case Audited Financial Statements for the previous year is not prepared thencertificate
from statutory auditor shall be submitted certifying the networth)
II. Technical
iii. The following qualifying requirements (A and B) shall be met by the sole bidder.
However, member meeting qualifying requirements of part A as below, shall be the
lead member for the purpose of the contract:
A - The bidder shall provide evidence of previous experience in the design, engineering,
supply/integration , installation, testing and commissioning of atleast one SCADA &
DMS/EMS (Supervisory Control and Data Acquisition System & Distribution
Management System Projects for Power Distribution /Transmission / (11KV or above)
Tr a n
i. The above project(s) should consist of atleast cumulative of all projects , 15 RTUs
or Data Concentrator (DC) or Bay controllerUnit (BCU or IED or in combination of
these items and 30 FRTU. In case of multiple projects, each project shall have
minimum 5 RTUs or Data Concentrator (DC) or Bay controllerUnit (BCU or IED or
in combination of these items above project should be in operation for atleast one year
during last 7 years from the bid due date.
B- bidder shall provide evidence of previous experience in the design, engineering, supply,
Power Finance Corporation
SCADA/DMS, system under RDSS - Govt. of India
Model Technical specification
The proof documents available in any language other than English shall be translated to
English and authenticated by Authorised Signatory of bidder for submission. In such
cases, the original language copies shall also be submitted along with the translated proof
docments)
Group-B&C towns
Only those bidders which meets the below mentioned minimum Qualifying Requirements shall
be considered for further evaluation of Technical Proposal.
The bidder or members of the consortium & their holding company shall not be based in prior
referenced countries as notified by MHA, GoI at the time of bidding.
The Bidder can be a Sole Bidder or a Consortium (of not more than two members) who shall
meet the following:-
I. Financial (Both lead & Consortium partner both shall meet the requirement
individually)
i. Average Annual financial turnover during the last 3 years, ending 31stMarch of the previous
financial year, should be at least 30% of the estimated cost (to be specified by utility).
(Proof: Annual Audited Financial Statements for last three financial years shall be submitted.
In case Audited Financial Statements for the previous year is not prepared then certificate from
statutory auditor shall be submitted certifying the annual financial turnover)
ii. The bidder should have a net worth not less than paid-up equity, in each of the last three
audited financial years.
(Proof: Annual Audited Financial Statements for last three financial years shall be submitted.
In case Audited Financial Statements for the previous year is not prepared then certificate from
statutory auditor shall be submitted certifying the net worth.)
Power Finance Corporation
SCADA/DMS, system under RDSS - Govt. of India
Model Technical specification
II. Technical
i. The following qualifying requirements (A and B) shall be met by the sole bidder.
However, member meeting qualifying requirements of part A as below, shall be the lead
member for the purpose of the contract:
A. The bidder shall provide evidence of previous experience in the design, engineering,
supply/ integration , installation, testing and commissioning of atleast one SCADA
(Supervisory Control and Data Acquisition Projects for Power
Distribution
/Transmission/Generation/ railways/ Oil /Gas / water / process control industries in
the last seven (7) years.
The above project(s) should consist of cumulative in all projects at least 15 RTUs
or/Data Concentrator (DC) or Bay controller Unit (BCU) or IED or in combination
of these items with each project minimum 5 qty The SCADA using IEC-870-5-
104/101/DNP3.0/MODBUS/IEC61850 protocol. The above project should be in
operation for atleast one year during last 7 years from the bid due date
B. The bidder shall provide evidence of previous experience in the design, engineering,
supply/Integration, installation, testing and commissioning of atleast one SCADA or
RTDAS Project for POWER DISTRIBUTION /TRANSMISSION/GENERATION/
railways/Oil /Gas / water / process control industries in the last seven (7) years .
The above project(s) should consist of cumulative in all projects atleast 15 RTUs or
Data Concentrator or DC) or Bay controller Unit (BCU) or FPI or in combination
of these items with each project minimum 5 qty. The SCADA or RT-DAS using IEC-
870-5-104/101/DNP3.0/MODBUS protocol . The above project should be in
operation for atleast one year during last 7 years from the bid due date.
(Proof: i) LoA from the owners/client and ii)certificates of Acceptance/ successful completion
for work done, in support of the qualifying requirements, clearly establishing – a) the start
and end date, b) operation of at least 1 year of the project, c) brief scope of work and d)
cost of project, on client letterhead.
The supporting proof document must be labeled as original/true copy/translation, as the case may
be, and the same shall necessarily be signed and authenticated by the Authorised Signatory of
bidder. The owner/client contact details shall be provided against each project experience proof
being submitted.
The proof documents available in any language other than English shall be translated to English
and authenticated by Authorised Signatory of bidder for submission. In such cases, the original
language copies shall also be submitted along with the translated proof documents)
Power Finance Corporation
SCADA/DMS, system under RDSS - Govt. of India
Model Technical specification
Initially the Supplier’s responses are reviewed for compliance with the Commercial terms and
conditions. The Suppliers who fail to comply with any of the commercial terms and conditions
mentioned may be termed as non-responsive and will not be evaluated further. For those
Suppliers who have qualified the commercial terms and conditions Technical evaluation will
be conducted followed by the Price-Bid evaluation. The price bids will remain sealed until the
technical evaluation is complete.
Technical Evaluation
Stage-2
B. Price-Bid Evaluation:-
The Price-Bid evaluation shall be done only for those bids which meets minimum QR and
bidders with lowest bid price (L1) shall be awarded
Section V.
Bidding Forms; Attachments; and Formats
Form F-1: Technical Proposal Submission Sheet
Date:
Invitation for Bid No.:
e-Tender Bid
No.:
To <Address of Utility>
We have read all the provisions of the Bidding Documents and confirm that notwithstanding
anything stated elsewhere in our bid to the contrary, the provisions of the Bidding Documents, are
acceptable to us and we further confirm that we have not taken any deviation to the provisions of
the Bidding Documents anywhere in our bid.
Any deviation, variation or additional condition etc. or any mention, contrary to the provisions of
Bidding Documents and its subsequent Amendment(s)/ Clarification(s)/Addenda/Errata (if any)
found anywhere in our bid proposal, implicit or explicit shall stand unconditionally withdrawn,
without any cost implication whatsoever to the Employer, failing which our bid shall be rejected.
2.1. We further declare that additional conditions, variations, deviations, if any, found anywhere in the
proposal, shall not be given effect to
3. We are aware that the Price Schedules do not generally give a full description of the work to be
performed under each item and we shall be deemed to have read the Technical Specifications,
Drawings and other Sections of the Bidding Documents to ascertain the fullscope of work included
in each item while filling in the rates and prices. We agree that the entered rates and prices shall be
deemed to include the full scope as aforesaid, including overheads and profit.
4. We undertake, if our bid is accepted, to commence work on the Facilities immediatelyupon your
Notification of Award to us and to achieve Completion of Facilities and conduct Guarantee Test (if
any) within the time specified in the Bidding Documents.
5. Our Bid shall be valid for a minimum period of 180 days from the date fixed for the bid submission
deadline in accordance with the Bidding Document, and it shall remainbinding upon us and may be
accepted at any time before the expiration of that period.
6. If our bid is accepted, we undertake to provide Advance Payment Security, Contract Performance
Securities and securities for Deed(s) of Joint Undertaking (as applicable) in
the form and amounts and within the times specified in the Bidding Documents.
7. We are not participating, as Bidders, in more than one Bid in this bidding process in accordance
with the Bidding Document;
8. Our firm, its affiliates or subsidiaries, including any subcontractors or suppliers for anypart of
the Contract, has not been declared ineligible by the <UTILITY NAME> and debarred as per Office
memorandum No F.1/20/2018-PPD Dated 02.11.2021 or any amendments thereof as on <bidder
to enter date of bid submission>. We further confirm to intimate the tender issuing authority
regarding any change in status w.r.t. ineligibility / debarring.
9. We understand that until a formal Contract is prepared and executed between us, thisbid, together
with your written acceptance thereof in the form of your Notification ofAward shall constitute the
formation of the contract between us.
10. We understand that you are not bound to accept our bid or any other bid you may receive.
11. We have read the ITB clause regarding restrictions on procurement from a bidder of a country which
shares a land border with India and on sub-contracting to contractors from such countries. We certify
that we/our Collaborator/JV Partner/Consortium member are/isnot from such a country or, if from
such a country, have/has been registered with the Competent Authority and we will not sub-contract
any work to a contractor from such countries unless such contractor is registered with the Competent
Authority. We hereby certify that we fulfill all requirements in this regard and are eligible to be
considered.
*We further confirm that evidence of valid registration by the Competent Authority
for us/our Collaborator/JV Partner/Consortium member, as applicable, is enclosed as
Annexure…**…. to Bid.
Name
In the capacity of
Signed
Duly authorized to sign the Bid for and on behalf of
Date
Note: 1. Bidders may note that no prescribed proforma has been enclosed for:
(a) Attachment 2 (Power of Attorney)
For this, Bidders may use their own proforma for furnishing the required information with the Bid
Form F- 2 : Price Proposal Submission Sheet
Date:
DCB No.:
Invitation for Bid No.:
To:
(a) We have examined and have no reservations to the Bidding Document, includingAddenda No.
(if any):
(b) We offer to supply in conformity with the Bidding Document and in accordance withthe
delivery schedule, the following Goods and Related Services:
(c) The total price of our Bid is quoted in online tendering portal. Our quoted prices are inclusive of all
taxes and duties incl GST (Utility to check compatibility of the tenderingportal regarding GST).
(d) We have uploaded the Price Schedules as per the formats provided.
Name
In the capacity of
Signed
Duly authorized to sign the Bid for and on behalf of
Date
Form F- 3: Bid Security
{To be on non-judicial stamp paper of Rupees One Hundred Only (INR 100/-) or appropriate value as per
Stamp Act relevant to place of execution, duly signed on each page.}
To:
[Utility]
[Address]
WHEREAS……………………… [Insert name of the Sole Bidder] / [ insert name of the Lead Joint Venture
Member followed by the words “ representing Joint Venture of [ insert names of all the members of Joint
Venture]”] with address ……………. [Insert address of Sole Bidder /Lead Joint Venture Member] having its
registered office at ……………. [Insert address of the Sole Bidder /Lead Joint Venture Member] (Hereinafter,
the “Bidder”) wishes to participate in Tender No. [Tender Details] (the “RFB”) issued by [Utility] (hereinafter,
the “Utility”) for [ name of the Package/ Contract title].
And WHEREAS a Bank Guarantee for [Amount] valid t i l l [Date] is required to be submitted by the Bidder
along with the RFB.
We, …………….[Insert name of the Bank and address of the Branch giving the Bank Guarantee] having our
registered office at …………….[Insert address of the registered office of the Bank] hereby give this Bank
Guarantee No. …………….[Insert Bank Guarantee number] dated …………….[Insert the date of the Bank
Guarantee], and hereby agree unequivocally and unconditionally to pay immediately on demand in writing
from the Utility any officer authorized by it in this behalf any amount not exceeding [Amount] to the said
Utility on behalf of the Bidder.
We ……………. [Insert name of the Bank] also agree that withdrawal of the Bid or part thereof by the Bidder
within its validity or not signing the Contract Agreement or non-submission of Performance Security by the
Bidder within the stipulated time of the Letter of Award to the Bidder or any violation to the relevant terms
stipulated in the RFB would constitute a default on the part of the Bidder and that this Bank Guarantee is liable
to be invoked and encashed within its validity by the Utility in case of any occurrence of a default on the part
of the Bidder and that the amount is liable to be forfeited by the Utility
This Guarantee shall be valid and binding on this Bank up to and inclusive of ……………. [Insert the date of
validity of the Bank] and shall not be terminable by notice or by Guarantor for the reason of change in the
constitution of the Bank or the firm of the Bidder or by any reason whatsoever and our liability hereunder shall
not be impaired or discharged by any extension of time or variations or alternations made, given, conceded
with or without our knowledge or consent by or between the Bidder and the Utility.
NOTWITHSTANDING anything contained hereinbefore, our liability under this guarantee is restricted to
[Amount]. Our Guarantee shall remain in force till [Date]. Unless demands or claims under this Bank Guarantee
are made to us in writing on or before [Date], all rights of the Beneficiary under this Bank Guarantee shall be
forfeited, and we shall be released and discharged from all liabilities there under.
[Insert the address of the Bank with complete postal [Insert signature of the Bank’s Authorized
branch code, telephone and fax numbers, and official Signatory]
round seal of the Bank]
Attested
……………………………. [Signature] (Notary
Public)
Place: …………………………. Date: …………………………….
INSTRUCTIONS FOR SUBMITTING BANK GUARANTEE
1. Bank Guarantee to be executed on non-judicial stamp paper of appropriate value as per Stamp
Act relevant to place of execution.
2. The Bank Guarantee by Bidder shall be given from any Scheduled Commercial Bank.
3. The full address along with the Telex/Fax No. and e-mail address of the issuing bank to be
mentioned
Attachment-2
Format of Power of Attorney of designated Bid Signatory by sole bidder/ lead
joint venture member
[To be on non-judicial stamp paper of Rupees One Hundred Only (INR 100/-) or appropriate value as per
Stamp Act relevant to place of execution.]
Know all men by these presents, we …………………………………………….[Insert name and address of the
registered office of the Lead Consortium Member of the Bidding Consortium/ Sole Bidder] do hereby
constitute, appoint, nominate and authorize Mr./Ms. ………………………………………………… [Insert
name and residential address], who is presently employed with us and holding the position of
………………………………. as our true and lawful attorney, to do in our name and on our behalf, all such
acts, deeds and things necessary in connection with or incidental to submission of our Bid in response to RFB/
Tender No. [RFB/ Tender Details] for [Insert name of Package/ Contract title] (the “Project”) issued by
[Utility], including signing and submission of the Bid and all other documents related to the Bid, including but
not limited to undertakings, letters, certificates, acceptances, clarifications, guarantees or any other document
which Utility may require us to submit. The aforesaid attorney is further authorized for making representations
to Utility, and providing information / responses to Utility, representing us in all matters before Utility, and
generally dealing with Utility in all matters in connection with our Bid till the completion of the bidding process
as per the terms of the IFB.
We hereby agree to ratify all acts, deeds and things done by our said attorney pursuant to this Power of Attorney
and that all acts, deeds and things done by our aforesaid attorney shall be binding on us and shall always be
deemed to have been done by us. All the terms used herein but not defined shall have the meaning ascribed to
such terms under the RFB
Signed by the within named ........................................... [Insert the name of the executant company] through
the hand of Mr./ Mrs. ……………………………………….duly authorized by the Board/ Owner to issue
such Power of Attorney dated this ………………………. day of ………
Accepted
……………………………… (Signature of Attorney)
[Insert Name, designation and address of the Attorney]
Attested
…………………………………..
(Signature of the executant)
(Name, designation and address of the executant)
…………………………………….
Signature and stamp of Notary of the place of execution
Common seal of ……………… has been affixed in my/our presence pursuant to Board of Director’s
Resolution dated…./ Owner
General
This pre-bid pre-contract Agreement (hereinafter called the integrity Pact) is made on day of the month of
…………………. and year of ……………… , between on one hand, the Chairman & Managing Director acting through
Shri ……………….,Designation of the executive, Unit of <..name of utility…> (hereinafter called the "Utility"
which expression shall mean and include, unless the context otherwise requires, his successors in office and
assigns) of the First Part and M/s ………………………………. represented by Shri , Chief Executive Officer
(hereinafter called the "BIDDER/Seller" which expression shall mean and include, unless the context
otherwise requires, his successors and permitted assigns) of the Second Part.
WHEREAS the Utility proposes to procure (Name of the Stores/Equipment/item) and the Bidder/Seller is
willing to offer/has offered the stores and
Whereas the Bidder is a private company /public company/ Government undertaking/ partnership/
registered export agency, constituted in accordance with the relevant law in the matter and the Utility is a
Ministry/ Department of the Government of India/PSU performing its functions on behalf of its Chairman &
Managing Director.
NOW, THEREFORE,
To avoid all forms of corruption by following a system that is fair, transparent and free from any
influence/prejudiced dealings prior to, during and subsequent to the currency of the contract to be entered
into with a view to:-
Enabling the Utility to obtain the desired said stores/equipment at a competitive price in conformity with the
defined specifications by avoiding the high cost and the distortionary impact of corruption on public
procurement, and
Enabling BIDDERs to abstain from bribing or indulging in any corrupt practice in order to secure the contract
by providing assurance to them that their competitors will also abstain from bribing and other corrupt
practices and the Utility will commit to prevent corruption, in any form, by its officials by following
transparent procedures.
The parties hereto hereby agree to enter into this integrity Pact and agree as follows:
1.1 The Utility undertakes that no official of the Utility, connected directly or indirectly with the contract,
will demand, take a promise for or accept, directly or through intermediaries, any bribe, consideration, gift,
reward, favour or any material or immaterial benefit or any other advantage from the BIDDER, either for
themselves or for any person, organization or third party related to the contract in exchange for an advantage
in the bidding process, bid evaluation, contracting or implementation process related to the Contract.
1.2 The Utility will, during the pre-contract stage, treat all BIDDERs alike, and will provide to all BIDDERs
the same information and will not provide any such information to any particular BIDDER which could afford
an advantage to that particular BIDDER in comparison to other BIDDERs.
1.3 All the officials of the Utility will report to the appropriate Government office any attempted or
completed breaches of the above commitments as well as any substantial suspicion of such a breach.
2. In case any such preceding misconduct on the part of such official(s) is reported by the BIDDER to the
Utility with full and verifiable facts and the same is prima facie found to be correct by the Utility, necessary
disciplinary proceedings, or any other action as deemed fit, including criminal proceedings may be initiated
by the Utility and such a person shall be debarred from further dealings related to the contract process. In
such a case while an enquiry is being conducted by the Utility the proceedings under the contract would not
be stalled.
Commitments of Bidders
3. The BIDDER commits itself to take all measures necessary to prevent corrupt practices, unfair means
and illegal activities during any stage of its bid or during any pre-contract or post-contract stage in order to
secure the contract or in furtherance to secure it and in particular commit itself to the following:-
3.1 The Bidder will not offer, directly or through intermediaries, any bribe, gift, consideration, reward,
favour, any material or immaterial benefit or other advantage, commission, fees, brokerage or inducement
to any official of the BUYER, connected directly or indirectly with the bidding process, or to any person,
organization or third party related to the contract in exchange for any advantage in the bidding, evaluation,
contracting and implementation of the Contract.
3.2 The Bidder further undertakes that it has not given, offered or promised to give, directly or indirectly
any bribe, gift, consideration, reward, favor, any material or immaterial benefit or other advantage,
commission, fees, brokerage or inducement to any official of the Utility or otherwise in procuring the Contract
or forbearing to do or having done any act in relation to the obtaining or execution of the contract or any
other contract with the Government for showing or forbearing to show favor or disfavor to any person in
relation to the contract or any other contract with the Government.
3.3 BIDDERs shall disclose the name and address of agents and representatives and Indian BIDDERs shall
disclose their foreign principals or associates.
3.4 BIDDERs shall disclose the payments to be made by them to agents/brokers or any other
intermediary, in connection with this bid/contract.
3.5 The Bidder further confirms and declares to the Utility that the Bidder is the original manufacturer/
integrator/ authorized government sponsored export entity of the defense stores and has not engaged any
individual or firm or company whether Indian or foreign to intercede, facilitate or in any way to recommend
to the Utility or any of its functionaries, whether officially or unofficially to the award of the contract to the
Bidder, nor has any amount been paid, promised or intended to be paid to any such individual, firm or
company in respect of any such intercession, facilitation or recommendation.
3.6 The Bidder, either while presenting the bid or during pre-contract negotiations or before signing the
contract, shall disclose any payments he has made, is committed to or intends to make to officials of the
Utility or their family members, agents, brokers or any other intermediaries in connection with the contract
and the details of services agreed upon for such payments.
3.7 The Bidder will not collude with other parties interested in the contract to impair the transparency,
fairness and progress of the bidding process, bid evaluation, contracting and implementation of the contract.
3.8 The Bidder will not accept any advantage in exchange for any corrupt practice, unfair means and
illegal activities.
3.9 The Bidder shall not use improperly, for purposes of competition or personal gain, or pass on to
others, any information provided by the Buyer as part of the business relationship, regarding plans, technical
proposals and business details, including information contained in any electronic data carrier. The Bidder also
undertakes to exercise due and adequate care lest any such information is divulged.
3.10 The Bidder commits to refrain from giving any complaint directly or through any other manner
without supporting it with full and verifiable facts.
3.11 The Bidder shall not instigate or cause to instigate any third person to commit any of the actions
mentioned above.
3.12 If the BIDDER or any employee of the BIDDER or any person acting on behalf of the BIDDER, either
directly or indirectly, is a relative of any of the officers of the Utility, or alternatively, if any relative of an
officer of the Utility has financial interest/stake in the BIDDER’s firm, the same shall be disclosed by the
BIDDER at the time of filling of tender.
The term ‘relative’ for this purpose would be as defined in Section 6 of the Companies Act 1956.
3.13 The BIDDER shall not lend to or borrow any money from or enter into any monetary dealings or
transactions, directly or indirectly with any employee of the Utility.
4. Previous Transgression
4.1 The Bidder declares that no previous transgression occurred in the last three years immediately
before signing of this Integrity Pact, with any other company in any country in respect of any corrupt practices
envisaged hereunder or with any Public Sector Enterprise in India or any Government Department in India
that could justify Bidder’s exclusion from the tender process.
4.2 The BIDDER agrees that if it makes incorrect statement on this subject, BIDDER can be disqualified
from the tender process or the contract, if already awarded, can be terminated for such reason.
5.1 As per govt orders, EMD is not required to be submitted alongwith the bid and Bidders shall
undertake in Form as given in the RFP not to withdraw the bid during its validity period and shall not
withdraw the bid failing in which they will be suspended for 3 years period for participating in PFC tenders.
5.2 In the case of successful Bidder a clause would also be incorporated in the Article pertaining to
Performance Bond in the Purchase Contract that the provisions of Sanctions for Violation shall be applicable
for forfeiture of Performance Bond in case of a decision by the Utility to forfeit the same without assigning
any reason for imposing sanction for violation of this pact.
6.2 The Utility will be entitled to take all or any of the actions mentioned at para 6.1 (i) to (x) of this Pact
also on the Commission by the BIDDER or any one employed by it or acting on its behalf (whether with or
without the knowledge of the BIDDER), of an offence as defined in Chapter IX of the Indian Penal code, 1860
or Prevention of Corruption Act, 1988 or any other statute enacted for prevention of corruption.
6.3 The decision of the Utility to the effect that a breach of the provisions of this Integrity Pact has been
committed by the Bidder shall be final and conclusive on the Bidder. However, the Bidder can approach the
independent monitor(s) appointed for the purposes of this Pact.
8. Independent Monitors
8.1 The Utility has appointed Independent Monitors (hereinafter referred to as Monitors) for this Pact in
consultation with the Central Vigilance Commission (Name & Addresses of Monitors to be given).
8.2 The task of the Monitors shall be to review independently and objectively, whether and to what
extent the parties comply with the obligations under this Pact.
8.3 The monitors shall not be subject to instructions by the representatives of the parties and perform
their functions neutrally and independently.
8.4 Both the parties accept that the Monitors have the right to access all the documents relating to the
project/ procurement, including minutes of meetings.
8.5 As soon as the Monitor notices, or has reason to believe, a violation of this Pact, he will so inform the
Authority designated by the Utility.
8.6 The BIDDER(s) accepts that the Monitor has the right to access without restriction to all Project
documentation of the Utility including that provided by the BIDDER. The BIDDER will also grant the Monitor,
upon his request and demonstration of a valid interest, unrestricted and unconditional access to his project
documentation. The same is applicable to Subcontractors. The Monitor shall be under contractual obligation
to treat the information and documents of the BIDDER/Subcontractors(s) with confidentiality.
8.7 The Utility will provide to the Monitor Sufficient information about all meetings among the parties
related to the Project provided such meetings could have an impact on the contractual relations between the
parties. The parties will offer to the Monitor the option to participate in such meetings.
8.8 The Monitor will submit a written report to the designated Authority of Utility/Secretary In the
department/ within 8 to 10 weeks from the date of reference or intimation to him by the Utility/ BIDDER and
should the occasion arise, submit proposals for correcting problematic situations.
9. Facilitation of investigation
IN case of any allegation of violation of any provisions of this Pact or payment of commission, the Utility or
its agencies shall be entitled to examine all the documents including the Books of Accounts of the BIDDER and
the BIDDER shall provide necessary information and documents in English and shall extend all possible help
for the purpose of such examination.
12 Validity
12.1 The validity of this Integrity Pact shall be from date of its signing and extend upto 5 years or the
complete execution of the contract to the satisfaction of both the Utility and the BIDDER/ Seller, including
warranty period, whichever is later. In case BIDDER is unsuccessful, this integrity Pact shall expire after six
months from the date of the signing of the contract.
12.2 Should one or several provisions of this Pact turn out to be invalid; the remainder of this Pact shall
remain valid. In this case, the parties will strive, to come to an agreement to their original intentions.
Utility BIDDER
Name of the officer CHIEF EXECUTIVE OFFICER
Designation
<…name of utility…>.
Witness Witness
1. ………………………………….. 1. …………………………………………
2. ………………………………….. 2. ………………………………………….
*Provisions of these clauses would need to be amended /deleted in line with the policy of the BUYER in
regard to involvement of Indian agents of foreign suppliers.
Form F- 4: Manufacturer’s Authorization
(To be obtained from all OEMs)
Date:
DCB No.:
Invitation for Bid No.:
To:
We hereby extend our full guarantee and warranty in accordance with Clause E ( 25 to 29) of the
General Conditions of Contract, with respect to the Goods offered by the above firm in reply to this
Invitation for Bids.
Name
In the capacity of:
Signed
Duly authorized to sign the Authorization for and on behalf of
Form F- 5: Certificate as to Corporate Principal
Signature:
Full Name:
Address:
Attachment-12
Declaration regarding Local content for granting of Purchase Preference
Agreement
WHEREAS the Purchaser had invited bids for certain Goods and RelatedServices, viz.,
(eg. Nameof
bid) vide their bid document number ,
dated
AND WHEREAS various applications were received pursuant to the said bid
AND WHEREAS the Purchaser has accepted a Bid by the Supplier for the supply of thoseGoods
and Related Services in the sum
of
(hereinafter “the
Contract Price”).
And in pursuance of having accepted the said bid the parties have agreed to enter into this
1. In this Agreement words and expressions shall have the same meanings as are
respectively assigned to them in the Contract referred to.
3. In consideration of the payments to be made by the Purchaser to the Supplier as indicated in this Agreement,
the Supplier hereby covenants with the Purchaser to providethe Goods and Related Services and to remedy the
defects therein and bring them in conformity in all respects with the provisions of the Contract.
4. The Purchaser hereby covenants to pay the Supplier in consideration of the provision of the Goods and
Related Services and the remedying of defects therein, the Contract Priceor such other sum as may become payable
under the provisions of the Contract at the timesand in the manner prescribed by the Contract.
IN WITNESS whereof the parties hereto have caused this Agreement to be executed inaccordance with the
laws of on the day, month and year indicated above.
Supplier)
Witness-1
Witness-2
PERFORMANCE SECURITY FORM
Bank Guarantee No. …………………… Date...................
Contract No.....................................
…………..[Name of Contract]…………………….
We refer to the Contract ("the Contract") signed on ..............(insert date of the Contract)…..... between
M/s. XXXXX (Name of Employer), having its Registered Office at XXXXX (Registered Address of
employer) (“the Employer”/” XXXXX (Name of Employer)”) on behalf of XXXX (Name of owner)
(hereinafter referred to as ‘XXXX (Short Name of Owner)’ / ’Owner’), and M/s ................. (Name of
Contractor) .................................................................................................................................,
having its Principal place of business at ………....(Address of Contractor)
............................... and Registered Office at ………....(Registered address of Contractor)
........................................................................................ ("the Contractor") concerning
…….................….. (Indicate brief scope of work) ............................... for the complete execution of the
…… (insert name of Package along with name of the Project)……..
[Applicable for Bank Guarantees issued by Contractor/Associate for those Contracts awarded to them]
Or
We refer to the Contract signed on ..............(insert date of the Contract)… between M/s.
XXXXX (Name of Employer), having its Registered Office at XXXXX (Registered Address of employer)
(“the Employer”/” XXXXX (Name of Employer)”) on behalf of XXXX (Name of owner) (hereinafter
referred to as ‘XXXX (Short Name of Owner)’ / ’Owner’), and M/s ................. (Name of Contractor)
.................., having its Principal place of business at
………....(Address of Contractor) ............................... and Registered Office at
………....(Registered address of Contractor)
........................................................................................ ("the Contractor") and the Contract
("the Contract") signed on ..............(insert date of the Contract)…..... between XXXXX
(Name of Employer) on behalf of Owner and M/s ................. (Name of Associate)
.................., having its Principal place of business at ………....(Address of Associate)
............................... and Registered Office at ……....(Registered address of Associate)
By this letter we, the undersigned, ………(insert name & address of the issuing bank)
………, a Bank (which expression shall include its successors, administrators, executors and assigns)
organized under the laws of .................................... and having its Registered/Head Office at
…..…….(insert address of registered office of the bank)……..... do hereby irrevocably guarantee payment
to the Employer up to ………………………….. i.e., Three percent (3%) of the Contract Price until thirty
(30) days beyond the Defect Liability Period i.e., upto and inclusive of (dd/mm/yy).
We undertake to make payment under this Letter of Guarantee upon receipt by us of your first written
demand signed by the Employer duly authorized officer or the authorized officer of Owner declaring the
Contractor to be in default under the Contract and without cavil or argument any sum or sums within the
above named limits, without your need to prove or show grounds or reasons for your demand and without
the right of the Contractor to dispute or question such demand.
Our liability under this Letter of Guarantee shall be to pay to the Employer whichever is the lesser of the
sum so requested or the amount then guaranteed hereunder in respect of any demand duly made hereunder
prior to expiry of the Letter of Guarantee, without being entitled to inquire whether or not this payment is
lawfully demanded.
This letter of Guarantee shall remain in full force and shall be valid from the date of issue until thirty (30)
days beyond the Defect Liability Period of the Facilities i.e. upto and inclusive of (dd/mm/yy) and shall
be extended from time to time for such period (not exceeding one year), as may be desired by M/s on
whose behalf this Letter of Guarantee has been given.
Except for the documents herein specified, no other documents or other action shall be required,
notwithstanding any applicable law or regulation.
Our liability under this Letter of Guarantee shall become null and void immediately upon its expiry, whether
it is returned or not, and no claim may be made hereunder after such expiry or after the aggregate of the
sums paid by us to the Employer shall equal the sums guaranteed hereunder, whichever is the earlier.
All notices to be given under shall be given by registered (airmail) posts to the addressee at the address
herein set out or as otherwise advised by and between the parties hereto.
We hereby agree that any part of the Contract may be amended, renewed, extended, modified, compromised,
released or discharged by mutual agreement between you and the Contractor, and this security may be
exchanged or surrendered without in any way impairing or affecting our liabilities hereunder without notices
to us and without the necessity for any additional endorsement, consent or guarantee by us, provided,
however, that the sum guaranteed shall not be increased or decreased.
No action, event or condition which by any applicable law should operate to discharge us from liability
hereunder shall have any effect and we hereby waive any right we may have to apply such law so that in all
respects our liability hereunder shall be irrevocable and, except as stated herein, unconditional in all respects.
Signature
Name
Designation
POA Number
Fax Number
Signature
Name
Address
Note :
1. For the purpose of executing the Bank Guarantee, the non-judicial stamp papers of
appropriate value shall be purchased in the name of Bank who issues the ‘Bank
Guarantee’.
2. The Bank Guarantee shall be signed on all the pages by the Bank Authorities indicating
their POA nos. and should invariably be witnessed.
3. The Bank Guarantee should be in accordance with the proforma as provided. However,
in case the issuing bank insists for additional paragraph for limitation of liability, the
following may be added at the end of the proforma of the Bank Guarantee [i.e., end
paragraph of the Bank Guarantee preceding the signature(s) of the issuing
authority(ies) of the Bank Guarantee]:
Quote
1. Our liability under this Bank Guarantee shall not exceed ________(value in
figures)_________________(value in words).
2. This Bank Guarantee shall be valid upto (validity date) .
3. We are liable to pay the guaranteed amount or any part thereof under this Bank
Guarantee only & only if we receive a written claim or demand on or before
(validity date) .”
Unquote
Format of Bank Guarantee verification Check list
Bidder’s Name and Address: To: XXXXX (Name and Address of Employer)
{In case of JV bidder, mention name
and address of all the Joint Venture members}
Dated the ……………. [Insert date of the month] day of ...................... [Insert month, year]
at ...................... [Insert place].
Signature {(of Bidder’s authorized Bid Signatory (ies)}# {In full and initials}:
The Purchaser will select a Supplier (also referred as the ‘bidder’) in accordance with the eligibility
criteria indicated in Section IV.
The bidders are invited to submit a Technical Proposal and a Price Proposal for goods and related
services required for the project as defined in Section VI, Scope of Work .This proposal will be the
basis for contract negotiations and finalization of the contract with the successful bidder.
The bidders must familiarize themselves with local conditions and take these into account while
preparing their proposals. To facilitate the bidders in making the Proposal, the Purchaser shall have a
“Pre-Bid conference” at the address and date as given in ITB, Section II. Please note that:
Costs involved in preparation of the proposal and of negotiating the contract, includinga visit to
the Purchaser, are not reimbursable.
The final evaluation shall be as per the evaluation methodology mentioned eligibilitycriteria.
Please check all attachments with the checklist provided at the end, prior tosubmission of
bid.
C 1.1: Guidelines for Technical proposal
In preparing the Technical Proposal, bidders are expected to examine this Bid document in detail. The
proposal should cover all the aspects of this bid document. Any bid not found responsive to this bid
document shall be rejected. Material deficiencies in providing the information requested may also result
in rejection of the proposal. The price proposal should follow standard formats/forms as given in
Appendix C3
While preparing the technical proposal, bidders must give particular attention that thetechnical proposal
does not include any financial information.
Company Statistics
Please provide the general and financial details of each of the entities (bidder, consortiummember
(if any) and subcontractors) in the following formats:
Table: Bidder – Company Statistics
Bidder’s Name
Address
Contact (s), Title (s), Telephone (s), E-mail id(s)
Bidders need to submit the details as per the format in the table provided.
Table: The details of the same should be included in the following format and necessarysupporting
documents should be attached with RFP:
1
2
3
4
5
6
7
Note : Kindly provide Client Performance Certificates for the completed projects
provided for establishing/confirming the requisite details for project experience as
mentioned above
Or Copy of LoA/ Work Order along with proof of release of final payment
C 2.3: Firm Detail
Bidder shall provide details of net-worth and turnover for the past three audited financialyears in
the following format:
Firm
Detail
Details FY 2019-20 FY 2020-21 FY 2021-22
Net-worth
Turn-Over
Audited financial reports and copy of the certificates supporting the above need to besubmitted as
proof.
Bidder must provide details of how they envisage the contract being managed including
principles such as (but not limited to) joint planning and control mechanisms; regular and active
review meetings; Project management of individual work streams and overall program
management of the entire service; Performance reporting
Bidder should outline their proposed governance structure and designate a Service Manager to
co-ordinate their activities and provide a focal point of contact to whom Utility can refer on any
matter concerning the service.
Reporting lines and decision-making powers within the bidder’s organization must be
explained
Outline the proposed escalation procedures in the event that issues arise.
Details of Certification
Description Bidder’s
Response
Please specify your company’s process for product development and enhancements
Utilities to prepare the detailed price schedules as per the Sample Price schedule is providedhereunder:
Price proposal
Bidders are requested to provide cost for each of the Project Area in the subsequent formats. The
Bidders should take a note of following points while filling the Price proposal.
1) Bidder will be responsible for payment of Taxes (including local entry taxes), duties, cess,
charges etc, including taxes, duties, cess, charges etc, to be paid by the Supplier pre- or post-
delivery. Such taxes, duties, cess, charges etc, if not explicitly mentioned in the following
tables, but applicable under law, should be included in the Quote under “Any other levies”
column.
2) The Bidder will provide Tax rates assumed for the calculation at the time of proposal for
each item in notes to respective table.
3) Please refer to GCC Clause 12.2 and the SCC for Price adjustments due to change in Tax
rates (including local entry taxes), duties, cess, charges etc.
4) Purchaser reserves the right to deduct and pay to the government authorities the taxes at
applicable rates from the price payable to the supplier.
5) The unit prices mentioned for various components should be the same for all Project Areas.
In case of any discrepancy among unit prices of various Project Areas, the lowest unit price
of equipment mentioned for any Project Area shall prevail.
Sub-Total A1
Grand Total A Rs.
Server/ workstation
D1
Hardware
SCADA Server No.
DMS Server No.
OMS Server No.
FEP server with interface
No.
switches
ISR server No.
NMS server No.
DTS server No.
Other Active Devices no
Developmental server No.
Commnuication Server No.
Web/Directory server No.
SMS gaterway No.
D2 Software
SCADA software Lot
ISR Software Lot
DMS software Lot
DTS software Lot
OMS Software Lot
Developmental software Lot
Network Management Software Lot
RDBMS package (incl in ISR)
WEB /Network security
(Incl in web server)
software
GIS Adaptor/Engine for
importing data from GIS Lot
system under IT system
Any other item to meet
Lot
specification requirements
Form 5
Per
Unit FMS Cost
Total
S.No. Equipment Unit Quantity Cost / year
(incl
taxes
&
duties)
)
Rs. Rs. Rs
F1 FRTUs
Form 6
Per UnitCost
(incl
Total FMS Cost / year
S.No Equipment Unit Quantity taxes &
duties)
Rs. Rs. Rs.
G1 MPLS
Annual charges for
100MBps Links with No.
RTUs
Modems No.
Sub- Total H1
Main Equipments -
H2 DR Centre
Main Equipments
UPS with suitable
rating running in
parallel redundant
mode*
VRLA type Battery
banks for above UPS
for minimum 30 min.
backup duration
Sub-Total H2
II For RTU / Data
Concentrator /
H3
Communication
Eqpts.
DC Power Supply
(DCPS) system
based on SMPS
Battery bank for
above DCPS
(VRLA Type) for
minimum 4 hrs
backup
Sub-Total H3
H4 For FRTU
48V DC Power
Supply (DCPS)
system based on
SMPS
Battery bank for
above DCPS
Form 8
J3 FPI
Commnuicable No
Sub-Total J3
RECONDUTORING
(Specify type of each
J4
conductor existing &
reconductoring )
Km
Km
Sub-Total J4
Control/power cable
for RTUs from
J5
outdoor
switchgear,if any at
Form 9 : Training
Description Duration Total Cost (Rs.)
in days
A. Operator’s Training
1. Operator for SCADA/DMS Control Centre 5
2. Instructor for DTS 10
B. Maintenance Training
1 Computer Hardware & System Software 10
2. Application Software (SCADA/DMS) 10
3. RTU & FRTU 5
4. Database & display development 5
6. Auxiliary Power Supply 3
7. Communication System including NMS 5 2
Form10 : FMS
S.No. Description Duration Peer FOR FOR
YEAR 2YEARS 5YEARS
cost ( Addl
3yrs)
1 FMS charges for SCADA/DMS Per year
system (maintaining overall system
availability as per TS)
2 FMS charges for SCADA/DMS Per
system (maintaining availability year
individual hardware & non –critical
functions as per TS)
3 Total FMS charges
The necessary spares required for maintenance of the system during FMS shall be provided by the
contractor. However, the consumables shall be provided by the owner.
FMS shall include all the supplied hardware & software under the project
Cost of overall system availability/year shall not be less than 40 % and more than 60% of total
FMS charges/year
Sub-Total A1
Grand Total A Rs.
Storage &
Backup Devices
External RAID
Mass storage
device ( for 24 No.
months online
backup)
Exteranl DAT
No.
drive
Switches
Layer II switch
(SCADA/DMS No.
LAN)
Layer II switch (
Planning &
No.
Development
system LAN)
Routers
Router for
interfacing IT
system & No.
SCADA/DMS
DR centre
Router at remote
No.
VDU
Security system
(DMZ)
Web server with
No.
load balancing
Mail server No.
Router No.
Firewall &
No.
network IDS/IPS
Layer II switch No.
Other Active
Devices
FORM 3
Per
Unit Total FMS Cost / year
S.No. Equipment Unit Quantity Cost
(incl
taxes
&
duties)
Rs. Rs. Rs
Server/ workstation
D1
Hardware
DR server No.
Commnuication
No.
Server
Workstation with
No.
one TFT Monitors
Storage & Backup
Devices
External storage
No.
device
Exteranl DAT drive No.
Switches
Layer II switch (DR
No.
LAN)
Routers
Router for
interfacing at No.
SCADA DMS centre
Printers
Color inkjet printer Set
FORM-4
Per
Unit Total FMS Cost / year
S.No. Equipment Unit Quantity Cost
(incl
taxes
&
duties)
Rs. Rs. Rs
E1 RTUs B &C -TYPE
RTU base equipment
comprising panels,
racks, sub-racks,
Power Supply
modules, CPU,
interfacing equipment,
required converters &
all other required
items/accessories
including complete
wiring for all modules
for locations
mentioned
Multifunctuions
transducers
Contact Multiplying
Relays (CMRs)
Heavy duty relays for
Control
Dummy Breaker
Latching Relays
Transformer
Transducers
Single TFT PC for
LDMS with 2KVA
UPS
Total FMS
(per Total Cost /
S.No Equipment Unit Quantity unit) year
Rs. Rs. Rs
G1 MPLS
Annual charges for 100MBps Links with
A) No.
RTUs
G2 Sub - Total g1
GPRS/MPLS-4G
B) Modems No.
FORM 7
Per FMS
Unit Total Cost /
S.No. Survey Unit Quanti Cost year
ty (incl
taxes &
duties)
Rs. Rs. Rs
H1 Main Equipments - Control centre
UPS with suitable rating running in
parallel redundant mode*
VRLA type Battery banks for above UPS
for minimum 30 min. backup duration
Sub- Total H1
Form 8
Per Unit FMS
Cost (incl Total Cost /
S.No. Survey Unit Quantity taxes & year
duties)
Rs. Rs. Rs
J1 RMU
RMU No
- -
Sub- Total J1 -
J2 SECTIONLIZER /RECLOSER
Sectionlizer recloser No
- -
Sub-Total J2 -
Commnuicable No
- -
Sub-Total J3 -
RECONDUTORING
(Specify type of each
J4
conductor existing &
reconductoring )
Km - -
Km - -
Sub-Total J4 -
Control/power cable for
RTUs from outdoor
J5
switchgear, numerical relays
if any at S/S
Control /Power cables
Km - -
Numerical relay
Nos - 1 -
Sub-Total J5
-
J6 Mandatory Spares
5% of above J1 TO J5
- -
Sub-Total J6 -
Grand Total (J)
-
Form 9 : Training
The necessary spares required for maintenance of the system during FMS shall be provided by the
contractor. However, the consumables shall be provided by the owner.
FMS shall include all the supplied hardware & software under the project
Cost of overall system availability/year shall not be less than 40 % and more than 60% of total
FMS charges/year
Sub-Total A1
Grand Total A Rs.
Server/
D1 workstation
Hardware
SCADA Server No.
DMS Server No.
OMS Server No.
FEP server with
interface No.
switches
ISR server No.
NMS server No.
DTS server No.
Other Active
no
Devices
Developmental
No.
server
Commnuication
No.
Server
Web/Directory
No.
server
SMS gaterway No.
Workstation with
dual TFT
No.
Monitors ( S/S
monitoring)
Workstation with
dual TFT
Monitors No
(Network
monitoring)
Remote VDUs
with one TFT No.
Monitors
Developmental
console with one No.
TFT
DTS/Workstation
Console with No.
dual TFTs
Storage &
Backup Devices
External RAID
Mass storage
device ( for 24 No.
months online
backup)
External DAT
No.
drive
Switches
Layer II switch
(SCADA/DMS No.
LAN)
Layer II switch (
Planning &
No.
Development
system LAN)
Routers
Router for
interfacing IT
system & No.
SCADA/DMS
DR centre
Router at remote
No.
VDU
Security system
(DMZ)
Web server with
No.
load balancing
Mail server No.
Router No.
Firewall &
No.
network IPS/IDS
Layer II switch No.
Other Active
Devices
GPS Time
synchronisation Set
system
Time, day & date
Set
digital displays
Printers
Server/
D1 workstation
Hardware
SCADA Server No.
DMS Server No.
OMS Server No.
FEP server with
interface No.
switches
ISR server No.
NMS server No.
DTS server No.
Other Active
no
Devices
Developmental
No.
server
Commnuication
No.
Server
Web/Directory
No.
server
SMS gaterway No.
Workstation with
dual TFT
No.
Monitors ( S/S
monitoring)
Workstation with
dual TFT
Monitors No
(Network
monitoring)
Remote VDUs
with one TFT No.
Monitors
Developmental
console with one No.
TFT
DTS/Workstation
Console with No.
dual TFTs
Unit Price
(Inclusive FMS Cost /
S.No. Equipment Un Quantity ofall taxes, TotalCost year
it duties,
Freight
&Insurance
)
Rs. Rs. Rs
E1 RTUs
RTU base equipment
comprising panels,
racks, sub-racks,
Power Supply
modules, CPU,
interfacing equipment,
required converters &
all other required Set
items/accessories
including complete
wiring for all modules
for
locations mentioned
Multifunctuions
No.
transducers
Contact Multiplying
No.
Relays (CMRs)
Heavy duty relays
No.
for Control
Dummy Breaker
No.
Latching Relays
Transformer
No.
Transducers
Single TFT PC for
No
LDMS INCL
2KVA UPS
Any other hardware
to meet functional
Lot
/performance
requirement of MTS
Sub - Total
(Hardware) -E1
E2 Software for LDMS
LDMS software No.
Any other software
to meet functional
Lot
/performance
requirement of MTS
Sub - Total (test
equipment) -E2
TEST
E3 EQUIPMENTS for
RTU
<Utility Name> Page <Date of release of Document>
166
RTU Database
Configuration &
No.
Maintenance
Software tool
Master Station cum
RTU Simulator &
No.
Protocol analyser
software tool
Laptop PC for above
software tools along
with interfacing No.
hardware including
Hub
Sub - Total (test
equipment) -E3
MANDATORY
E4 SPARES FOR RTU
5% of E1
Sub - Total
(mandatory spare) -
D4
Grand total E
Form 5
Unit Price
(Inclusive Total FMS Cost
S.No. Equipment Unit Quantity ofall / year
taxes,
duties,
Freight
&Insuran Rs. Rs
ce)
F1 FRTUs
Form 6
Unit Price
(Inclusive ofall Total FMS Cost / year
S.No Equipment Unit Quantity taxes, duties,
Freight
&Insuranc
e)
Rs. Rs. Rs.
MPLS
Annual charges for
100MBps Links with No.
RTUs
Sub - Total g1
GPRS/MPLS-4G
Annual charges for
2MBps Links with No.
FRTUs /FPI
Modems No.
Form 7
Unit Price
(Inclusive FMS Cost /
Total
S.No. Survey Unit Quantity ofall taxes, year
duties,
Freight
&Insuranc
e)
Rs. Rs. Rs.
Main Equipments -
H1
Control centre
UPS with suitable
rating running in
Set
parallel redundant
mode*
VRLA type Battery
banks for above UPS
for minimum 30 min.
backup duration Set
Sub- Total H1
Main Equipments -
H2
DR Centre
Main Equipments
UPS with suitable
rating running in
parallel redundant
mode*
VRLA type Battery
banks for above UPS
for minimum 30 min.
backup duration
Sub-Total H2
II For RTU / Data
Concentrator /
H3
Communication
Eqpts.
DC Power Supply
(DCPS) system
based on SMPS
Battery bank for
above DCPS
(VRLA Type) for
minimum 4 hrs
backup
Sub-Total H3
H4 For FRTU
<Utility Name> Page <Date of release of Document>
169
48V DC Power
Supply (DCPS)
system based on
SMPS
Battery bank for
above DCPS
(VRLA Type) for
minimum 4 hrs
backup
Sub-Total H4
Remote VDU
H5
location
UPS (2 kVA )
Sub-Total H5
Mandatory Spares
H6
for UPS
5% of above H1TO
H5
Sub-Total H6
Grand Total (H)
Form 8
&Insuranc
e)
Rs. Rs. Rs.
RMU (WAY No of
J1 requirement) WAYS
RMU No
Sub- Total J1
SECTIONLIZER
J2 /RECLOSER
Sectionlizer No
Recloser No
Sub-Total J2
J3 FPI
Commnuicable No
Sub-Total J3
RECONDUTORING
(Specify type of each
J4
conductor existing &
reconductoring )
Km
<Utility Name> Page <Date of release of Document>
170
Km
Sub-Total J4
Control/power cable
for RTUs from
outdoor
J5
switchgear,if any at
S/S and numerical
relays
control /power cable Km
Numerical relay
/BCPU Nos
Sub-Total J5
J6 Mandatory Spares
5% of above J1 TO J5
Sub-Total J6
Grand Total (J)
Form 9 : Training
Form10 : FMS
S.No. Description PER 2YEARS 3 more years
YEAR initial years
after
opertiona
l
acceptanc
e
Cost of FMS for overall cost system availability shall not be less than 40% or not more than 60%
of total FMS cost
FMS Cost of all items shall be specified. FMS cost of non critical items such as printer ,
DAT, DTS consoles , DTS server shall not be more 10% of unit rate of item and no FMS for
Bandwidth charges . The same needs to be specified in the cost and shall be paid on SLA on
actual usage basis
The necessary spares required for maintenance of the system during FMS shall be provided by the
contractor. However, the consumables shall be provided by the owner.
Bidder can define quantity of servers , router, switches as per system configuration in the bid subject to
adherence to functional , performance , redundancy , cyber security and all technical requirements . The
quantity shall be as per indicative quantity in Chapter 19 , Table 9 . However , utility to define quantity as
per approved project and bidder can define quantity of servers , router, switches as per system
configuration of the proposal in the bid subject to adherence to functional , performance , redundancy ,
cyber security and all technical , test requirements .
Unit price is inclusive of taxes, freight and insurance, However , GST % to be indicated by bidder for items
Total cost of basic RTU in form 4 row 1 shall comparable with the breakup given below in Form 11.
This is to derive unit rate of the modules
Total (per
Total
S.No. Equipment Unit Quantity unit)
Rs. Rs.
A RTUs
1 Power supply
No.
module
2 CPU Module
No.
3 Communication
No.
module (Specify
no of Ethernet
and serial ports
4 Digital Input
No.
(DI) Module
(Specify no of
channels
5 Digital
No.
Output
(DO)
Module
(Specify no
of channels
6 Analog input if
No
any (AI)
Module (Specify
no of channels
7 Any other hardware
to meet functional
Lot
/performance
requirement of MTS
Sub - Total (1
TO 7 = (ROW
1 OF FORM
F4)
Total cost of basic FRTU in form 4 row 1 shall be comparable with the breakup given below in
Form 11. This is to derive unit rate of the modules
Total (per
Total
S.No. Equipment Unit Quantity unit)
Rs. Rs.
A FRTUs
1 Power supply
No.
module
2 CPU Module
No.
3 Communication
No.
module (Specify
no of Ethernet
and serial ports
4 Digital Input
No.
(DI) Module
(Specify no of
channels
5 Digital
No.
Output
(DO)
Module
(Specify no
of channels
6 Analog input if
No
any (AI)
Module (Specify
no of channels
7 Any other hardware
to meet functional
Lot
/performance
requirement of MTS
Sub - Total (1
TO 7 = (ROW
1 OF FORM
F5)
C 4.2:Compliance checklist
2 Please confirm you have submitted all the mandatory forms Yes/ No
specified in Appendix C (Technical & Financial Proposal)
3 Please confirm you have noted the bid submission deadline Yes/ No
specified in Section III, BDS (ITB 23.1)
4 Please confirm you have noted that the performance security will Yes/ No
be furnished within time period as specified in Section II, ITB
clause 42.1
Facilities Management Services post successful completion of acceptance tests shall be provided for a
period of five years from the date of completion of acceptance test.
Bidder shall submit a detail Gantt chart as per along with the following implementation schedule.
Bidders shall drill down these activities into sub/sub-sub activity in the chart. The chart shall also detail
out time and resource effort required to execute each activity. The detailed bar charts for all the work
activity shall however, be discussed and agreed to by the successful Bidder with the owner before start
of the execution of work.
Table 7: Expected Implementation Schedule
Sta En
Activity/ Sub Activity Weekly Plan
rt d
W1 W2 W3 W4 W5 …
1 Mobilization at site with establishment of site
office, requisite resource deployment etc.
2 Field Survey for SCADA/DMS Data
3 System Design (Pre-Implementation Plan,
Testing and Development) and Approval
4 Factory Acceptance Test (FAT)
- RTUs
- FRTUs
- Communication Equipment
Table of Contents
CHAPTER-1: INTRODUCTION & GENERAL INFORMATION ...................................................... 1
1.0 Introduction: ............................................................................................................................ 1
1.1 Objectives ............................................................................................................................... 1
1.2 Parts of the Scheme ................................................................................................................. 1
1.2.1 Eligible Works and Activities under Part A – Metering ................................................. 1
1.2.2 Eligible Works and Activities under Part A- Distribution Infrastructure Works ............ 2
1.2.3 Eligible entities for Part A .............................................................................................. 2
1.2.4 Eligible Works and Activities under Part B .................................................................... 3
1.3 SCADA /DMS system ............................................................................................................ 3
1.3.1 Groups of SCADA system eligibility criteria’s & components ...................................... 3
1.3.2 Make in India ................................................................................................................ 10
1.3.3 Broad Role Definition for SIA ...................................................................................... 10
1.3.4 Specific Exclusions ....................................................................................................... 14
1.3.5 Generic requirements .................................................................................................... 14
1.3.6 Facilities to be provided by Employer/Owner (Utility) ................................................ 15
1.3.7 General Requirements ................................................................................................... 15
1.3.8 General Bidding Requirements ..................................................................................... 16
1.3.9 Items of Special Interest ................................................................................................ 17
1.3.10 Site Conditions .............................................................................................................. 17
1.3.11 Applicable Standards .................................................................................................... 17
1.3.12 Warranty ....................................................................................................................... 18
1.3.13 Terms for utility & SIA ................................................................................................. 18
1.3.14 Proposed SCADA/DMS system ................................................................................... 18
1.3.15 Existing System for Group A , B, C & U towns separately. ......................................... 19
CHAPTER -2: SCADA FUNCTIONS ................................................................................................. 20
2.0 General requirements ............................................................................................................ 20
2.1 Design requirements ............................................................................................................. 20
2.1.1 SCADA/DMS Function Access ............................................................................................ 20
2.1.2 Critical & non critical functions ............................................................................................ 20
2.2 SCADA Functions .................................................................................................................... 21
2.2.1 Communication protocol....................................................................................................... 22
2.2.2 Data Acquisition ................................................................................................................... 23
2.2.2.1 Polling method .................................................................................................................. 23
2.2.2.2 Telemetry Failure .............................................................................................................. 24
2.2.3 Time synchronization of RTUs ............................................................................................. 25
2.2.4 Data Exchange ...................................................................................................................... 25
2.2.5 Data Processing ..................................................................................................................... 26
2.2.6 Continuous Real-time data storage and playback ................................................................. 30
Page i
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
2.2.7 Sequence-of-Events data ....................................................................................................... 31
2.2.8 SCADA language.................................................................................................................. 31
2.2.9 Supervisory Control .............................................................................................................. 31
2.2.10 Fail-soft capability ................................................................................................................ 35
2.2.11 Remote database downloading, diagnostics & configuration ............................................... 35
2.3 Information Storage and Retrieval ............................................................................................ 35
2.3.1 Circuit breaker status Table .................................................................................................. 36
2.3.2 Real-time Database Snapshot Tables .................................................................................... 36
2.3.3 Hourly Data tables ................................................................................................................ 37
2.3.3.1 Missed Hourly Data Storage ................................................................................................. 37
2.3.3.2 Hourly Data Calculations ...................................................................................................... 38
2.3.4 SAIDI/SAIFI table ................................................................................................................ 38
2.3.5 Daily Energy Data table ........................................................................................................ 38
2.3.6 Load priority table................................................................................................................. 38
2.3.7 SOE data table....................................................................................................................... 39
2.3.8 Feeder Limit overshoot table ................................................................................................ 39
2.3.9 FPI fault table ....................................................................................................................... 39
2.3.10 Equipment Failure Table....................................................................................................... 39
2.3.11 User defined index table ....................................................................................................... 39
2.3.12 Average time restoration table .............................................................................................. 39
2.3.13 Daily /Weekly Flash report for management of utility ......................................................... 40
2.3.14 Historical Information (HI) Data Retrieval ........................................................................... 40
2.3.15 System Message Log Storage and Retrieval ......................................................................... 40
2.3.16 Mass storage of data/files ...................................................................................................... 40
2.4 Load Shed Application (LSA) .................................................................................................. 40
2.4.1 Basic rules for load shedding & restoration .......................................................................... 41
2.4.2 Modes of operation ............................................................................................................... 41
2.4.2.1 Manual Load Shed ................................................................................................................ 41
2.4.2.2 Manual Load Restoration ...................................................................................................... 42
2.4.2.3 Auto Load Shed .................................................................................................................... 42
2.4.2.4 Auto Load Restoration .......................................................................................................... 42
2.4.3 Alarms/Events ....................................................................................................................... 43
2.4.4 Summary Report ................................................................................................................... 43
2.5 Common Disaster Replica Recovery Centre ( DRR) ................................................................ 43
2.6 Data recovery function (DR) ..................................................................................................... 43
2.7 RT-DAS system ........................................................................................................................ 44
CHAPTER 3: DMS FUNCTIONS & SUPPORTING FUNCTIONS .................................................. 45
3.0 General Requirements ........................................................................................................... 45
3.1 DMS functions ...................................................................................................................... 45
Page ii
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
3.1.1 Network Connectivity Analysis (NCA) ........................................................................ 51
3.1.2 State Estimation ............................................................................................................ 53
3.1.3 Load Flow Application (LFA) ...................................................................................... 55
3.1.4 Volt –VAR Control (VVC) ........................................................................................... 58
3.1.5 Fault Management & System Restoration (FMSR) Application .................................. 59
3.1.6 Loss Minimization via Feeder Reconfiguration (LMFR) ............................................. 62
3.1.7 Load Balancing via Feeder Reconfiguration (LBFR) ................................................... 63
3.1.8 Operation Monitor......................................................................................................... 64
3.2 Outage Management System ................................................................................................ 65
3.2.1 Outage Scheduling Management .................................................................................. 65
3.2.2 Trouble Call Management System ................................................................................ 65
3.2.3 Crew Dispatch & Work Management Key Features..................................................... 66
3.2.4 Outage Analytics & Reporting ...................................................................................... 67
3.2.5 Web Clients & Mobile Views ....................................................................................... 67
3.3 Disptacher Training Simulator (DTS)................................................................................... 68
3.3.1 Instructor Control .......................................................................................................... 69
3.3.2 Trainee control .............................................................................................................. 69
3.3.3 Pre-Session Activities ................................................................................................... 69
3.3.4 Scenario Construction ................................................................................................... 69
3.3.5 Event Types .................................................................................................................. 70
3.3.6 Event Initiation.............................................................................................................. 71
3.3.7 Session Activities .......................................................................................................... 71
3.3.8 Post-session Activities .................................................................................................. 72
3.3.9 DTS Performance and Sizing ........................................................................................ 72
3.3.10 DTS Database and Displays .......................................................................................... 72
CHAPTER –4: USER INTERFACE REQUIREMENTS .................................................................... 73
4.0 General Requirements ........................................................................................................... 73
4.1 System Users......................................................................................................................... 73
4.2 Function and Data Access Security....................................................................................... 73
4.3 Windows Environment ......................................................................................................... 74
4.4 Display interactions............................................................................................................... 75
4.4.1 Display Requests ........................................................................................................... 75
4.4.2 Display navigation ........................................................................................................ 75
4.4.3 Permanent Indicators..................................................................................................... 76
4.4.4 Default Screen Layout .................................................................................................. 77
4.4.5 Display Note pad........................................................................................................... 77
4.4.6 Quality Code and Tag Indication .................................................................................. 77
4.5 User Interaction Techniques ................................................................................................. 77
4.5.1 User Guidance ............................................................................................................... 78
Page iii
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
4.5.2 User Help ...................................................................................................................... 78
4.5.3 Overlapping user access ................................................................................................ 78
4.5.4 Function Key Usage ...................................................................................................... 79
4.6 Trend ..................................................................................................................................... 79
4.6.1 Graphical Trend ............................................................................................................ 79
4.6.2 Tabular Trending........................................................................................................... 80
4.7 Alarms ................................................................................................................................... 80
4.7.1 Alarm Categories .......................................................................................................... 81
4.7.2 Alarm Priority levels ..................................................................................................... 81
4.7.3 User Interaction for Alarms .......................................................................................... 81
4.7.4 Alarm Inhibit/Enable..................................................................................................... 81
4.7.5 Alarm Acknowledgment ............................................................................................... 81
4.7.5.1 Audible alarm silencing ................................................................................................ 82
4.7.5.2 Change Alarm Limits .................................................................................................... 82
4.7.5.3 Alarm Presentation........................................................................................................ 82
4.8 Events.................................................................................................................................... 82
4.9 Hardcopy Printout ................................................................................................................. 82
4.10 Report Generation ................................................................................................................. 83
4.11 System Configuration Monitoring and Control .................................................................... 83
4.12 Dynamic Data Presentation................................................................................................... 83
4.13 Element Highlighting ............................................................................................................ 84
4.14 Display Types ....................................................................................................................... 84
4.14.1 Dashboard ......................................................................................................................... 84
4.14.2 SCADA/DMS System Display ......................................................................................... 84
4.14.3 Distribution System Network Display .............................................................................. 84
4.14.4 Interchange Display .......................................................................................................... 85
4.14.5 Substation SLD displays Menu ......................................................................................... 85
4.14.6 Substation SLD Displays .................................................................................................. 85
4.14.7 Control panel displays ....................................................................................................... 85
4.14.8 Tabular Displays ............................................................................................................... 85
4.14.9 Alarm Summary Displays ................................................................................................. 85
4.14.10 Event Summary Displays .............................................................................................. 85
4.14.11 Operating Information Summaries ................................................................................ 86
4.14.12 Manual Override Summary ........................................................................................... 86
4.14.13 Off-Normal Summary ................................................................................................... 86
4.14.14 Out-of-Scan Summary .................................................................................................. 86
4.14.15 Alarm Inhibit Summary ................................................................................................ 86
4.14.16 Tag Summary ................................................................................................................ 86
4.14.17 Graphical Trending Summary Displays ........................................................................ 86
Page iv
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
4.14.18 Tabular trending summary display ……………………………………………………86
Page v
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
5.9 System Generation and Build ............................................................................................. 106
5.10 Software Utilities ................................................................................................................ 106
5.10.1 File Management Utility ................................................................................................. 106
5.10.2 Auxiliary Memory Backup Utility .................................................................................. 106
5.10.3 Failure Analysis Utility ................................................................................................... 106
5.10.4 Diagnostic Utility ............................................................................................................ 107
5.10.5 System utilization Monitoring Utility ............................................................................. 107
5.10.6 Other Utility Services...................................................................................................... 107
CHAPTER -6: HARDWARE REQUIREMENTS FOR SCADA/DMS ............................................ 108
6.0 Introduction ......................................................................................................................... 108
6.1 General Requirements for Hardware .................................................................................. 108
Page vi
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
7.9 Software Errors ................................................................................................................... 125
7.10 Server Redundancy and Configuration Management ......................................................... 125
7.11 Server Startup...................................................................................................................... 126
7.12 Peripheral Device Redundancy and Configuration Management ....................................... 127
7.13 System Configuration Monitoring and Control .................................................................. 127
CHAPTER 8: TESTING & DOCUMENTATION............................................................................. 128
8.0 General ................................................................................................................................ 128
8.1 Type testing......................................................................................................................... 128
8.2 Ad-doc testing ……………………………………………………………………………. 128
8.3 Factory Acceptance Tests (FAT) ........................................................................................ 128
8.3.1 Hardware Integration Test .............................................................................................. 128
8.3.2 System Build test ............................................................................................................ 128
Page vii
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
9.9.4 Dummy breaker latching relay ........................................................................................ 141
9.10 Contact Multiplying Relays (CMRs) .................................................................................. 141
9.11 Time facility ........................................................................................................................ 142
9.12 Diagnostic Software ............................................................................................................ 142
9.13 SCADA language based on IEC61131-3 ............................................................................ 142
9.14 Input DC Power Supply ...................................................................................................... 142
9.15 Environmental Requirements .............................................................................................. 142
9.16 RTU Size and Expandability............................................................................................... 142
9.17 RTU Panels ......................................................................................................................... 143
9.18 Wiring/Cabling requirements .............................................................................................. 143
9.19 Terminal Blocks (TBs)........................................................................................................ 144
9.20 RTU Architecture................................................................................................................ 144
Page viii
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
11.1 Multi-Function Transducers (MFTs) .................................................................................. 154
11.2 DC Transducer .................................................................................................................... 154
11.3 Transformer Tap Position Transducer................................................................................. 155
11.4 Modems............................................................................................................................... 155
11.5 WAN router ........................................................................................................................ 157
SECTION 3, CHAPTER –12 ............................................................................................................. 158
TEST EQUIPMENTS FOR RTU/FRTU ............................................................................................ 158
12.0 RTU/FRTU Configuration and Maintenance Tool ............................................................. 158
12.1 RTU/FRTU Data base configuration & Maintenance software tool ................................... 158
12.2 Master station-cum-RTU/FRTU simulator & protocol analyzer software tool .................. 158
12.3 Laptop PC for above software tools along with interfacing hardware ............................... 158
CHAPTER –13: TESTING, TRAINING & DOCUMENTATION ................................................... 159
Page ix
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
14.2.2 Equipment/Panel Earthing & Surge Protection............................................................... 171
14.2.3 Cabling Requirements ..................................................................................................... 171
14.2.3.1 Power Cables .............................................................................................................. 171
14.2.3.2 Cable Identification ..................................................................................................... 171
14.2.3.3 Cable and Hardware Installation ................................................................................. 172
14.2.3.4 Enclosures/Panels design ............................................................................................ 172
14.2.3.5 Enclosure/Panel Earthing ............................................................................................ 172
14.3 DC POWER SUPPLY SYSTEM........................................................................................ 173
14.3.1 General Technical Requirements for SMPS based DC power supply units ................... 173
14.3.2 Operational/Component Requirements ........................................................................... 174
14.3.3 Wiring ............................................................................................................................. 174
14.3.4 Bus Bars .......................................................................................................................... 174
Page x
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
14.3.31 Type Testing of DCPS ................................................................................................ 181
14.3.32 Factory/Site Testing of DCPS ..................................................................................... 182
14.4 BATTERY REQUIREMENTS .......................................................................................... 183
14.4.1 Constructional Requirements .......................................................................................... 184
14.4.2 Containers ....................................................................................................................... 184
14.4.3 Cell Covers...................................................................................................................... 184
14.4.4 Separators ........................................................................................................................ 184
14.4.5 Pressure Regulation Valve .............................................................................................. 184
14.4.6 Terminal Posts ................................................................................................................ 184
14.4.7 Connectors, Nuts & Bolts, Heat Shrinkable Sleeves ...................................................... 185
14.4.8 Flame Arrestors ............................................................................................................... 185
14.4.9 Battery Bank Stand ......................................................................................................... 185
Page xi
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
15.1.9 Interconnecting Cables, Wiring, Connectors, and Terminal Blocks ............................... 194
15.1.9.1 Metallic Cables ........................................................................................................... 194
15.1.9.2 Connectors .................................................................................................................. 195
15.1.9.3 RMU-FRTU Connectors ............................................................................................. 195
15.1.10 5.6 RMU Characteristics ............................................................................................. 195
15.1.11 General Requirements ................................................................................................. 195
15.1.12 Parameter Requirements ............................................................................................. 196
15.1.13 Design Details ............................................................................................................. 197
15.1.14 Earthing ....................................................................................................................... 198
15.1.15 Incomer Load Break Switches .................................................................................... 198
15.1.16 Circuit Breakers .......................................................................................................... 198
15.1.17 Cable Termination....................................................................................................... 199
Page xii
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
15.2.2 Applicable Standard ........................................................................................................ 208
15.2.3 Definitions and Abbreviations ........................................................................................ 208
15.2.4 Requirements .................................................................................................................. 210
15.2.4.1 General ........................................................................................................................ 210
15.2.4.2 Environmental Conditions .......................................................................................... 210
15.2.4.3 Testing......................................................................................................................... 211
15.2.4.4 Mounting Features of Autorecloser ............................................................................ 211
15.2.4.5 Bushings ...................................................................................................................... 211
15.2.4.6 Finish........................................................................................................................... 211
15.2.4.7 Control Equipment ...................................................................................................... 211
15.2.5 Auto recloser Operation parameters................................................................................ 214
15.2.6 Auto Recloser Statistical Measurement Functions ......................................................... 214
Page xiii
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
15.3.13 Communication ........................................................................................................... 227
15.3.14 Power Supplies............................................................................................................ 227
15.3.15 Maintenance and Commissioning ............................................................................... 228
15.3.16 Rating Plate ................................................................................................................. 228
15.3.17 Additional Information ............................................................................................... 229
15.3.18 Test.............................................................................................................................. 230
15.3.19 Packing/Documentation .............................................................................................. 230
15.3.20 Auxiliary Supply to the Controller Unit of Auto Recloser and Sectionliser ............... 231
15.3.20.1 STD: IS 3156-1992: voltage transformers .................................................................. 231
15.3.21 Fault passage indicators .............................................................................................. 231
15.3.21.1 Environmental specifications ...................................................................................... 231
15.4 Fault Passage Indicator (Communicable with FRTU/ Direct to Control Centre ) .............. 232
Page xiv
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
15.6.4 Workmanship: ................................................................................................................. 242
15.6.5 Drawing and Literatures ETC ......................................................................................... 242
15.6.6 Overall Dimensions......................................................................................................... 242
15.6.7 Tests & test certificates ................................................................................................... 242
15.6.8 Guarantee ........................................................................................................................ 242
15.6.9 Training ........................................................................................................................... 242
15.6.10 RMUs: ......................................................................................................................... 243
15.6.11 Auto Reclosers ............................................................................................................ 243
15.6.12 Sectionalizer ................................................................................................................ 243
15.6.13 Fault passage indicators .............................................................................................. 243
CHAPTER 16: SUPPORT SERVICES AND TRAINING ................................................................ 246
16.0 General ................................................................................................................................ 246
Page xv
GST Power Finance Corporation
SCADA/DMS, System under RDSS - Govt. of India
Model Technical specification
17.7.2 Payment of maintenance charges (based on SCADA-DMS -OMS System availability )260
17.8 The Contractor’s Obligations .............................................................................................. 264
17.9 Responsibilities of Utility ................................................................................................... 264
17.10 Responsibility Matrix ...................................................................................................... 264
CHAPTER 18: PROJECT MANAGEMENT, QUALITY ASSURANCE AND DOCUMENTATION
............................................................................................................................................................ 267
18.0 Project Management ........................................................................................................... 267
18.1 Project Schedule.................................................................................................................. 267
18.2 Progress Report ................................................................................................................... 267
18.3 Transmittals......................................................................................................................... 267
18.4 Quality Assurance & Testing .............................................................................................. 268
18.4.1 Quality Assurance and Quality Control Program............................................................ 268
18.4.2 Inspection ........................................................................................................................ 269
18.4.3 Inspection and Test ......................................................................................................... 270
18.4.3.1 Test Plans & Procedures ............................................................................................. 271
18.4.3.2 Test Records................................................................................................................ 271
18.4.3.3 Reporting of variances ................................................................................................ 271
18.4.3.4 Factory Test ................................................................................................................ 271
18.4.3.5 Field Performance Test ............................................................................................... 272
18.5 Type Testing ....................................................................................................................... 272
18.6 Documentation .................................................................................................................... 272
Page xvi
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 1 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 2 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
The scheme would be optional to DISCOMs and will be implemented in urban and rural areas
of all States/UTs except private DISCOMs.
1.2.4 Eligible Works and Activities under Part B -
Part B encompasses work related to Training, Capacity Building and other Enabling
& Supporting Activities
1.3 SCADA /DMS system
The objective of reducing Aggregate Technical and Commercial (AT&C) losses in the project
area can be achieved by plugging pilferage points & reliability by improvement in supply of
quality power, faster identification of faults & early restoration of power, proper metering,
strategic placement of capacitor banks & switches, proper planning and design of distribution
network. Bidder /Contractor responsible to implementation of the system shall be SIA
(SCADA Implementation Agency)
1.3.1 Groups of SCADA system eligibility criteria’s & components
1.3.1.1 Group-A: SCADA /DMS system in towns
1.3.1.1.1 Eligibility
The real time monitoring & control of the distribution system through state-of-the art
SCADA/DMS system encompassing all distribution Sub-stations & secondary network
emanating from S/S shall be implemented to achieve objective of this scheme. SCADA/DMS
system for Towns with following criteria shall be eligible
Non special category states
Town population > = 2.75 Lacs (as per 2011 Census data) in non-special category
states and Capital /Discom/PD HQ towns
Special category states
Town population > =1 Lacs (as per 2011 Census data) in special category states
and Capital /Discom HQ towns
Further, works in existing SCADA /DMS towns due to outgrowth /suburb and differential
area/electrical network (newly added S/S, Feeders) or functions such as OMS, FPI , additional
RTU/ FRTU w.r.t RAPDRP or legacy SCADA/RT-DAS (For new locations or locations
where faulty equipment or equipment with end of life ) may be considered as up-gradation of
the system as Group U towns.
Further, where RTDAS under IPDS is commissioned, the existing FRTU shall act as Sub RTU
to new RTU and report all Input points captured to new RTU and I/O card for differential
points may only be considered in configuration of new RTU in order maximize usage of
infrastructure created under RT-DAS.
In case of numerical relays, RTU at substations to act as gateway , data concentrator for
numerical relays/ BCPUs connected over IEC 61850 and I/O Cards in RTUs to be configured
accordingly i.e. for bays where requisite I/Os are not served through numerical relays/ BCPUs.
1.3.1.1.2 Components of Group- A towns
Major components that a SCADA /DMS implementation would include are given as under.
However, the final scope of work will be finalized by the utilities as per their requirements in
Page 3 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
the relevant RFP document. Survey, Supply, Design, Engineering, Installation, Testing,
Commissioning, Go-Live & service based (SLA) for utility for:
a. SCADA/DMS Control Centre (SDCC) at each Group-A town
b. Common Disaster Recovery Centre for SCADA/DMS for group-A towns per utility or
town as per requirement and availability of infrastructure (Building etc.) by utility
(CDRC)
c. SCADA & Information Storage & Retrieval (ISR) Functions
d. Load Shed application (LSA)
e. Outage data analytics and reporting (ODAR)
f. DMS Functions
i. Network Connectivity Analysis (NCA)
ii. State Estimator (SE)
iii. Load Flow (LF)
iv. Voltage VAR Control (VVC)
v. Fault Management and System Restoration (FMSR)
vi. Feeder Reconfiguration, Loss Minimization, Load Balancing, LMFR,LBFR)
vii. Operation Monitor (OM)
g. OMS Functions
i. Trouble call & Outage Management System (TCOMS)
ii. Crew assignment & Work Order Management (CAWOM)
iii. Mobile APP, Web client for Crew (MAWC)
Page 4 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
FIG - SCADA DMS CONTROL CENTRE (SDCC) FOR EACH SCADA/DMS TOWN (GROUP A)
1.3.1.2 Group-B : SCADA system in towns
1.3.1.2.1 Eligibility
The real time monitoring & control of the distribution system through state-of-the art SCADA
system encompassing all distribution Sub-stations & FPIs at secondary network emanating
Page 5 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
from S/S shall be implemented to achieve objective of this scheme. SCADA system for Towns
with following criteria shall be eligible
SCADA in towns based on Common district-wise or Circle-wise or Zone wise common
control centers in all other statutory towns (2011 census) with population 25000 or more.
1.3.1.2.2 Components of Group- B towns
Major components that a SCADA implementation would include are given as under.
However, the final scope of work will be finalized by the utilities as per their requirements in
the relevant RFP document. Survey, Supply, Design, Engineering, Installation, Testing,
Commissioning, Go-Live & service based (SLA) utility for:
Common District/ Circle /Zone - wise, Standard SCADA Control Centre (SSCC) for
all eligible in the district. (A district control center can be clubbed in to Zonal SCADA
control centers (ZSCC) adjoining districts if present count of aggregated O/G Feeders
is up to 400 feeders. This includes monitoring of Substations of Group C also). Further,
for Ladakh, Manipur, Mizoram, Nagaland, Meghalaya, Sikkim, Arunachal Pradesh,
Tripura, Andaman, Puducherry, DNH&DD, Goa, Lakshadweep etc. may have
common ZSCC in each state for all towns for SCADA besides SDCC for capital town.
This is a guideline to create appropriate architecture. However, utilities of other states
can decide to club / co-locate ZSCC with SDCC as per the ease in monitoring /control
of electrical network / optimize control centers requirements based on availability of
building infra for control centers as per sanction
Common Data Recovery Centre for SCADA for group-B towns per utility
SCADA & Information Storage & Retrieval (ISR) Functions
Network Connectivity Analysis (NCA)
State Estimator (SE)
Load Flow (LF)
Load Shed Application(LSA)
Outage data analytics and reporting (ODAR)
SCADA Dispatcher training simulator (DTS) per Control center
SCADA system to supervise& control primary S/S & monitor FPIs at secondary HV
Distribution network
RTUs at all primary S/S &, FPI communicable on secondary HV Distribution network
etc. MFTs at Feeders
Fault passage Indicators (Communicable/ Non Communicable ) for fault reporting
Secured Communication using VPN/SSL
MPLS network for connecting all S/S RTUs to Main & DR center
Secured GPRS/MPLS-4G/DLC etc. for communicating of FPIs with control centers
Protocols for communication
IEC 60870-5-104 –RTU, IEC 60870-5-104/101 for FRTUs, FPI to control
centers.
MODBUS or IEC 60870-5-101/104 – MFTs to RTUs
Page 6 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
ICCP (TASE.2) between SCADA/DMS Control center /DR center & state load
dispatch center(optional)
Support /compliance to IEC61850 ,IEC60870-5 suite for RTU/CC for
numerical relays
FIG – STANDARD SCADA CONTROL CENTRE (SSCC) FOR DISTT OR ZONAL SCADA
CONTROL CENTRE (ZSCC EACH SCADA AND RT-DAS TOWNS (GROUP B &C)
Ref. Fig 1.2
Support /compliance to DLMS/ IEC 62056 for SMART meters
Cyber security compliance from CERT.IN empanelled agencies and any other
notified MoP/Nodal agency /CEA from time to time.
Machine to Machine requisite data transfer of reliability to National Power Portal
or any other portal as directed by MoP /PFC / CEA in the desired format such as
JSON Object, XML, and CSV etc.
Conducting Factory Acceptance Test (FAT), Site Acceptance Test (SAT), Type test
(as required), etc. successfully, Go live, operational acceptance & handing over to
customer.
Service based (SLA ) support during FMS for utility post Operational acceptance
(S.A.T)
Further , where RTDAS under IPDS is commissioned , existing FRTU shall act as
Page 7 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Sub RTU to new RTU and report all Input points captured to new RTU and I/O
card for differential points may only be considered in configuration of new RTU in
order maximize usage of infrastructure created under RT-DAS
In case of numerical relays, RTU at substations to act as gateway , data concentrator
for numerical relays/ BCPUs connected over IEC 61850 and I/O Cards in RTUs
to be configured accordingly i.e. for bays where requisite I/Os are not served
through numerical relays/ BCPUs
1.3.1.3 Group-C : RT-DAS system in towns
1.3.1.3.1 Eligibility
The real time monitoring of the distribution system through state-of-the a RT-DAS system
encompassing all distribution Sub-stations & FPIs at secondary network emanating from S/S
shall be implemented to achieve objective of this scheme. SCADA system for Towns with
following criteria shall be eligible
RT-DAS in towns based on Common district-wise or Circle-wise or Zone wise common
control centers of Group B in all other statutory towns (2011 census) with population less
than 25000. However, based on the requirement, utility may opt basic SCADA
1.3.1.3.2 Components of Group- C towns
Major components that a RT-DAS implementation would include are given as under.
However, the final scope of work will be finalized by the utilities as per their requirements in
the relevant RFP document. Survey, Supply, Design, Engineering, Installation, Testing,
Commissioning, Go-Live & service based (SLA) for utility for:
Common District/ Circle /Zone - wise, Standard SCADA Control Centre (SSCC)
for all eligible in the district. (A district control center can be clubbed Zonal
SCADA control centers (ZSCC) adjoining districts if present count of aggregated
O/G Feeders is up to 400 feeders. This includes monitoring of Substations of Group
C also. Further, for Ladakh, Manipur, Mizoram, Nagaland, Meghalaya, Sikkim,
Arunachal Pradesh, Tripura, Andaman, Puducherry, DNH&DD, Goa,
Lakshadweep shall have common ZSCC in each state for all towns for SCADA
besides SDCC for capital town.
Real time Data Acquisition & Information Storage & Retrieval (ISR) Functions
Network Connectivity Analysis (NCA)
State Estimator (SE)
Load Flow (LF)
Outage data analytics and reporting (ODAR)
RT-DAS system to supervise primary S/S & monitor FPIs at secondary HV
Distribution network
RTUs at all primary S/S &, FPI communicable on secondary HV Distribution
network etc. MFTs at Feeders
Fault passage Indicators (Communicable/ Non Communicable ) for fault reporting
Secured Communication using VPN/SSL
MPLS network for connecting all S/S RTUs to Main & DR center.
Page 8 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 9 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Service based (SLA ) support during FMS for utility post Operational acceptance
(S.A.T)
1.3.2 Make in India
Keeping in view the aims and objectives of Atma Nirbhar Bharat Abhiyan, Ministry of Power
has issued Public Procurement (Preference to Make in India) for Purchase Preference (linked
with local content) Order in respect of Power Sector on 28.7.2020. This order is in line with the
DPIIT Notification No.P-45021/2/2017-PP (BE-II) dated 4th June, 2020. This order along-with
amendments, if any, from time to time, shall be followed by the DISCOMs and bidder in the
implementation of the scheme.
1.3.3 Broad Role Definition for SIA
The SIA in coordination with utility (as per the requirement to be given in the detailed RFP and
group A , B , C, U towns ) shall carry out field survey, design ,engineering, supply, installation,
testing & commissioning of SCADA/DMS software applications, Dispatcher Training
Simulator (DTS) , hardware (including PCs, Servers, Routers, Switches, VPS, RTU, FRTUs,
Multi-function Transducers (MFTs), Communication equipment , Auxiliary power supply
etc.), software (including operating system, databases, network management system etc.),
network (LAN,WAN), RMUs, Sectionalizers, A/R , FPIs etc.
Integration with existing /under implementation IT system under IPDS & any other relevant
SCADA/ DMS or RT-DAS legacy/ Numerical relay in the identified project areas of the utility
in the RFP
Data of outage /SAIDI/SAIFI to be transported in machine to machine mode to National Power
portal or any other GoI portal as notified in future.
Integration with State Load Dispatch center (SLDC) for the state for exchanging relevant real
time data & scheduling data over ICCP if opted by utility. In case utility includes data exchange
facility with SLDC, then it is their responsibility to do necessary bilateral agreement for data
exchange with TRANSCO or owner of SLDC. & facilitate necessary help to SIA
Facilities management services for maintaining infrastructure as per SLA , post successful
completion of acceptance tests for a period of seven years from the date of completion of
acceptance test.
The key components of the model RFP includes & not limited to following:
1) Hardware: site survey, planning, assembly/ manufacturing, design & Engineering,
Supply, loading, transportation, unloading, insurance, delivery at site, handling,
storage, installation, testing, commissioning and documentation of all necessary
hardware and networking equipment and its connectivity, as specified in the detailed
specifications. The SIA shall take the responsibility to install the servers, RTU/FRTU,
MFTs, Video Projection System (VPS) switches, routers, backup and tape devices,
Workstation PCs, Aux Power supply, communication equipment, RMUs,
Sectionalizers, A/R, FPIs etc. and other necessary hardware/software at the sites. The
SIA shall provide the time frame for procuring and delivering all the necessary
hardware. Though the scope covers establishment of a SCADA/DMS control center
along with associated hardware and software, the SIA shall design and provide the
Software & hardware at SCADA/DMS control center including RTU/FRTU locations
with 100% expandability for future growth in electrical distribution network of the city.
The delivered hardware ( Processor ,HDD, RAM &software etc.) for servers, PCs ,RTU,
FRTU etc. shall be sized for ultimate system sizing while maintaining the performance,
availability & functions as per specification.. However, other items such as I/O modules,
Page 10 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
additional workstation can be added as per the growth in the network The SIA shall
provide the necessary design & engineering documents, drawings and plan, sizing,
cabling and connectivity and the bill of material, etc. & obtain approval from utility
2) Software: Site survey, planning, assembly/ manufacturing, design & Engineering,
Supply, loading, transportation, unloading, insurance, delivery at site, handling,
storage, installation, testing, commissioning and documentation of operating systems at
servers/desktops, database and SCADA/DMS,OMS, RTDAS application software, etc.
3) Facilities management services (FMS) for maintaining infrastructure, activities for
creation/ modification /deletion of database / display, reports , GIS data maintenance
and activities related to additional RTU/FRTU/ and enablers etc. procured by utility
to cater growth of electrical distribution network . During the FMS period any creation
modification/addition/deletion of database incl. GIS , RTU/FRTU/displays/ reports,
limits setting etc. shall be ensured in line with change/ growth of electrical network in
form of new RTU/FRTU/ RMU/Sectionalizers/ FPIs , numerical replays etc. provided
by utility. The activities shall be ensured for atleast post successful completion of
acceptance tests for a period of seven years from the date of completion of operational
acceptance of the SCADA/DMS System. However, under RDSS scheme, utilities will
be funded & awarded for FMS for two years from the date of Go-Live / S.A.T only but
bids will be evaluated considering 5 years of FMS
The Contractor shall be required to provide the services under FMS so as to manage
entire system including all equipment, installations including hardware, software &
networks installed & commissioned by Contractor for the utility in order that they meet
the availability requirement as specified in the document.
The System Management Services shall be provided by SIA as FMS Contractor inorder
that maximum uptime & performance levels of systems installed are ensured. As such,
FMS Contractor is expected to provide services as per ITIL (IT Infrastructure Library)
standards with performance levels meeting or exceeding those mentioned in Service
Level Agreement (SLA) agreed between utility & Contractor.
To achieve the desired Service Levels, the Contractor may need to interact, coordinate
and collaborate with the other Service Providers as required. The Contractor will act
as the Single Point of Contact for all issues relating to the Service Levels. The
Contractor will have the responsibility to deal with the other vendors (during warranty
period) /other vendors as selected by utility (after warranty period) as the case maybe, to
provide the services at agreed service levels. However, the prime responsibility of
providing desired services shall be that of lead Contractor during warranty period. The
role of SIA as FMS Contractor (shall start immediately after systems are installed,
commissioned and handed over to the owner after Operational acceptance (S.A.T) of
the System.
The Scope of Work shall include the software and hardware maintenance support to be
provided by the Contractor in respect of the system supplied including interim audit
in case of major change and regular annual Cyber security audit by CERT.IN
empaneled agency or any agencies notified by MoP/GoI /Nodal agency under this
project during 5 year Facility Management Services (FMS) period along with
Supervision & Operationalizing 5 year warranty of the SCADA,DMS,OMS, RTDAS
System and communication network after the Operational Acceptance of the same.
Page 11 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
4) System Design and Engineering: The SIA shall be responsible for detailed design and
engineering of overall system, sub-systems, elements, system facilities, equipment,
services, including systems application software and hardware etc. It shall include
proper definition and execution of all interfaces with systems, equipment, material and
services of utility for proper and correct design, performance and operation of the
project.
SIA shall provide complete engineering data, drawings, reports, manuals and services
offered etc. i.e. complete set of documentation /drawings for Utilities review, approval
and records
5) Supply of Equipment and Material: The SIA shall also be responsible for
manufacture, inspection at manufacturer’s works, supply, transportation, insurance,
delivery at site, unloading, storage, complete supervision, installation and successful
commissioning of all the equipment, systems and application software. The proposed
deliverables should be state of the art in architecture and engineering practices In case
of third party products/software packages, SIA should furnish at least 5 years warranty
along with supporting plan from respective OEMs to support FMS time line
Any item though not specifically mentioned, but is required to complete the project
works in all respects for its safe, reliable, efficient and trouble free operation & to meet
performance ,availability & functional requirements as envisaged in the RFP shall also
be taken to be included, and the same shall be supplied and installed by the SIA without
any extra cost
6) Testing and Commissioning: The SIA shall be responsible for the testing processes
such as planning (includes preparing test plans and defining roles and their
responsibilities), preparation (consists of preparing test specification, test environment
and test data) for all tests viz. Type tests, FAT, SAT and successful commissioning.
During the FMS period any modification/addition/deletion of database/displays/
reports etc. shall be ensured in line with growth of electrical network in form of new
like RTU/FRTU/ RMU/Sectionalizers / FPIs provided by utility. SIA shall also be
responsible for successful conduction of cyber security audit by CERT.IN empaneled
agency.
7) Geographical Scope: The Locations where the systems shall be implemented shall be
detailed by the particular utility in the RFP
8) Integration Scope: SIA should ensure that legacy systems and the new solutions lined
up by them are tightly integrated and do not remain stand-alone and shall perform on
real time basis as envisaged in specifications. All required external systems shall be
integrated using an integration middleware layer. The scope of integration of external
systems includes, legacy SCADA/DMS system, RTU/FRTU, IT systems, Numerical
relays etc. including billing , customer care , GIS etc. already existing and functional
in the utility, but outside the present scope of work and defined in RFP by utility . The
integration is expected to be Industry Standards Based on IEC 61968-1 Bus (SOA
Enabled on enterprise Bus) using CIM/XML, OPC, ICCP etc., which is, on-line, real
time or offline where appropriate and shall operate in an automated fashion without
manual intervention, which is documented for future maintenance.
SIA shall make necessary provisions/software linkages in the proposed solution so that
the IT system or any legacy SCADA/DMS system as specified in the RFP may be
integrated seamlessly.
9) Training for Employees: The SIA shall organize training to the core Group of
Page 12 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
implementation team of the utility as well as end user training. Representatives from
the successful bidder, Purchaser’s implementation project and change management
teams will be involved throughout in the development of training strategy, training
material design and development, standards and training delivery to ensure that change
management issues are incorporated, and that training strategies and materials are
aligned to the requirements of the project and as business-specific as possible
10) Assist Utility and PMA for responding to queries to Nodal Agency: SIA may be
responsible for preparing responses to the queries raised by the Nodal Agency.
Adequate support will be provided by the utilities to the SIA
11) Progress Update: The SIA may also provide periodic status update reports
highlighting critical issues to the utility. Further, any information (progress report, etc.)
as and when sought by the Nodal Agency/Ministry of Power shall be furnished by the
SIA.
12) In addition to the above, following works are also in the scope of the contractor:
(a) Database, Reports and display development
(b) Training
(c) Obtaining the statutory clearances required, if any from Ministry of
Communication/ Govt Authority. All the charges deposited to aforesaid authority
for obtaining statutory clearance will be reimbursed by the owner. The owner will
also provide the necessary support if required in getting the clearances
d) Hired /leased communication network & arrange SLA with service provider in line
with SLA of FMS period. Once SIA is appointed, a tripartite agreement among
Utility, service provider & SIA shall be signed.
e) Sufficient SPARES /INVENTORY for FMS period of 5 years to meet SLA
13) Other Services and Items: The scope also includes, but not limited to the following
services/items described herein and elsewhere in specification:
a. Project Management and Site Supervision: The bidder shall be responsible
for the overall management and supervision of works, including the
implementation of risk management as well as change management initiatives.
He shall provide experienced, skilled, knowledgeable and competent personnel
for all phases of the project, so as to provide the utility with a high quality system
b. Interface Coordination: The bidder shall identify all interface issues with utility
and other agencies if any, and inform utility which shall interface, coordinate and
exchange of all necessary information among all concerned agencies.
c. Scope Change Management: Utility to finalize the scope change management
procedure during development/Implementation stage
Page 13 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 14 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Similarly for Group A Towns of SCADA/DMS, bidding can be done in multiple packages
(Maximum 5 towns of Group A). Also, for Group U Towns of SCADA/DMS, bidding can be
done in multiple packages (Maximum 5 towns of Group U). The package mentioned here is
indicative for optimal configuration for packaging and utility may reconfigure as per the need
of the project
1.3.6 Facilities to be provided by Employer/Owner (Utility)
a. Arranging necessary shutdowns and work permits at various sites.
b. Formation of team for SCADA works at control center and field level both.
c. Timely approval of documents, tests etc.to ensures completion of project in time.
d. Timely release of payment to contractor on achievement of milestones/compliances
e. Reconductoring of line for switching of loads in case of RMU connected networks
f. Retrofittment of breaker for SCADA ready
g. Any other communication infra like Fiber/ radio optic etc. other than MPLS ,GPRS/MPLS-4G
h. Providing all the necessary data regarding the power distribution system network.
i. Providing storage space at site free of cost wherever available. Special storage needs
such as watch and ward services and air conditioning shall be provided by the
contractor.
j. The existing earthing system at the substations may be utilized for earthing of the
offered equipment. However, it is essential that the contractor shall assess its suitability
for the offered equipment and carry out the modifications if required. It is recommended
to provide separate electronic earthing for SCADA equipments by contractor.
k. Suitable space/Infrastructure incl. civil works, electrical raw supply , Air-conditioning
, firefighting , building security , lighting , furniture etc. for Control center/DR,
Substations for installation of control center/ DR equipments, RTUs /FRTUs/APS etc.in
line with SCADA/DMS system implementation schedule.
l. Providing details of Existing Legacy systems if any SCADA/DMS/ RTDAS,
RTU/FRTU, IT, Numerical relays RMU/FPI, GIS etc. system under R-APDRP for
integration.
m. Utility shall ensure that Project implementation & operation to be done by O&M dept.
of utility where IT dept. /cadre shall work as support. This is mandatory
1.3.7 General Requirements
The Bidder's proposal shall address all functional, availability and performance requirements
within this specification and shall include sufficient information and supporting
documentation in order to determine compliance with this specification without further
necessity for enquiries
An analysis of the functional , availability and performance requirements of this specification
and/or site surveys, design, and engineering may lead the Contractor to conclude that additional
items and services are required that are not specifically mentioned in this specification. The
Contractor shall be responsible for providing at no added cost to the employer all such
additional items and services such that a viable and fully functional system is implemented
that meets or exceeds the capacity, and performance requirements specified. Such materials
and services shall be considered to be within the scope of the contract. To the extent possible, the
Bidders shall identify and include all such additional items and services in their proposal.
Page 15 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
All equipment provided shall be designed to interface with existing equipment and shall
be capable of supporting all present requirements and spare capacity requirements
identified in this specification.
The offered items shall be designed to operate in varying environments including
suitability as per higher altitude requirement. Adequate measures shall be taken to provide
protection against rodents, contaminants, pollutants, water & moisture, lightning& short
circuit, vibration and electro-magnetic interference etc.
The Contractor shall demonstrate a specified level of performance of the offered items
during well-structured factory and field tests. Further, since at the substations limited
space is available the contractor shall make all the efforts to economize the space
requirement.
The Bidders are advised to visit sites (at their own expense), prior to the submission of the
proposal, and make surveys and assessments as deemed necessary for proposal submission.
The successful bidder (Contractor) is required to visit all sites. The site visits after contract
award shall include all necessary surveys to allow the contractor to perform the design
and implementation functions.
After the site/route survey the Contractor shall submit a survey report for all the sites. This
report shall include at least the following items; however, the exact format of the report
shall be finalized by the contractor with the approval of Employer.
a. Proposed layout of Equipment in the existing rooms and buildings.
b. Proposed routing of power, earthing, signal cables and etc.
c. Confirmation of adequacy of Space and AC Power supply requirements
d. Proposals for new rooms/buildings, if required
e. Identification of facility modifications, if required
f. Identify all additional items required for interconnection with the existing equipment.
g. Requirement of Modification to existing earthing arrangement, if any.
1.3.8 General Bidding Requirements
The offered equipment/system/ solution must be in successful operation for at least one
year as on the date bid opening. However, the computer software /hardware shall be of
latest current industry technology/ standard models as per Model Technical specification
chapter 1-19 The Bidder shall beresponsive to the technical requirements as set forth in
this specification. To be considered responsive, the Bidder's proposal shall include the
following:
1. A detailed project implementation plan and schedule that is consistent with the scope
of the project. The plan shall include all the activities required, show all key milestones,
and clearly identify the nature of all information and project support to be provided for
completion of the project. Manpower resources, proposed to be deployed by the
Contractor during the execution phase, shall be clearly indicated.
2. Documentary evidence in support of the qualifying requirements specified in the
bidding document i.e. RFP shall be submitted along with the bid.
3. Performance certificate for the offered equipment/systems from the user’s in line to the
requirements mentioned in the biding documents.
Page 16 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
4. The type test certificates for the offered equipments. In case it is not type tested. The
commitment for same to be conducted during implementation
5. Completed equipment Data Requirement sheets/Questionnaire
6. Technical details of the offered equipment/systems.
7. Description of existing IT system shall be included by utility
8. SLA & Cyber security compliance plan
1.3.9 Items of Special Interest
To assist in understanding the overall requirements of the project, the following items of special
interest are listed. The Bidder shall pay particular attention to these items in preparing the
proposal.
a. The contractor shall be responsible for overall project management, system integration
and testing to complete all the facilities under the project.
b. The project shall be implemented in the time schedule described in the section- 9.
c. The database, displays and reports for SCADA/DMS/OMS/RT-DAS system are to be
developed by the contractor; however, the contractor shall associate the
employer/owner’s engineers also during the data base development. The required
hardware & software for completion of this activity may be used out of the hardware &
software to be supplied under this contract.
d. The APIs (Application Program Interfaces) specified/needed chapter 2 is to be supplied.
However the supply of source code is not mandatory. (API only for customized portion
,if any is to be provided )
e. Integration with legacy system if indicated in the RFP
1.3.10 Site Conditions
The sites are located in the towns of Group A for SCADA/DMS as per list in Chapter 19
Annexure 1. The minimum to maximum temperature & relative humidity generally falls
between … to … C. & ..... to. % respectively. The sites are located in the towns of Group B
for SCADA as per list in chapter 9 Annexure 2. Further, where RTDAS under IPDS is
commissioned, the existing FRTU shall act as Sub RTU to new RTU and report all Input points
captured to new RTU and I/O card for differential points may only be considered in
configuration of new RTU in order maximize usage of infrastructure created under RT-DAS
as per list in chapter 19 Annexure 2.
The minimum to maximum temperature & relative humidity generally falls between … to …
C. &..... to.... % respectively. The sites are located in the towns of Group C for SCADA as per
list in Annexure 3 The minimum to maximum temperature & relative humidity generally
falls between … to … C. &..... to.... % respectively. The sites are located in the towns of Group
U for SCADA /DMS as per list in Annexure 4 The minimum to maximum temperature
& relative humidity generally falls between … to … C. &..... to.... % respectively. Utility shall
also indicate locations at above 2000 m form M.S.L if any for suitable hardware. The
system/equipment shall be designed as per the environmental conditions mentioned in the
relevant section of this specification. The operating and ambient temperature specified for
hardware /equipment in respective chapters are indicative for each equipment in the
specification . Utility may change as per the climatic condition and operational requirement
with vendor neutral approach
1.3.11 Applicable Standards
The applicable standards are mentioned in the respective technical section. The offered
Page 17 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
equipment shall conform to the standards mentioned in the specification except to the extent
modified by this specification. In case of any discrepancy between the description given in the
specification and the standards the provisions of the technical specification shall be followed.
The parameters not specifically mentioned in this specification shall conform to the standard
mentioned in this specification.
Wherever, new standards and revisions are issued during the period of the contract, the
Contractor shall attempt to comply with such standards, provided there is no additional
financial implication to employer/owner.
In the event the Contractor offers to supply material and/or equipment in compliance to any
standard other than those listed herein, the Contractor shall include with their proposal, full
salient characteristics of the new standard for comparison for equivalence or better.
For Group A , SCADA/DMS/OMS and Group B , SCADA and Group C RTDAS and Group
U shall be considered irrespective of terms of SCADA , DMS, OMS, RTDAS is mentioned in
any combination in specification as per the relevant functional requirements common and
specific both that group .
1.3.12 Warranty
This would include seven years warranty for the related hardware & software supplied under
the SCADA/DMS project after the Site acceptance test (S.A.T), operational acceptance of the
SCADA/DMS System. The 5 year warranty shall include comprehensive OEM on-site warranty
for all components (H/W and Software including OS) supplied including reloading and
reconfiguration of all Software and device drivers/patches etc. if required. In case 5 Years
warranty is beyond standard warranty period of the equipment or required to cover to cover
FMS period , the extended warranty shall be the responsibility of SIA.
1.3.13 Terms for utility & SIA
The term contractor & bidder shall be referred as SCADA/DMS implementation agency (SIA)
& owner; employer shall be referred as utility where ever mentioned in the RFP /Model
Technical specification (MTS)
1.3.14 Proposed SCADA/DMS system
Utility shall write in brief about the proposed system for Group A ,B &C
Page 18 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
End of Chapter 1
Page 19 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 20 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 21 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 22 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 23 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
ii. RTU/ FRTU/ FPI status change is detected such as RTU/ FRTU/ FPI restart,
Communication Link restoration
iii. On demand by SCADA/DMS functions
iv. On request by the user
The TCP/IP Communication for RTU, FRTU,FPI on public network shall be encrypted over
SSL Security / VPN & the equipment should take control command from designated Master
IP address only and no other IP. The RTU, FRTU, FPI & all TCP/IP devices that are on Public
Network shall form a private VPN network with the SCADA Front End, through which
encrypted data gets exchanged. In case, RMU & Sectionlizer is supplied with built -in FRTU
is supplied, then also the above time skew and update requirement shall be met .
2.2.2.2 Telemetry Failure
If data is not received from an RTU/FRTU/ FPI after a user-adjustable number of retries, each
affected point in the SCADA system shall be marked with a ‘telemetry failure quality code’
and an alarm shall be generated. Telemetry failure of data can be due to failure of
communication link, failure of complete RTU/, FRTU/FPI or RTU/ FRTU module or MFT
etc. Only a single alarm shall be generated if an entire RTU/ FRTU or its communication
channel fails.
In the event of telemetry failure, the last good value/status shall be retained in the database for
each affected point. When telemetry returns to normal, the associated SCADA system shall
automatically resume updating the database with the scanned data.
The user shall be able to substitute a value in the database for any point that is experiencing
telemetry failure which shall be marked with ‘manual replaced’ quality code in addition to
the ‘telemetry failure’ quality code. The user shall also be able to delete any point (or entire
RTU/FRTU/FPI) from scan processing. All deleted points shall be marked with a ‘delete-from-
scan’ quality code.
Acquisition Modes
The following modes of data acquisition shall be supported:
a) Enable
When RTU/FRTU/FPI is enabled, the data is scanned in normal fashion and
control command execution is allowed.
b) Disable
When RTU/FRTU/FPI is disabled, the data scanning & control execution is
disabled. This is equivalent to” delete from scan “of complete RTU/FRTU/FPI
c) Test /Maintenance
Placing an RTU/ FRTU in test mode shall generate an appropriate event message. When an
RTU/FRTU is in the test mode, the real-time database shall retain the last value from all points
collected via the RTU/FRTU before it was placed in the test mode. The points shall be marked
in the database with a quality code indicating that their source RTU/FRTU is in the test mode.
All system displays, programs, data links, and other devices shall use this value. Supervisory
control of points that are in the test mode shall not be permitted.
When an RTU/FRTU is removed from the test mode, a message shall be generated, the test
mode quality code shall be removed from all points assigned to the RTU/FRTU, the database
values shall resume updating on each scan, and any controls for the RTU/FRTU shall be
Page 24 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
enabled.
2.2.3 Time synchronization of RTUs
The SCADA/DMS system will be synchronized from the GPS based Time and frequency
system. The SCADA system shall synchronize the time of all connected RTUs/FRTUs/FPI
every 15 minutes (user configurable from 5 minutes to 24 hrs.) using time synchronization
message in the IEC 870-5-104/101 protocol /NTP/SNTP. The servers /Workstations at
SCADA/DMS control center shall be synchronized using NTP/SNTP. The time of DR center
shall also be synchronized from the GPS based system installed in one of the associated
SCADA/DMS control center or SCADA centre in the DISCOM
2.2.4 Data Exchange
Utility shall specify the external systems, if any with which data exchange of SCADA system
is envisaged and shall specify interface and interoperability parameters in the RFP. Utility
shall also provide the required access & information of such existing systems to SIA for
implementation
2.2.4.1 National Power Portal (NPP) & National Feeder Monitoring System (NFMS)
Machine to Machine data transfer to existing National Power Portal (NPP) & National Feeder
Monitoring System (NFMS envisaged under PART A of the scheme separately. The data
transfer shall be done in JSON object or any other format as finalized required, by creating
suitable APIs at SCADA control Centre. The data primarily will be feeder wise SAIFI/SAIFI
values on daily basis. Further, it shall be possible to transfer other telemetered data of interest
of feeder also. The data & exchange format will be decided during design & Engineering
phase.
Further, the real time SCADA/DMS status /reports in view only mode for capacity building
may be required to be linked with any common infra directed by MoP/ PFC
2.2.4.2 SCADA/DMS system with IT system (optional)
If data exchange requirement of specific parameters with IT system is envisaged by utility in
the RFP then, SCADA/DMS System shall exchange data with ISR System & ISR System shall
be the nodal interface with all IT System. The Data Center, DR Center and Customer Care
Center under IT System, shall exchange data with the ISR System, using Open Standards like
CIM/XML & IEC 61968 Series Standards for Power System, OPC, ICCP/TASE.2., ODBC
The GIS System shall exchange data with SCADA System over IEC 61968-1 SOA based
ESB/Bus using CIM/XML Models for Power System using GIS Engine / Adapters supporting
the standard.
Direct SQL/ODBC interfaces should continue to be supported for report generation and ad-hoc
queries.
If utility was having GIS/ billing/customer system prior to this scheme such as IPDS i.e.
considered as legacy, then interfaces may be selected accordingly viz. ODBC/DDE etc. using
ASCII files. However, they shall provide system in compliance of the data exchange
requirement specified in this para.
Data to be exchanged with IT system is defined ISR section. For DR & SLDC, it is given
below:
2.2.4.3 For data exchange between SCADA/DMS control centers & DR center,
optional (SLDC):
If opted & requirement specified by utility in this RFP, then SCADA/DMS control centers
Page 25 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
shall also exchange data using ICCP with State Load Dispatch Centre (SLDC) of the state.
Data exchange shall also allow other information to be transferred report by exception but also
configurable periodically, or on demand. It shall be possible to exchange at least the
following data:
Real-time telemetered data of the interconnected network,
Non-telemetered data of the interconnected network,
Calculated data of the interconnected network,
SOE data of the interconnected network
Historical data of the interconnected network
Scheduling data
Operator messages.
Event /alarm lists
It is envisaged that the utility shall get the load forecasting & drawl schedules from SLDC
& versa in order to execute planning of load distribution. In addition, status /measurement of
interconnected network shall be able exchanged in both directions.
For Group-A towns, Disaster recovery is replica of main control center and hence shall be
in sync on daily basis or on demand also.
Whereas for Group B&C, the data exchange with DR is required all the data to be transferred
from control center to DR which is required for system build in order to build a system from
scratch. ICCP TASE.2 protocol or equivalent nonproprietary/ De-Facto protocol shall be used
transfer network model / database changes on incremental /global basis automatically once a
day & on demand It shall transfer all data /information which are required for system build in
order to build a system from scratch.
2.2.5 Data Processing
The SCADA/DMS system shall prepare all data that they acquire for use by the power system
operations and other applications. The data processing requirements shall apply to data
collected from all specified sources.
Data acquired from RTUs/FRTUs/FPI/IT system, as well as data received from the DMS and
the existing control centers (if any and specified by utility in this RFP), shall be processed and
placed in the Real-Time Database as soon as it is received.
Data processing involves a value which has been converted to internal form and analyzed for
violations of limits. The data processing shall set various data attributes depending on the
results 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. The
SCADA system shall have capability to accept data from the following sources:
a. Real-time (also referred as telemetered) data received from control centers /IT
system (data center, customer care, DR center and RTUs/FRTU/FPI etc.)
b. Calculated data
c. Manually entered data
d. Sequence of events data
e. Alternate data sources
Page 26 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 27 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 28 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
(4) On/Off
(5) Auto/Manual
(6) Remote/Local
(7) On Control/Off Control
(8) Set/Reset
b. Three-state points: Any of the state combinations listed in (a) above shall be
supported with a third, typically, in-transit state which is the case for slow
operating devices such as isolator. If a device remains in this state for a period
more than a threshold value, the same shall be alarmed.
c. Momentary change Detection (MCD): The input to capture the states of fast
acting devices such as auto-reclosers.
Commanded changes initiated by supervisory control shall not be alarmed but shall generate
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. In the event of off normal positions,
the same shall be reflected in the off normal summary list
2.2.5.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 definable
interactively at a console as well as by the programmer using database creation and maintenance
procedures.
Calculated analog values shall use database points as the arguments and mathematical 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
operators etc. shall be provided.
It shall be possible to calculate running maximum value, minimum value and average value
over a time interval (time interval configurable from 5 minutes to 60 minutes). The value shall
be reset after the elapse of defined time interval. These values shall be stored with time of
occurrence for maxima and minima and the time for averaging.
Calculated status values shall use database points as arguments and combinational logic
functions that include the logical, comparative operators such as AND, inclusive OR, exclusive
OR, NOT, Less Than, Greater Than, Less Than or Equal To, Greater Than or Equal To, and
Equal To ,If , else if etc. Suitable rules or operators (such as multi-level parentheses) shall be
provided to indicate the sequence of operations in the calculation.
2.2.5.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 switching devices, such
as breakers and disconnectors, in order to define the configuration of the substation for display.
The energization of lines, transformers, bus sections and generating units shall be determined
so that the associated displays may correctly show the status of these power system elements.
The configuration shall be re-evaluated and updated whenever a switching device status
change & analog value change beyond dead-band is detected.
Page 29 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 30 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
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 shall be
transferable in RDBMS database tables of ISR system for generation of tabular displays and
reports.
2.2.7 Sequence-of-Events data
Sequence-of-events (SOE) data shall be chronological listings of „status change events with
time stamp‟ acquired from RTUs /FRTUs/FPIs. The SOE data shall be collected from all
RTUs/FRTU/FPI 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/FPI shall be merged for chronological listings
and stored for subsequent review. At least latest 1000 SOE data shall be available for display.
The SOE resolution of RTU/FRTU/FPI is defined in respective sections for RTU/FRTU.
SCADA/DMS system at control center shall have 1ms SOE resolution. However, a s SOE
time stamping is done at RTU/FRTU/FPI level, the same shall be in line with resolution
defined for RTU/FRTU/FPI.
All SOE data collected from all RTU/ FRTU/FPIs shall be stored in daily RDBMS database
of ISR system.
2.2.8 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.
2.2.9 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.
Supervisory control shall allow the SCADA system to remotely control switching devices. A
control action shall require a confirmation-of-selection-prior-to-execution response. Initiation
of the control execute step shall occur after the dispatcher confirms that the correct point and
control action have been selected.
After the dispatcher/DMS function initiates control execution, the RTU/FRTU shall be
addressed for verification that the correct point has been selected at the RTU/FRTU and then
the control action shall be executed. It shall also be possible to reset the flag in FPI through a
command.
It shall be possible to issue control commands as a group control from SCADA where
switching devices pertaining to different RTUs/FRTU or a RTU/FRTU may be controlled as
a group. The SCADA system shall send the control commands sequentially (without
dispatcher intervention), if the commands pertain to switching devices in the same
RTU/FRTU, using the Selection Check before operate (SCBO) of prior–to-execution. The
control commands pertaining to different RTUs /FRTUs may be executed in parallel.
If, after selecting a point, the user does not execute the control action within a programmer-
adjustable time-out period, or if the user performs any action other than completing the control
action, the selection shall be cancelled and the user be informed. If the communication to the
Page 31 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
RTU /FRTU/FPI is not available, the control command shall be rejected and shall not remain
in queue.
The user shall not be prevented from requesting other displays, performing a different
supervisory control action, or performing any other user interface operation while the
SCADA/DMS system waits for a report-back on previously executed control actions.
The system shall process supervisory control commands with a higher priority than requests
for data from the RTU /FRTU /FPI data acquisition function.
Functional requirements for the various types of supervisory control are given below. A
supervisory control request shall be sent from control center only after the controlled point was
checked for proper conditions. The request shall be rejected by the System if:
1. The requested control operation is inhibited by a tag placed on the device or
maintenance tag
2. The device or S/S in local manual control mode
3. An Uninitialized, Telemetry failure, delete from scan, manual replaced,
Test/maintenance , or Manually Entered data quality indicator is shown for the
device;
4. The Operating Mode/ user permission of the workstation/console attempting
control does not permit supervisory control
5. The device is already selected for control request or control execution is from
another workstation / user/window /console or control request is progressing
6. Time out after selection
7. The device is not subject to supervisory control of the type being attempted
Rejection of a control request from control center shall occur before any transmission is made
for control purposes. A control rejection message shall be displayed for the Dispatcher
2.2.9.1 Digital Status Control
A digital control output results in the activation of an output relay in a RTU/FRTU.Different
commands shall be possible for these digital status controls.
Successful completion of the control request shall be recorded as an event. Failures to
complete shall be handled as specified in UI section. Control requests shall be canceled and
the selection of the point shall be terminated when the user cancels a request, does not perform
the next step of the control procedure within the selection time-out period from the previous
step of the procedure, or the request is rejected.
2.2.9.1.1 Breakers
The user shall be able to select and operate the two state controllable switching device i.e.
Circuit breakers/ LBS/ in case of RMUs, Isolator also
2.2.9.1.1.1 Reset flag of FPI
The user shall be able to select and operate switches or the reset flag of FPI as per utility
SoP.
2.2.9.1.1.2 Capacitor Banks
The user shall be able to control capacitor devices. The procedure for controlling these devices
shall be the same as that of a switching device except that any supervisory control action must
Page 32 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
be inhibited for a programmer-adjustable time period after the capacitor/ reactor device has
been operated. A message shall appear if an attempt is made to operate the device prior to
expiration of that time period & dispatcher is required to give command after expiration of
inhibited time period.
2.2.9.1.1.3 Tap Changing Transformers
SCADA system shall have the capability to raise and lower the on load tap position of the
transformers from SCADA control center through supervisory commands.
Depending on system conditions, the user may raise or lower the tap positions of On Load
Tap Changing (OLTC) transformers. OLTC's tap position needs to be monitored if supervisory
control action is to be exercised. OLTC tap position input shall be acquired as an analog value.
Tap excursions beyond user-specified high and low limits shall cause the master station to
generate an alarm.
Supervisory control of OLTCs shall only be permitted when the transformer's control mode
is Supervisory. All attempted invalid control actions shall be rejected.
For supervisory operations, the initial selection and control of the transformer for a raise/lower
operation shall follow the (SCBO) Sequence. Upon receipt of the raise/lower command, the
RTU will immediately execute the control action. It shall not be necessary for the user tore-
select the transformer for additional raise/lower operations; the user shall only have to repeat
the desired number of raise/lower commands, which shall be executed immediately. Normal
scanning functions shall not be suspended between the times that repeated raise/lower
commands are issued.
The user shall be able to cancel the operation or have it automatically cancelled by the master
station after a programmer-adjustable time period elapses after the last raise/lower command.
This multi-step procedure as described below
1. The RAISE and LOWER pushbuttons shall be displayed.
2. The command shall be launched as soon as RAISE or LOWER is selected.
The Raise and Lower buttons shall not be replaced by a single Execute
button. The RAISE/LOWER pushbuttons shall continue to be displayed,
and it shall be possible to initiate these controls repeatedly without
reselection of the controlled point, provided that the execution of the
previous control command has successfully been completed.
3. The RAISE/LOWER pushbuttons shall remain available until either (a) the
dispatcher clicks the CANCEL button or (b) the control times out due to
inaction by the dispatcher.
4. A separate timeout period, adjustable in the range of up to 120 seconds, shall
be provided for incremental control. The timer shall be reset and start counting
again whenever a RAISE or LOWER command is issued.
Successful completion of incremental control shall be recorded as an event. However failure
of incremental control, including failure to achieve the intended result, shall be alarmed.
2.2.9.1.1.4 Set point Control
The SCADA/DMS shall provide the capability to issue set point control using SCBO
procedure to field equipment The SCADA/DMS shall transmit a numerical value to the
device being controlled, to indicate the desired operational setting of the device.
Page 33 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 34 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
when the command is issued. At least ten timer periods of 1 to 60 seconds (adjustable in steps
of one second) shall be supported, any of which may be assigned to any device.
The user shall be provided with an indication that a control action is in progress and,
subsequently, a report of the result. If the control was unsuccessful, an alarm shall be generated
that states:
(a) The control message exchange was not completed successfully,
(b) The device failed to operate, or
(c) The device operated but failed to achieve the desired result (e.g., following a
close control action, a three-state device operates from the open state, but
remains in the transition state).
If the control was successful, an event message shall be generated.
For commands issued as part of a group control, DMS applications etc., the successful
completion of all device control actions shall be reported via a single message. If the operation
is unsuccessful, the user shall be informed of those devices in the group that failed to operate.
2.2.10 Fail-soft capability
The SCADA system shall be able to manage & prevent system from total shutdown / crash
etc.in the event of system crosses mark of peak loading requirements through graceful de-
gradation of non –critical functions & also relaxing periodicity / update rate of display refresh
& critical functions by 50%.
2.2.11 Remote database downloading, diagnostics & configuration :
The SCADA/DMS system shall be able to download database run diagnostics & create/modify
/delete configuration/ parameterization from centralized control center locations to
RTU/FRTU/FPI etc. using ASDU/ messages of respective protocols or file transfer.
2.3 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 database management system
(RDBMS) database as historical information (HI) data. This includes storing of data such as
SOE, status data, Analog values, calculated values, Energy values etc. Programmer shall also
be able to set storage mode as by exception in place of periodic storage.
Subsequently, the data shall be retrieved for analysis, display, and trending and report
generation. All stored data shall be accessible from any time period regardless of changes
made to the database after storage of that data (e.g., it shall be possible to retrieve stored data
for a variable that no longer exists in the SCADA/DMS computer system through backups on
storage medias viz. tapes /MO disks e t c . and initialize study-mode DMS functions with stored
data on the corresponding power system model).
The addition, deletion, or modification of data to be collected and processed shall not result
in loss of any previously stored data during the transition of data collection and processing to
the revised database.
It should be able to compress data, and should have 100% retrieval accuracy. However, the
retrieval of compressed historical streams should be of the same performance levels as normal
SCADA retrieval. The ISR should be able to interface over ICCP, OPC, ODBC and
CIM/XML, JSON to external systems (as defined by utility to interface with in the section
“Data exchange”) for analytics over SOA / ESB for Integration with IT Systems, over the
Enterprise Services Bus & SOA Architecture provided as part of legacy system. The ISR
Page 35 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
system shall act as the real interface between SCADA and IT System, where-by the real-time
operational system is not affected with a transaction processing system like IT, and the IT
Integration efforts will not in any way effect the real-time operationally of SCADA/DMS
System.
In ISR should also support ad-hoc queries /reports, and define display and report formats for
selected data via interactive procedures from operator workstations. Formatted reports and
responses to user queries shall be presented in alphanumeric or graphical format on either
operator workstations or printers at the option of the user. Procedure definition facilities shall
be provided for activities that will be frequently performed. 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 tags and ranges, station names, point names,
equipment types, status values, text string matches on selected data fields etc. and
combinations of these criteria.
It shall be possible to reload any IS&R archival media that has been removed from IS&R and
access the archived data without disturbing the collection, storage, and retrieval of IS&R data
in real-time.
The ISR system shall also be used for mass storage of data/files such as DMS application save-
cases, Output results of DMS applications, Continuous real-time data of selected time window
etc.
The online period of data tables is 24 months, however, there shall not be time restriction to
online availability of logs, real time data based on the stored values.
The System Design Parameters of ISR system is given in the chapter19
2.3.1 Circuit breaker status Table
The ISR function shall maintain a table in RDBMS database where real-time status of all
Circuit breakers, in case of RMU -LBS, isolators & Sectionalizers switching also along with
the associated quality codes shall be stored. The change of status of any breaker shall be
updated in this table as soon as the change is detected by the SCADA system. This table shall
contain additional information such as date & time of tripping, cause of tripping, Expected
duration of outage etc. Some of the causes of tripping could be Supervisory controlby user,
Protection tripping, Tripping / closing by DMS applications. Information on expected
duration of outage shall be taken from schedules for DMS application such as Load shed
application etc. For expected duration of outages due to p r o t e c t i o n tripping, the sameshall
be user enterable field. Such daily tables for 24 months duration shall be stored on auxiliary
memory (Online). Tables for the previous day shall be backed up to Magnetic tape/or any
offline storage device for this purpose by the user at 10AM daily.
The ISR function shall transfer the information available in the "Circuit breaker status table”
as defined above, and may be used by existing Customer Care center /legacy system using
SOA/Enterprise Service Bus, over ODBC/OPC/ICCP Adapters / Interfaces. The complete
Circuit Breaker Information shall be transferred to Customer care center on demand & by
exception along with the associated quality codes and additional information associated with
the CB.
2.3.2 Real-time Database Snapshot Tables
At the end of each 5 minutes, the following real time snapshot data shall be stored in RDBMS
in Real-time Database Snapshot tables:
Page 36 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
a) All telemetered analog values and Calculated values for all tele-metered analog
points (at least maxima & minima with associated time and average values).
Energy values are not envisaged for storage in Data snapshot tables.
b) All status values with time stamp
All the above values as specified above in (a) & (b) shall be stored along with their associated
quality code. The periodicity of the snapshot shall be user adjustable to include 5, 15, 30, and
60 minutes. Data Snapshot tables shall be created on daily basis. Such daily tables for 24
months duration shall be stored on auxiliary memory (Online). Tables for the previous day
shall be backed up to Magnetic tape/ or any offline storage device for this purpose by the user
at 10AM daily.
The ISR function shall prompt the user through a pop-up window to inform the user for taking
the backup. The pop-up window shall persist till user acknowledges the same. In addition to
that data can be stored on offline storage device.
The user shall also be able to initialize the study-mode power system analysis functions from
stored snapshot data.
2.3.3 Hourly Data tables
At the end of each hour information as defined below shall be included in the hourly data
tables, in RDBMS database form:
(a) Selected analog values along with their associated quality codes
(b) Selected status values along with their associated quality codes
(c) Results of hourly calculations for selected analog points (atleast maxima &
minima with associated time and average) alongwith their associated quality
codes.
(d) In addition to above a separate hourly energy data table exclusively for energy
values (Export and Import Active and reactive Energy values for each feeder)
shall be created in ISR alongwith their associated quality codes.
Hourly data tables shall be created on daily basis. Such daily tables for 24 months duration
shall be stored on auxiliary memory Online). Tables for the previous day shall be backed up
to Magnetic tape/ or any offline storage device for this purpose by the user at 10AM daily.
The ISR function shall prompt the user through a pop-up window to remind the user for taking
the backup. The pop-up window shall persist till user acknowledges the same.
2.3.3.1 Missed Hourly Data Storage
The programmer shall be able to independently assign any one of the following processing
for each hourly value to be executed when the value is missed and cannot be acquired prior to
the storage of hourly values.
(a) Store zero and a telemetry failure quality code for each missed hour.
(b) Store the last good data value, with a questionable data quality code, for each
missed hour.
(c) Temporarily store zero with a telemetry failure code for each missed hour.
(d) When the next good hourly value is obtained, divide that value by the number of
hours since the last good value was obtained and insert this value, with a
questionable data quality code, for all hours with missed data and the first hour
Page 37 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
that good data was obtained as is the case for energy values.
2.3.3.2 Hourly Data Calculations
The programmer shall be able to define calculated values using stored hourly data and
constants as operands. The calculations shall allow the carry-forward of data from one day,
week, or month to the next. The results of all calculations shall include quality codes derived
from the quality codes of the operands. The following calculations shall be provided:
(a) Addition, subtraction, multiplication, and division
(b) Summation of an hourly value by day, week, and month: The running total
of the summation for the current day, week, and month shall be updated each
hour and made available for display.
(c) Maximum and minimum of a value over a programmer-definable time period,
and the time the maximum or minimum occurred
(d) Average of a value over a programmer-definable time period
2.3.4 SAIDI/SAIFI table
SAIDI/SAIFI values of each feeder shall be stored on daily/ weekly/ monthly/ quarterly and
yearly and user defined timeline basis The values shall be determined from IEEE 1366
standard formula. In addition any customization as per Govt requirement may also be
incorporated.
The SAIDI/SAIFI data shall be determined from outage and restoration time (breaker on &
off /on cycle) and the time of outage. SAIDI /SAIFI shall be determined considering reason
of outage in terms of planned and unplanned outage (Planned due to maintenance /operator
command driven), Unplanned ( Fault/Trip driven ). In addition, the data consumer count and
load connected on feeder on monthly basis shall be updated from user entry or export from
IT system if any. There shall be suitable alarm/event message including user ID for such
activity. Such tables on daily/ weekly/ monthly/ quarterly and shall be available
The data so captured shall also derive town wise SAIDI/SAIFI on daily/ weekly/ monthly/
quarterly, yearly and user defined timeline basis. Such daily tables for two years duration
shall be stored on auxiliary memory (Online). Tables for the every year shall be backed up to
Magnetic tape/ or any offline storage device for this purpose by the user.
2.3.5 Daily Energy Data table
The daily energy data table shall be generated for storage of daily energy values for 15 minute
blocks / one hour blocks of a day & shall be stored for each feeder on daily basis along with
quality codes. This daily energy data shall be exchanged with the Billing system in Data
center/ legacy master billing center, if so defined to integrate in data exchange on daily basis
and on demand. This table shall be created on daily basis. Such daily tables for 24 months
duration shall be stored on auxiliary memory. Daily Energy data table for the previous month
shall be backed up to Magnetic tape by the user on the 10th of every month.
2.3.6 Load priority table
ISR system shall maintain a Load priority table containing information such as breaker name,
number of consumers connected to each Breaker and Load priority of each Breaker. In
addition, the priority of the feeders shall be updated from user entry or export from IT system
if any on monthly basis or user defined based on AT&C and revenue generation /collection
or any other priority Besides, this system shall also be able to set load priority based on the
AT&C an revenue information collected from IT system for each feeder
Page 38 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
There shall be suitable alarm/event message including user ID for such activity. The
table information shall be used by various DMS applications.
2.3.7 SOE data table
ISR system shall maintain SOE data table which shall store the SOE data for complete
distribution system. It shall be possible to sort the table by Time, Date, Substation name/,
feeder/line name, device name etc. using SQL commands. This table shall be made on daily
basis. Such daily tables for two years duration shall be stored on auxiliary memory. For the
purpose of sizing of table, daily 4 changes per SOE point may be considered. All CBs,
protection and alarm contacts shall be considered as SOE. Tables for the previous day shall
be backed up to Magnetic tape/ MO disks by the user at 10AM of every day.
2.3.8 Feeder Limit overshoot table
ISR system shall maintain feeder limit over shoot instances record for each feeder load for
overload condition, voltage for under voltage, over voltage and power factor for low power
factor any other parameter utility required to define Feeder Limit overshoot table. The data
shall contain count of such instances and duration for which feeder experienced such
condition and index for overshoot limit of voltage ) low ,high ), current ( high ), power factor
(low) etc on daily, monthly, quarterly, yearly basis. Such daily tables for two years duration
shall be stored on auxiliary memory. Tables for the previous day shall be backed up to
Magnetic tape/ MO disks by the user at 10AM of every day.
2.3.9 FPI fault table
ISR system shall maintain feeder FPI instances record for each feeder for o/c & E/F instances
required to define FPI index table . The data shall contain count of such instances and type
, section (FPI ) for which feeder experienced such condition and index for FPI fault index on
daily, monthly, quarterly, yearly basis. Such daily tables for two years duration shall be stored
on auxiliary memory. Tables for the previous day shall be backed up to Magnetic tape/MO
disks by the user at 10AM of every day
2.3.10 Equipment Failure Table
ISR system shall maintain record of DT, Power transformer failure information on weekly
manner . The same shall be collected from ERP system if any or any other system where such
data is maintained and also there shall be provision for user to enter data pertaining to failure
of power transformer and DT to determine DT & Power transformer failure rate shoot
instances record on weekly monthly, quarterly, yearly basis. Such daily tables for two years
duration shall be stored on auxiliary memory. Tables for the previous day shall be backed up
to Magnetic tape/ MO disks by the user at 10AM of every day.
2.3.11 User defined index table
ISR system shall maintain record of user defined indexes derived for performance from
telemetered data to record on daily weekly monthly, quarterly, yearly basis. Such daily tables
for two years duration shall be stored on auxiliary memory. Tables for the previous day shall
be backed up to Magnetic tape/ MO disks by the user at 10AM of every day.
2.3.12 Average time restoration table
ISR system shall maintain record of avg time to report outage location, restoration of supply of
feeder, project area on monthly, quarterly, yearly basis. Such daily tables for two years duration
shall be stored on auxiliary memory. Tables for the previous day shall be backed up to Magnetic
tape/ MO disks by the user at 10AM of every day.
Page 39 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 40 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
result in a total amount of load shed, which closely resembles the specified total. The
despatcher can then choose any of the recommended actions and execute them. The
recommendation is based on Basic rules for load shedding & restoration
In case of failure of supervisory control for few breakers, the total desired load shed/restore
will not be met. Under such conditions, the application shall inform the dispatcher the balance
amount of load to be shed /restore. The load-shed application shall run again to complete the
desired load shed /restore process. The result of any Load Shed operation shall be archived
in Information storage and retrieval (IS&R) system.
2.4.1 Basic rules for load shedding & restoration
The load shall be shed or restored on the basis of following basic rules:
(a) By load priority
The LSA shall have a priority mechanism that shall allow the user to assign higher priorities
for VIP/ Critical loads or any other important load or feeders with high revenue or low AT&C
losses. The load assigned with the higher priorities shall be advised to be shed later and restore
earlier than load with relatively lower priorities. Each load priority shall be user definable
over the scale of at least 1-10.
(b) By 24 Hrs. load shed /restore history
The loads of equal priorities shall be advised for restoration in such a way that loads shed
first shall be advised to be restored first. The application shall ensure that tripping operations
is done in a cyclic manner to avoid the same consumers being affected repeatedly, however,
priority loads shall be affected least.
(c) By number of consumers affected
The consumer with equal priority and similar past load shed history shall be considered by
the application in such a way that minimum number of consumers are affected during the
proposed load shed. The data for number of consumers connected to a feeder /device shall be
taken from computerized billing system.
2.4.2 Modes of operation
The load-shed application shall operate in the following modes:
(a) Manual load shed
(b) Manual load restoration
(c) Auto load shed
(d) Auto load restoration
Each mode of operation can be enabled or disabled by operator independently. The load
can be shed & restore in possible combination i.e. manually shed & auto restore vice versa or
both operations in the same modes.
2.4.2.1 Manual Load Shed
In this mode operator specifies a load to be shed in a project area The software shall determine
& propose all the possible combinations of switches to be operated for the requested load
shed considering the basic rules for load shed & restoration.
In case more than one options are possible, then the application shall identify all such options
with the priority of consumers along with the number of consumers are likelyto be
affected for the particular load shed option. The despatcher shall select & execute one
Page 41 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 42 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
suitable protection to ensure that shall be provided in user interface such as discard ,forbidden
etc. if user accidently enters LSR _stp higher or equal to LSR_str or LSR limits or LSS _str
higher or equal to LSS_stp or LSR limits, lower than LSS . The sequence of frequency limits
shall be permitted as LSR str>LSR_stp>LSS _stp >LSS_str. Adequate protection as
mentioned above shall be given if user tries to violate the same.
(b) Time of day based restoration
The function shall operate to restore load at the predefined time of the day & load to be
restored. The software shall automatically execute the switching operations considering the
basic rules for load shed & restoration.
2.4.3 Alarms/Events
All Load shed & restore operations executed shall be logged in the system as events. In case
the supervisory control fails during the operation in predefined time, an alarm shall be
generated with the possible reason for the failure.
2.4.4 Summary Report
Load shed application shall generate Summary Reports for project area on daily basis. These
reports shall be available online for minimum period of two days. The following reports shall
be made.
(a) Daily Load shed report indicating, substation name, feeder/device name,d
a t e /time, duration of load shed and amount of load shed, Number of
consumers affected based on consumer indexing information, mode of load
shed including planned outages of feeders/network equipments.
(b) Daily Alarm summary pertaining to LSA, substation wise.
(c) Substation wise daily Served, un-served power & energy for every 5 minute
time block
(d) Served & un-served power for last seven days for every 5-minute time block
to calculate Load forecast for the next day. The report shall contain a column
to define weightage factor (multiplier) by despatcher to calculate Load forecast
for the next day. The weightage factor is required to consider the type of the
day such as holiday, festivals, rainy day, etc. Separate report for total load
forecast of complete project area shall also be generated from above two
reports.
2.5 Common Disaster Replica Recovery Centre ( DRR)
The same shall be replica of SCADA DMS Control center for Group A and with secured
permission and upon non availability of main SCADA/DMS Control center, the operation of
that town shall be possible from DRR. However, system shall remain in sync at hourly basis
and shall be suitable interlocks to avoid any accidental command. In case main control center
is not available, all underlying equipment i.e. RTU/FRTU/FPI etc shall switch reporting to
DRR and DRR will now act as master and sych old master. The process of switching shall
not take more than 15 minutes. Now, after swapped configuration of DRR and Main Control
Centre, the data sych shall continue from new master SCADA Centre to swapped DRR centre
2.6 Data recovery function (DR)
The DR function is a repository of system build up software of all towns Group B & Group
C towns.Two year online backup shall be available at this location with data pertaining to
each town i.e. system build ups shall be available of each town separately so that the same can
Page 43 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
be utilized upon setting up newer system after disaster. The data related to network model of
SCADA/DMS control center of each town shall be sent to DR center periodically once a day
& upon user request. The data shall be configured to be sent globally & incremental. All logs,
data model etc. & necessary interfaces that are essential for complete system build up shall be
stored at DR center. All requisite data which is build the system from scratch shall be
transferred to DR. An alarm shall be generated & send to SCADA/DMS control center upon
attaining user defined threshold e.g. 80% for storage at DR center.
2.7 RT-DAS system
The RT-DAS system shall use control center of Group B towns and shall have SCADA
features except control capability. However, the same may be upgraded for enabling control
,if need be without additional license and only by adding output cards and enabling in the
configuration software.
End of Chapter 2
Page 44 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 45 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
A network overview display of the distribution system with substations, feeders color 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. 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 the distribution network using what if analysis.
All DMS result tabular displays shall have capability for sorting by name and calculated
parameters. The solution prescribed by DMS application shall consider & identify & sort
the following as minimum.
1. Remote controllable circuit breaker with capability to interrupt fault currents
2. Non-remote controllable circuit breaker with capability to interrupt fault currents
3. Remote controllable circuit breaker with no capability to interrupt fault currents
4. Non-remote controllable circuit breaker with no capability to interrupt fault
currents.
5. Remote controllable disconnector
6. Non remote controllable disconnector.
7. Fuse
8. Ground/ Earth switch etc.
9. RMUs
10. Sectionlizer
11. Communicable FPIs
Network Model, GIS association
The DMS applications shall have a common model for the project area comprising of primary
substation feeders, distribution network and devices with minimum 10 possible islands, which
may be formed dynamically. All DMS applications shall be able to run successfully for the
total distribution system with future expandability as envisaged under the specification. The
following devices shall be represented in the model as a minimum:
a) Power Injection points
b) Transformers
c) Feeders
d) Load (balanced as well as unbalanced)
e) Circuit Breakers
f) RMUs &Sectionizers
g) Isolators
h) Fuses
Page 46 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
i) Capacitor banks
j) Reactors
k) Generators
l) Bus bars
m) Temporary Jumper, Cut and Ground
n) Ring, Meshed & radial network configuration
o) Line segments, which can be single-phase, two-phase or three-phase and
makeup a distribution circuit.
p) Conductors & Cables
q) Grounding devices
r) Fault detectors/FPI
s) IEDs
t) 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 DMS application shall be
available for printing at user request.
Population and maintenance of the distribution network model should be possible by using the
database maintenance tools to build the database from scratch. In case the required data already
exists within the Employer’s corporate Geographic Information System (GIS) as a legacy, the
DMS database functions should leverage this effort by providing an interface/adaptor to extract
GIS data using the CIM international standard IEC 61970/61968 and automatically generate
the complete Network Operations Model. The data extracted should include network device
information, connectivity, topology, nominal status and non- electrical data such as cable,
l a n d b a s e data etc. Further Land base data can be sourced from GIS in Shape files or DXF.
The utility shall provide all necessary details of legacy system for interface and to use this data.
The extraction process should comply with the international standard CIM data descriptions.
The CIM standard is maintained by the IEC (Technical Committee 57, WorkingGroup 14) and
is used for a wide range of purposes. The extraction process should be independent of the real-
time network management system. 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-based data (provided as a dxf file, shape file etc.) may also be displayed as required.
Page 47 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
An interface with the already existing Geographical Information Systems shall be developed
using interoperability features between the DMS and the installed GIS.
Each of the two systems shall keep its own specificity, and shall be used for what it has been
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 two systems use.
It shall be implemented while maintaining the SCADA/DMS and GIS integrity as individual
systems. It is of the utmost importance that the two systems remain able to operate separately.
The required functionalities for this interface shall cover the two following aspects:
The transfer of specific real-time data from the DMS into the GIS data-base the possibility to
navigate easily from one system to the other through the user’s interface
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.
In case of non-availability of the interface details of legacy system by utility. GIS adaptor shall
tested to establish with sample database and the bidder shall run the same through, single line
diagrams schema with network element parameters.
Utility shall specify availability of updated GIS based asset /network database and GIS
application software In case of non-availability of the same , utility shall be provided through
sanctioned scope of IT/AMISP etc or on their own funds. For SCADA/DMS , if existing
database of electrical assets is not up to date or incorrect. Bidder may consider , the scope of
survey , data entry , updation in their scope . Further , if license is not upto date. Then bidder
shall in their as part of “any other items required to meet functional and performance
requirement” in the BOQ . The details software ,available interface and state of data to be
specified in the legacy section .i.e chapter 1 of RFP
As an option , utility may also include GIS software also in the RFP as per approved IT OR
/SCADA projects . There shall not be duplication in IT (AMISP etc and SCADA). Key feature
/ specification is given in the table below:
Sr.No. GIS Specifications
Geographic Information System solution consists of a system for capturing, storing,
checking, integrating, modification , analyzing and displaying geo data related to positions
on the Earth's surface and data related to attributes of the entities/Customers in an utility
1 area. It pertains to both vector and raster GIS
The GIS product shall have an industry standard Data Model and shall be CIM compliant.
2 Standard adaptors to export the data in CIM model should be available off the shelf.
Geographic Information System solution shall support modelling of High voltage, Medium
voltage and Low voltage distribution network and associated assets including Generators,
HV lines, HV Transformers, MV lines (OH & UG cables), Poles, Primary Substations, LV
lines (OH, ABC & UG cables, 1Phase, 2Phase & 3Phase), Switchgears, Auto-Reclosers, Load
Break Switches, DDLO’s, Distribution Transformers, LV fuses, Retail & Bulk customers ,
3 RMU, IED , FPIs etc using appropriate GPS coordinate system .
Existing data if available with discom will be shared with the bidder which shall be migrated
4 to the proposed GIS solution by the bidder.
Bidder will propose to follow the three-stage database modeling process involving
Conceptual, Logical and Physical data models. The finalization of the data model would be
performed as part of SRS jointly with discom. To design the Data model, Bidder will
5 develop conceptual model to assemble a high-level abstract representation of the GIS
Page 48 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
layers and to identify basic relationship between data entities by grouping of simple
features into categories or thematic groups. Standard five key elements of Geo database
design
Logical model will be developed further to visualize clearly data relationships, shapes and
business attributes and finally Physical model will be prepared which will constitute
complete details, defined schema design and specifically defines attributes and their
characteristics like Relationships, Subtypes,
Domains, Topology Rules, data dictionary, primary keys for each feature class. Fine-tuning
6 of these models will be performed until all the data requirements are fulfilled.
This shall enable creation of GIS base application geo-database, which shall provide
interfaces to the business process applications presently operational in the utility and to
7 future business applications planned to be implemented by the utility.
Shall support structured export of connected network in CIM/XML format for one-time
initial load as well as incremental changes. Shall also support structured publishing of
8 proposed network changes with SCADA/DMS/OMS system.
The GIS Enterprise software package with latest version, and spatial database engine with
industry proven database specifically for maintaining spatial networks and long
transaction spatial handling scaling up to very large numbers of users and terabytes of
data with latest version supplied. The system shall have to be Open GIS consortium (OGC)
9 registered compliant product time tested, widely deployed at multiple utilities worldwide
The system shall provide support in the form of a documented interface specification
10 (API) to allow software - based functionality
11 The system should have functionality to Zoom; PAN the display across the screen.
. The system shall generate color graphic displays of the system network which can be
zoomed in / out. This shall represent each of the elements in the electrical system with
suitable differing colors for the elements. The color-coding will be based on the rated
voltage, Percentage of voltage at each bus,
12 Percentage of loading of section, Symbols or any other chosen parameters by user.
Dynamic selection of attributes: User should be able to dynamically select one or more of
the attributes of an object, to be displayed as label of the object. This can be for viewing,
13 plotting and printing purposes
14 System should be able to perform move, copy, rotate, mirror and offset.
15 System should specify the real time measurement / length while drawing the lines.
Ability to report the lengths of conductors and the associated cost of the conductor (if
16 available from associated compatible units.
The graphic user interface shall have a modular structure with main menus and sub-
menus that allow users to dynamically configure their own user interface to required
17 level.
It shall be possible to view the system elements such as Customer location etc on,
mapping and indexing work. It shall be dynamically possible to switch from one mode of
view to the other by use of a pointing device. It shall be possible to view the physical
18 system details in the background of the area maps created
The application should have facility of cluttering and decluttering. The process of showing
more details as users zooms in is called cluttering and process of hiding details as user
19 zooms out is called decluttering
The software shall be able to check the electrical network line continuity for the power
flow through graphical and non- graphical data as listed below :
The electrical line tracing till the end of the line by considering the switch positions on the
20 line. The line will have to be highlighted after the tracing.
Should provide a collection of tools for managing, modelling, and editing facility and land
21 base data in an enterprise system.
Page 49 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Should have configurable tools such as.
• Support electric feeder/circuit creation and configuration
• Support to industry standard utility data models
• Support various types of electric feeder Traces (upstream, downstream, protective
device etc.).
• Network trace shall be configurable – By Voltage Class (HV,MV,LV), phase, circuit,
22 upstream/downstream, etc.
Should support for Standard distribution operations such as Phase Change/Phase
propagation,
Replacement or Addition of Conductor, Rotation of phasing information, updating flow
23 directions, updating voltages etc
Should have out of the box tracing tools for the Electric utility:
• Find Downstream features
• Find Upstream features
24 • Protective device trace and options
It should have out of box tools to store stored items and can update attribute in a mass
25 manner.
26 Database extraction tools for importing and exporting network data.
Page 50 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Create statistics & various statistical operations, viz. create charts and reports, and Sort
38 tables by multiple attributes, populate values based on expression, Summarize data.
39 Should be able to plot data on the map directly from the tables.
40 Software should support Display graphs, charts and calculated values
Tool should have simplified view of the network for better operations management and
41 faster decision making.
42 Tool should Check network connectivity
GIS solution shall be a integrated GIS product to deliver value beyond just asset data
tracking.
GIS Software should be compatible to be integrated with enterprise systems such as AMI,
Mobile work Force Management, SCADA, DMS,OMS ERP, Online billing System, or any
43 other system to be used by utility in future with standard interface specificied.
44 Data analytical dashboards / reports
Page 51 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
The NCA shall assist operator to know operating state of the distribution network indicating
radial mode, loops and parallels in the network. Distribution networks are normally operated
in radial mode; loops and/or parallel may be intentionally or inadvertently formed.
A loop refers to a network connectivity situation in which there exist alternative power flow
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 one power source. Parallel paths often result in circulating currents
and such operating conditions need to be avoided. All loops/parallels in an electrical network
shall be shown 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 or CLOSED
position.
Alarms shall be generated when presence of abnormal switches, De- energized components of
network and of Network loops / parallels is detected.
3.1.1.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 when
information available is not complete or inconsistent. The trace shall persist through
subsequent display call-ups, until the operator explicitly removes it or requests another trace.
In addition, at the bottom of the geographic view the number of transformers and customers
passed by the trace are shown.
(a) Feeder tracing - This feature shall aid dispatcher to identify the path from a
source to all connected components by same color.
(b) Circuit tracing- This feature shall enable operator to select any device and
identify the source 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 of the 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 that are downstream of the selected element. In the case where a
downstream trace is performed on a de-energized section of the network, the trace
highlights all devices electrically connected to the element.
3.1.1.2 Temporary Modifications:
The NCA will allow temporary modifications at any point in the distribution network to change
the network configuration, to isolate faults, restore services or perform maintenance. A
Summary shall list the jumpers, cuts and grounds that are currently applied. The function is
performed by the NCA and is implemented locally within the client software and has no effect
on the operations model or other clients viewing the network.
3.1.1.3 Cuts:
Cuts facilitated in any line segment in the network. The cut may be applied to one or more
available phases of the conductor. The cut could also be applied as a temporary switch inserted
in the line.
The cut must be given a name or id number for identification, which is
displayed as a label on the geographic network view.
It should be possible to select the position of the label relative to the cut
symbol.
Page 52 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
The position can be altered after the cut has been placed.
Once placed the cut symbol can be selected and switched on and off by the operator in the same
way as a standard disconnect switch. Cuts can also be tagged.
3.1.1.4 Jumpers
Jumpers are a means of providing a temporary, switchable connection between two points on
the network. The operator should be able to select two points and place the jumper 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 connection between the two points but
other partial or cross-phase connections may be made if required. The popup shall warn the
operator about abnormal connections such as not all phases being connected or the nominal
voltage being different at the two connection points. Once the jumper has been placedthe switch
symbol in the center can be selected and switched open or closed. The topology of the network
model is updated accordingly. There is no restriction on the placement of jumpersbetween lines
connected to different feeders or different substations.
Temporary connections between phases on the same line segment, known as a phase jumper
shall be supported. This can be used in conditions where one phase is de-energized and it is
desired to restore customers by energizing the dead conductor from one of the live phases.
3.1.1.5 Temporary Grounds
Temporary grounds should only be placed, for obvious reasons, on de- energized sections of
a line. These grounds represent the mechanical grounding of lines for safety purposes during
maintenance or construction.
A temporary ground may be placed on one or more of the available phases. It must be given a
name and addition information can be included in the description field.. If a line segment is re-
energized while a temporary ground is still applied, the ground will be automatically removed.
3.1.1.6 Reports and Displays
The reports and displays shall be generated indicating the followings as a minimum:
(a) Abnormal switches in tabular display
(b) De-energized components of network in tabular display
(c) Presence of loops & parallels on network displays
(d) Un-served/ disconnected loads (loads affected due to tripping of CBs) in
tabular displays
(e) List of temporary jumpers/cuts /grounds
3.1.2 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 of all buses, sections and
transformers, active and reactive power losses in all sections and transformers, etc.).
Firstly, the symmetrical (per phase) and asymmetrical (three-phase) load of all nodes in the
radial or weakly meshed MV network, which are not remotely monitored, that is not directly
covered by the SCADA System shall be using evaluated Load Calibration . SE represents the
basic DMS function, because practically all other DMS Analytical Functions are based on its
results.
Page 53 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
This is the unique function dealing with the unobservable load of the actual network, which is
not directly covered by the SCADA System. Function is used for balanced and unbalanced
networks.
The function is based on an algorithm specially oriented towards distribution networks, with
low redundancy of real time, remotely monitored data, The deficiency of real time data has to
be compensated with historical data.
Beside the parameters of network elements, the real-time data consists of:
Actual topology, transformers tap changer position, etc.
Voltage magnitudes of supply point and other nodes in the network.
Current magnitudes (active and reactive power) at feeder heads.
Current magnitudes (active and reactive power) from the depth of the network.
The historical data of the network consists of:
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), for
e.g. four types of days (for example: weekday, Saturday, Sunday and holiday).
Peak-loads for all distribution transformers and/or consumers (peak-currents
and/or peak powers) and/or monthly electric energy transfers across all
distribution transformers (consumers).
SE function shall run in all cases from the range of networks where all historical data are
known, but also in networks with no historical data available (based on parameters of the
network elements).
Also according to users setting, the SE function shall be able to 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 be used
for estimation of the current state. In the Simulation mode, the function is used for estimation
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 and
compensates them with historical data, pseudo and virtual measurements, to achieve the
minimal set of input data necessary for running a consistent Load Flow.
The SE algorithm shall consist of the next important steps:
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.
Verification of measurements– It shall be obtained from artificially redundancy of
measurements (too small number of measurements and notable main number of
pseudo measurements obtained from first approximation). This step shall consider
Page 54 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
two sub-steps: (a) in sighting evidence bad measurements, (b) verification and/or
correction all permanent measurements. In this step, incorrect measurements shall be
corrected or discarded.
Load calibration – The function shall distribute the load to the busbars of the MV
network on the basis of the set of verified measurements and historical data.Also,
Load calibration shall deal with consumers specified directly through their
current/time diagrams i.e. load curves as well as with consumers with constant
consumption. The function shall run even any of these data are not available. It shall
be designed in such a way that the quality of results of the function running increases
directly with the amount of given data.
Load Flow calculation – This shall be the next function in the specification based on
the loads assigned in the previous step.
3.1.2.1 Input/output
Beside the network element parameters, main inputs for the functions consist of above noted
real time and historical data. In the case of the function running in the Simulation mode, the
real time data must be replaced with the corresponding data from the saved cases or forecasted
ones.
Main outputs of the function are estimation of:
Voltage magnitudes in the entire network.
Current magnitudes and power factors for all network elements.
Loads of all MV and LV consumption buses.
Losses of active and reactive powers in the entire network, by each supply
transformer or feeder.
Beside those results, output of SE function is tabular report, also. In this report measurement
verification results are presented those results are:
Pre-estimated and estimated values of measurements. Minimal and maximal
expected values of measurement. Quality of each measurement.
Deviation measured values from estimated and pre-estimated values.
3.1.3 Load Flow Application (LFA)
The LFA shall utilize information including real-time measurements, manually entered data,
and estimated data together with the network model supplied by the topology function, in order
to determine 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 data
b. Manual entered data
c. Estimated data
d. Power source injections
e. Loops and parallels
Page 55 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 56 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
The Event Triggered LF execution shall always have the highest priority. The study mode LF
function shall be executed on a snapshot or save case with user defined changes made to these
cases. The study mode execution of LF Function shall not affect the Real-time mode execution
of LF function.
(a) Event Triggered Real Time LF Execution:
The LF function shall be executed by pre-defined events that affect the distribution system.
Some of the events the dispatcher may choose for triggers shall include:
Power system Topology Change i.e. Alteration in distribution system
configuration.
Transformer Tap Position Change / Capacitive/reactor MVAR Change
Feeder Over loadings
Sudden change in feeder load beyond a set deadband
(b) Periodic Real Time LF Execution:
The real-time distribution system load flow application shall be executed periodically as
configured by the dispatcher. The function shall be executed periodically even if there are no
significant changes in the operating conditions, as some of the power flow outputs shall be
required to provide aggregate summaries (losses, etc.)
(c) On Demand Real Time LF Execution:
Dispatchers may initiate the real-time LF function at any time through dispatcher command.
(d) Real Time LF Execution initiated by other DMS Applications:
Other DMS functions may initiate the real-time LF function at any time as desired for the
execution of the respective functions.
3.1.3.2 Study Mode Load Flow Execution:
It shall provide despatchers 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 access of the real
time data as necessary. Study mode load flow shall be used to study contingency cases.
It shall be possible to prepare and store at least f i f ty cases along with the input parameters,
network configuration and output results.
The dispatcher shall be able to select the saved Case to be used as a Base case for LF execution
and modify the base case. Possible changes, which the dispatcher shall be permitted to make,
shall include:
(a) States of individual power system elements
(b) Values of specific parameters including nodal loads, bus voltages, connected
kVA, power factor etc.
The Study Mode shall calculate various values for each feeder and prepare summaries as LF
output.
The Load Flow function shall provide real/active and reactive losses on:
Station power transformers
Feeders
Page 57 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Sections
Distribution circuits including feeder regulators and distribution
transformers, as well as the total circuit loss
3.1.3.3 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, section
(c) Total three phases and per phase KW and KVAR losses in each feeder, section,
transformer, DT substation & for project area
(d) Active & reactive power flows in all sections, transformers List of overloaded
feeder, lines, bus bars, transformers loads etc. including the actual current
magnitudes, the overload limits and the feeder name, substation name
(e) List of limit violations of voltage magnitudes,
overloading.
(f) Voltage drops
(g) Losses as specified above
3.1.3.4 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 phase
losses for each substation, feeder and project area. All the overloaded lines, busbars,
transformers, loads and line shall start flashing or highlighted.
The LF outputs shall be available in the form of reports. The report formats along with its
contents shall be decided during detailed engineering.
3.1.3.5 Alarms
The LFA shall warn the Despatcher when the current operating limits are exceeded for any
element or when lines are de-energized. It shall also warn the Despatcher 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.
3.1.4 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.
The following resources will be taken into account for voltage and reactive power flow control:
TAP Changer for voltage control
VAR control devices: switchable and fixed type capacitor banks.
Page 58 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
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 despatcher shall
have the option to simulate switching operations and visualize the effect on the distribution
network by comparisons based on line loadings, voltage profiles, load restored, system losses,
number of affected customers. The solution shall identify /sort the different type of switches
that are required for operation i.e. remote /manual etc.
3.1.4.1 Modes of operation
The VVC function shall have following modes of reconfiguration process:
(a) Auto mode
(b) Manual mode
The despatcher shall be able to select one of the above modes. These modes are described
below:
Auto mode
In auto mode, the function shall determine switching plans automatically and perform
switching operations upon despatcher validation automatically.
Manual mode
In manual mode, the function shall determine switching plans automatically and perform
switching operations in step-by-step manner.
A filter for remote operable & manual switches shall be provided with switching plan.
3.1.4.2 Reports
Detailed reports of complete switching sequence for VVC operation, including voltage / VAR
levels before switching & after switching shall be presented.
3.1.4.3 Displays
The User interface for VVC function shall have following summary displays as minimum:
(a) Network & tabular display to VVC switching
(b) Tabular display giving chronological sequence for VVC operation
Page 59 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
phase faults and shall not be restricted by their time of occurrence on one
or more feeders. Thus, the ability to handle multiple faults of different types,
on multiple feeders, shall be provided. It shall be capable to carry out
restoration of large area after a occurrence wide spread faults amounting to
substantial outages in the town.
2) FMSR shall be capable of allowing the substitution of an auxiliary circuit
breaker or line reclosers that may temporarily function in place of a circuit
breaker or line reclosers that is undergoing maintenance.
3) The Operator shall be able to suspend FMSR restoration capabilities by
activating a single control point. 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 same point.
4) FMSR shall be capable of isolating faulty sections of network by opening
any available line Circuit Breaker that may be necessary, however operating
limitations on device such as control inhibit flag shall be respected.
5) FMSR application shall utilize the results of LF for recommendations of
switching steps for 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 of restorations ,the operator shall
have the privilege of selecting the best restoration option suggested by
FMSR before it starts restoration .The operator shall also be to simulate the
LF for the recommended switching actions ,so that the necessary violations
can be displayed on graphical display also. If an overload condition is
expected as a result of the proposed switching, it shall be displayed to the
operator on a graphical display and proposed alternative switching
sequence to avoid or minimize the overload.
6) FMSR shall be capable of using data derived from substation RTUs/FRTUs
/FPIs to recognize faults in substation transformer banks, any fault on the
primary side of these banks that cause loss of outgoing feeder voltage and
current or any fault occurred on 11KV network.
7) FMSR shall be capable to make Restoration plans with identification name
and respective merit orders & its execution of Restoration plan using
network Display and single 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 pending restoration actions.
3.1.5.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 network as faulty. On detection of fault in the network, an alarm
shall be generated to draw attention of the dispatcher.
Switching device tripping caused by SCADA/DMS applications shall not be considered as a
faulty condition. FMSR application shall also not be initiated if the quality flags such as,
manually replaced value , and Out of scan are set for a switching device.
Page 60 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
To avoid potential difficulties during severe storm conditions, the Operator shall be able
to suspend FMSR switching sequence of restoration capabilities by activating a single control
point. 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 as detect
and isolate faults following the next outage event. The same shall be recorded as an event.
3.1.5.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 are having no intermediate fault indicators & intermediate switches are
not capable to trip on fault upto the closest NO(Normal open) point, the dispatcher can open
the last switch before NO point & try to close breaker , if trips again faultis on further upstream
& the same method is to be repeated else fault is located in the downstream section only. For
t h e sections where protection signal or FPI indication is available, the same shall be derived
through these telemetered signals. Network diagram identifying the faulty
sections/components shall be displayed identifying 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 currents
2. Non-remote controllable circuit breaker with capability to interrupt fault
currents
3. Remote controllable circuit breaker with no capability to interrupt fault currents
4. Non-remote controllable circuit breaker with no capability to interrupt fault
currents.
5. Remote controllable disconnector
6. Non remote controllable disconnector.
7. Fuse
8. Ground/ Earth switch etc.
3.1.5.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 done be by
closing NO switch to allow the power from alternate source. In case more than one feasible
switching plan exist, the despatcher shall be guided for most optimum plan based on the merit
order ie minimum switching operations, minimum loss path, and system operation within the
safe limits of various network elements. The despatcher shall have the option to simulate
switching operations and visualize the effect on the distribution network by comparisons based
on line loadings, voltage profiles, load restored, system losses, number of affected customers.
The FMSR function shall have feature to attain the pre-fault configuration on despatcher’s
request after repair of faulty sections.
The FMSR function shall have following modes of restoration process:
Page 61 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 62 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 63 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
SCADA system while recommending the switching operations. The function shall distribute
the total load of the system among the available transformers and the feeders in proportion to
their operating capacities, considering the discreteness of the loads, available switching
options between the feeder and permissible intermediate overloads during switching. The
despatcher shall have the option to simulate switching operations and visualize the effect on
the distribution network by comparisons based on line loadings, voltage profiles, load restored,
system losses, number of affected customers.
3.1.7.1 Modes of operation
The function shall have following modes of reconfiguration process:
(a) Auto mode
(b) Manual mode
The despatcher shall be able to select one of the above modes. These modes are described
below:
Auto mode
In auto mode, the function shall determine switching plans automatically for load balancing in
the network and perform switching operations upon despatcher validation automatically.
Manual mode
In manual mode, the function shall determine switching plans automatically for load balancing
in the network based on which despatcher can perform switching operations in step-by-step
manner.
A filter for remote operable & manual switches shall be provided with switching plan,
3.1.7.2 Displays & Reports
The summary report shall cover the followings:
(a) Loadings of feeders and transformers before and after reconfiguration.
(b) Voltage profile of the feeders before and after reconfiguration.
The report shall also highlight violations that are occurring in the network with display layers
before and after reconfiguration.".
3.1.8 Operation Monitor
The Operations Monitoring function shall track the number of operations made by every
breaker, capacitor switch, reclosers, OLTC, isolator and load break switch that is monitored
by the System. Devices shall be identified by area of responsibility, substation, feeder, and
device ID to provide the necessary information for condition-based maintenance of these
devices.
Each monitored device shall be associated with a total operations counter. This counter shall
be 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 uncommanded trip operations. The date and time of the last operation shall be saved
for each device when one of the counters is incremented.
An Operator with proper authorization shall be able to enter total operations and fault
operations limit for each counter. An alarm shall be generated when a counter exceeds its
limits. No additional alarms shall be generated if the counter is incremented again before it is
Page 64 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
reset. For each counter, the System shall calculate the present number of operations expressed
as a 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 to
inhibit operations counting for individual devices. Such devices shall be included in
summaries based on areas of responsibility. Resetting and inhibiting counters shall be
permitted only for devices that belong to the areas of responsibility and resetting shall require
the console to be assigned to an appropriate mode of authority. The user info, date and time,
when each counter was last reset shall be saved.
The countersand 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 together
with its accumulated operations data by simply selecting the device on any display where it
appear
3.2 Outage Management System
3.2.1 Outage Scheduling Management
Full-fledged OMS is envisaged in A/U towns and in B/C it is limited to Fault reporting from
FPI to maintenance crew over mobile and information to customer care centre and
considered in SCADA functions and servers under B/C towns
The system shall enable utility to partially or completely deenergize an electric circuit and
notify utility concerned personnel and provide interface to customer care system. The system
shall exhibit following features
Advance notifications
Priority Management of outage requests
Work permits
Generating switching plans to support the power outage requests
Status updates
Work order completion
Notifies affected customers in advance so that they have adequate time to make
appropriate decisions or alternate plans
Allows for field crew to communicate delays in planned work and assists in
providing a timely update to the expected time of restoration
Allows for field crew to promptly provide notifications when their work is
completed
Crews can submit preliminary information about changes made to the
energized system, and close the associated work orders or tasks
3.2.2 Trouble Call Management System
Customer outage related trouble call management system summarizes all of the ticket
information and primarily used by the operator or dispatcher to analyze the location of any
ticket (prediction or confirmed outage). The data of OMS regarding outages / tickets shall
be shared with Customer Care Centre of DISCOM.
The system shall exhibit following features:
Trouble call summary display provides an itemized summary of all trouble
calls on the system in whole or by area.
Switching devices operated by SCADA as a commanded change of state will
Page 65 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
generate an outage ticket which does not have to be confirmed by a crew.
Telemetered protective devices operate automatically on a fault condition when
they are tripped by relay. In this condition, outage prediction will 'walk'
downstream to predict incident downstream of tripped protective device.
If a telemetered protective device closes automatically, or under SCADA
control, the system will close the outage ticket and commence with the call
back process to inform the affected customers.
Trouble calls are organized into accounts and may be expandedby
geographical, electrical or work areas:
Normal
Critical
Premium / VIP
Medical, etc.
SCADA generated outages are logged as SCADA generated so as to
differentiate them from trouble calls generated manually or by the prediction
algorithm.
Customer-centric information organized and displayed both graphically and in
tabular form by area
User friendly table organizes the calls into the following basic ticket groups
which are filtered by type based on the user’s area of responsibility:
Unassigned
Assigned
Incident
Trouble Calls
Outages
Completed Trouble Calls
Rejected
Closed
3.2.3 Crew Dispatch & Work Management Key Features
Crew & Work Order Management provides an organized and efficient way to manage the
correlation of crews to Work Orders or Tickets. Crew Management user interface enhances the
dispatcher and supervisor’s situational awareness via an easy to use and visual progress of
outage restoration or work resolution.
Enables Operator / Dispatcher to monitor crews and assign crews to jobs
Manage crews and activity related to daily work orders
Schedule the work for independent creation, tracking and management of each
job
Work orders may be linked to Trouble Calls if the work order is related to the
outage
Dispatcher is able to monitor the crew workload and the crew’s progress.
Page 66 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Summary screens to monitor and manage Work Orders and Trouble Calls
Crew workload can be balanced to handle changes in the personnel or resources
3.2.4 Outage Analytics & Reporting
Real-time dashboard summaries as well as detailed tabular and customizable graphic reports
supporting drill-down and query capability shall be built up
User-defined reports covering crew, trouble calls, outage, outage codes, call
codes, failure codes, calculations, area reports, device operation, planned
outages, etc.
Create custom reports using drag and drop from the data model.
Automatic calculation and reporting of several performance indices including
IEEE 1366 continuity of service indices: SAIDI, CAIDI, SAIFI, MAIFI, etc.
Quality of Service (QoS) reporting based on the logged events, times and
degree of restoration for display and reporting.
Reporting to crew through SMS about on configured feeder manager nos.
The following reports shall be minimum and shall be defined apart from utility specific
reports :
Outage History
Cause analysis
KPI indices (Reliability, efficiency in closure of tickets)
Recurring trouble summary
Worst performing feeders/ devices
Crew assignments
Closed cases
3.2.5 Web Clients & Mobile Views
The Web-Based Solution offers an extended thin-client web-based application that allows users
to visualize, simulate, and manage their electrical systems remotely from the web.
This tool applies to Real-Time operations as well as analysis, and optimization. It provides the
user with a remote platform for executing “what-if” scenarios on existing operating conditions
and predicts system responses using analysis calculations. Users can monitor single or multiple
systems from a single web page; No software installation is required at the client machines.
Applications
Predictive “What-if” Simulation using exiting operating conditions
Remote Scenario Execution
Review Results on the One-Line Diagrams & Reports
System Monitoring & KPI Views
Geographical Power Distribution Views
Alarms & Events
Page 67 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 68 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 69 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 70 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 71 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
(d) Event Demand: shall allow the Instructor to demand the immediate execution of
an event.
(e) Event Omission: shall allow the Instructor to omit a scheduled event from the
training scenario in progress without interrupting the training scenario.
(f) Periodic Snapshot: shall allow the instructor to create a historical file that is
periodically updated with session data necessary to resume simulation as it occurs
during the simulation. The DTS shall not pause while the snapshots are being
collected and saved. The snapshot save area shall be circular in nature where the
oldest snapshot will be overwritten each time a new snapshot is saved when the
save area is full.
(g) Demand Snapshot: shall allow the Instructor to create a historical file, identical
to that created by a periodic snapshot, on demand during the simulation. The DTS
shall not pause while the snapshots are being collected and saved.
3.3.8 Post-session Activities
The DTS shall provide the following capabilities to assist the Instructor in reviewing a training
session with the Trainee:
(a) Snapshot Review: shall initialize the DTS with a snapshot saved during a training
session. After a snapshot has been loaded, the Trainee and Instructor shall be able
to call displays to examine any data available during a session.
(b) Snapshot Resume: shall resume the simulation from a snapshot in the same
manner as it would resume from a Pause.
(c) Evaluation report: Based on the actions performed, timeliness & an evaluation
report shall be created to review performance of trainee.
3.3.9 DTS Performance and Sizing
The DTS shall be sized the same in all respects as the SCADA/DMS control system. In
addition, the capabilities of the DTS shall include the following items as minimum:
(a) 20 DTS base cases
(b) 20 scenarios
(c) 250 event groups
(d) 50 events per group
(e) 50 session snapshots
(f) 5-minute snapshot periodicity
(g) 100 conditional events
(h) 1000 variables in conditional events.
(i) 2 Trainee (according to no. of DTS consoles) & 1 instructor
3.3.10 DTS Database and Displays
The DTS SCADA and Network model database must have the same functionality & displays
as the real-time system database & displays. It must be possible to initialize the DTS with a
copy of the database of real-time system in addition creation of database locally.
End of Chapter 3
Page 72 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 73 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
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 each time a user attempts a console action, such as:
(a) Calling a display
(b) Entering or changing display data
(c) Viewing, editing, or printing a report
(d) Executing a supervisory control action
There shall be no restrictions on the assignment of multiple jurisdictions to a console & user
or the assignment of a jurisdiction to multiple consoles & users. The access security function
shall ensure that each jurisdiction is at all times assigned to a least one console. If a console
failure or manual reassignment of jurisdiction results in one or more jurisdictions not being
assigned to at least one console, the unassigned jurisdictions shall be automatically assigned
to a pre- assigned default console and suitable alarms shall be generated.
SCADA/DMS users shall not require additional login (user name and password) to the other
facility allowed as per operating jurisdictions such as ISR. “Single Sign-On” (SSO) technology
be employed (i.e., a user logs on once to the SCADA/DMS using individually defined user
name and password which permits appropriate level of access to all SCADA/DMS facilities,
including IS&R. Further, the facility should be compatible with enterprise-wide SSO
capabilities.
Each log-on and log-off shall be reported as an event. Unsuccessful attempts to log-on shall
also be reported as events.
4.3 Windows Environment
The user interface for SCADA/DMS system shall be web enabled. The SCADA/DMS system
displays shall operate within a windows environment and shall conform to the standards
contained in the X Consortium's Inter-Client Communications Conventions Manual (ICCCM).
The window system shall work with the graphical user interface provided and shall allow
windows created on the workstations to communicate with processors equipped with X
Windows- compatible software on their respective local area networks (LANs) and with future
remote applications over the wide area network (WAN).
Alternatively, 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 met by available features of Microsoft Windows.
It shall be possible to save window configuration in Rooms. Rooms shall allow each user to
configure 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 user shall 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.
The user interface software shall be based on state-of-the-art web-based technology to present
interactive, full-graphics views of system data via LAN, corporate intranet or the internet. The
same displays shall be used.
It is essential that the same web-based user interface (same navigator, same tools) be available
to the operator either for local use in the dispatching center or remotely.
Page 74 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Real-Time Dynamic Graphics and HMI Solutions for C/C++, C# / NET, Java and Web /
Mobile is envisaged.
The web technology shall be natively supported by the SCADA & DMS product, which means
that having the displays shown in the web browser shall not bring additional work to the
maintenance engineer at display building time. Nor shall it require additional third-party
software products like specific plug-ins.
C/C++, Java and C# .NET libraries for a variety of Windows, Linux/Unix and embedded
platforms, with MFC, Qt and Gtk support. z Cross-platform support for a run-time choice of
a graphics driver: hardware-accelerated OpenGL or a native GDI. z Web deployment via a
client-side HTML5 and JavaScript, or server-side (ASP.NET or JSP. Supported platforms:
Windows, Linux, Solaris, AIX, HPUX etc
A vast collection of pre-built widgets - real-time charts, graphs, dials, meters, process control
symbols and others – to be provided with the Toolkit. The Graphics Builder may be used to
modify widget drawings, create dashboards containing multiple widgets, as well as design
custom widgets and add them to the Builder’s palettes.
The web user interface shall support and enforce all security features including cyber security
compliances.
4.4 Display interactions
Rapid, convenient, and reliable display requests shall be provided using the following
methods:
4.4.1 Display Requests
a) Selection of a display from a menu display
b) Cursor target selection on any menu, graphic, or tabular display
c) Selection of an alarm : in this case, it shall call up the one-line display containing
the alarm’s location,
d) Selection of an alarm or event message on a summary display followed by a display
request command
e) Selection of display by Entering a display name or number
f) Forward and reverse paging in a page-based display.
g) Selecting a previous display by re-call command.
h) 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).
i) Selecting function keys or cursor targets dedicated to displays.
4.4.2 Display navigation
Display navigation methods shall provide a consistent approach for moving within a
display. The following methods shall be provided:
a) Panning with cursor positioning device or scroll bars
b) Zooming with cursor positioning device
c) Navigation window for rapid movement between portions of a world display
d) Rubber-band zooming.
Page 75 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
e) Tool tip
f) Find & locate
g) Drag & drop
Zooming shall affect the magnification level of the data displayed. Panning shall move the
viewed portion of a world map space. The size of the viewed portion of the map relative to the
whole display shall be indicated by the width of the sliders in the scroll bars of the window
displaying the sector. When a display is first called up in a window, it shall be automatically
scaled as per default zoom level.
Both continuous and discrete panning and zooming control shall be provided. Continuous
panning and zooming shall be done in a convenient and intuitive way using the mouse; and
the resulting changes in the screen contents shall be “smooth” and instantaneous without any
noticeable delay. Discrete panning and zooming in larger steps shall be possible by dragging
the mouse, using the keyboard, and clicking on pushbuttons on toolbars.
When only a part of the display is shown in the active window, the user shall be able to request
a “navigation” window for orientation. This window shall show a small replica of the complete
display, with the displayed sector of the display highlighted. The user shall be able to move
the navigation window anywhere on the screen, and shall be able to close it.
A decluttering mechanism that defines the visibility of a graphic construct as a function of its
magnification shall be provided. As zooming changes the magnification of data displayed, the
declutter mechanism shall cause levels of detail to be shown or suppressed.
The magnification range corresponding to each declutter level shall be defined as system
configuration parameter. Static and dynamic element within a display shall have associated
with it a visibility designation as yes or no for each
In addition to reaching the various decluttering levels through zooming, users shall also be
allowed to request a specific level from a dialog menu.
The user shall be able to scale (zoom) the image of a world co-ordinate space or display in a
smooth fashion to any convenient scale factor. The scale factors shall allow the presentation
of an entire world co-ordinate space or display on the full screen or a window.
Static and dynamic data shall be displayed and updated during a scaling operation, and display
text shall be scalable to be consistent with the scaled image. At defined scale factors, levels of
de-clutter shall be invoked.
The user shall be able to select an area of a world co-ordinate display by cursor manipulation
(“rubber-banding”) and cause the display to be redrawn with the selected area centered in the
display and with the selected area magnified to best fit the full window. The window
dimensions shall not be changed by such an action.
A tool tip or equivalent method shall be provided for displaying information in English text &
numeral upon moving cursor on the device etc.
Find & locate feature to take the user to the online/ network display where the particular
component exists.
4.4.3 Permanent Indicators
Several indicators, including those listed below, shall be permanently shown on each
SCADA/DMS Display screen as minimum:
Date and Time: Date shall be presented in the format DD/MM/YY.
Page 76 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 77 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
As appropriate for the data and function requested, a menu containing output destinations such
as screen, printer, or file shall be presented. When the destination is selected by the user, the
requested action shall begin. It shall not be necessary to select an execute command to
complete the interaction except for supervisory control actions.
The user shall be able to end the interaction sequence at any time by selecting a cancel
command. The progress of all user operations shall be monitored. If the user does not complete
to a step within a multi-step operation within a pre-defined time, the process shall reset, and
the user shall be informed of the reset. A partially completed action shall be reset if the user
begins another non-related sequence.
A programmer-adjustable time-out cancel shall also be provided.
4.5.1 User Guidance
The SCADA/DMS system shall respond to all user input actions indicating whether the action
was accepted, was not accepted, or is pending. For multi-step procedures, the systems shall
provide feedback at each step. User guidance messages shall be English text and shall not
require the use of a reference document for interpretation. User shall be guided for multiple
options. The use of mnemonics is prohibited, unless the mnemonics are industry-accepted or
approved by employer. Provisions are required for administrators to edit the toolbars and
menus, user guidance messages and to construct new ones through an interactive procedure
and without programming.
4.5.2 User Help
In addition to the user guidance, general and specific context-sensitive on-line help shall be
available to the SCADA/DMS user. Context sensitive means that the help informationprovided
shall be applicable to the next step or steps in the sequence being performed. The Help menu
shall present a list of topics available for reference. The topics shall refer to the SCADA/DMS
user documents. The ability to scroll through the topic’s explanatory text shallbe supported.
The Help button in a dialog box and help key shall present the text of the user documents
where use of the dialog box is explained. The user shall be able to scroll through this text. Exit
from the help facility shall return the user to the same point in the sequence for which help
was requested.
Context sensitive help facilities shall be provided for each application software package and
operator display. The capability to easily edit or add additional help facilities in the future shall
be provided.
The provided help facility shall also support:
Search mechanism
Navigation links between related topics within the help
documents
select/copy mechanism
Print facilities
4.5.3 Overlapping user access
The 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 such as data entry and supervisory control as follows:
Page 78 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
(a) Data Entry: Although the same data entry field, device status entry or
fields (in the case of 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 user guidance message. Concurrent data entryon different
areas of a world display, however, shall be allowed.
b) Supervisory Control: Although the same power system device, such asa
circuit breaker, may appear concurrently in multiple windows at
multiple consoles, control of the power system device shall be
restricted to one window at a console at a time. An attempt to initiate
control of the power system device from another window shall result
in a user guidance message.
4.5.4 Function Key Usage
Special functions shall be assigned to the 12 function keys on a standard keyboard. With
extensions (e.g., Shift, Alt, Esc) this shall result in a minimum of 48 function key actions.
4.6 Trend
Trend shall be a display of series of values of parameters on a time axis. Both graphical trend
and tabular trends shall be supported. The attributes of the trend display shall be user
configurable. The trend application shall be able to show trends for any measurement type
from more than one source, at least from real- time, historical and forecast sources. It shall
be possible to combine this data showing data for comparison using a shared timeline
simultaneously comparing for example yesterday (historic) and today (historic, actual and
forecast) as two curves on the same time axis. It should be possible to trend different types of
parameters (P, Q, V, I, F etc.) with associated Scales on the same display. The user shall be
able to select a trend rate different than the sampling rate.
4.6.1 Graphical Trend
The user shall be able to select and configure trending on Graphical displays enabling user for
entry of the following parameters:
(a) Data value name
(b) Trend header
(c) Trend direction (horizontal or vertical)
(d) Scale (unidirectional and bi-directional)
(e) Zero offset
(f) Trace number, color & texture
(g) Trend data rate
(h) Trend start time and date (historical data only)
(i) Total trend duration (historical data only)
(j) Reference lines or shading axes (With default to restrictive alarm
limits)
(k) Windows/chart to be used
Page 79 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Each alarm shall be subjected to a series of alarm processing functions. A device or value's
alarmable conditions shall be assigned to an alarm category and alarm priority levels. Alarms
Page 80 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
shall also be subjected to advanced alarm processing. The results of the alarm processing shall
determine the console(s) that will receive and be authorized to respond to the alarm and the
associated actions with the alarm.
All alarm messages shall be recorded on auxiliary memory of SCADA/DMS system and
archived in chronological order & reverse chronological order. It shall be possible to sort,
display and print user selected alarm messages from any console by the user.
4.7.1 Alarm Categories
An alarm category provides the logical interface that connects an alarm condition to a specific
Area of Responsibility (AOR) or operational jurisdiction as defined and accordingly alarm
shall be reported to user. Every alarm shall be assignable to a category. Each category shall,
in turn, be assignable to one or more users. A means shall be provided for changing operating
shifts without reassignment of alarm categories at a console. Each log-on and log-off shall be
reported as an event.
4.7.2 Alarm Priority levels
Each alarm shall be assigned to an alarm priority level. Up to 8 alarms priority levels shall be
supported. Each alarm priority level shall be presented in separate display. For each alarm, it
shall be possible for the programmer to independently configure the following actions:
(a) Audible alarm tone type selection and its enabling/disabling
(b) Alarm messages to be displayed on an alarm summary
(c) Alarm message deleted from alarm summary when acknowledged
(d) Alarm message deleted from alarm summary when return-to-
normal alarm occurs
(e) Alarm message deleted from alarm summary when return-to-
normal alarm is acknowledged
(f) Alarm message deleted by user action.
This assignment shall determine how the alarm will be presented, acknowledged, deleted, and
recorded.
4.7.3 User Interaction for Alarms
The User shall be able to perform the alarm interactions described below.
4.7.4 Alarm Inhibit/Enable
Inhibiting alarms for a value or device, including a complete RTU /FRTU/FPI or other data
source, shall cause all alarm processing of that value or device to be suspended. The action
shall be recorded in the event log. However, Scanning of the value or device shall continue
and the database shall be updated.
4.7.5 Alarm Acknowledgment
An alarm shall be acknowledged by selecting an alarm acknowledge command when the item
in alarm is selected on:
(a) Any display showing the item in alarm
(b) 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 under acknowledged &
Page 81 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 82 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
black & white and print preview. Also any of the available printers shall be selectable from
the print Menu.
4.10 Report Generation
The contractor shall be required to generate the Daily, Weekly, Monthly reports formats for
SCADA/DMS system. The report formats shall be finalized during detailed engineering stage.
The user shall be able to schedule periodic generation of reports, direct report to display, print
report, and archive report using report-scheduling display. The report scheduling display shall
enable entry of the following parameters, with default valuesprovided where appropriate:
(a) Report name
(b) Report destination (printer or archiving device)
(c) Time of the system should produce the report.
The user shall be able to examine and modify the contents of reports for the current period
and for previous report periods using displays. Any calculation associated with the revision
of data in a report shall be performed automatically after data entry has been completed.
The report review displays shall accommodate formatted report pages up to132 characters in
width and 66 lines in length and shall contain headings that correspond to the printed report
headings. For reports containing more columns or rows than the display, the system shall
include a means to view the entire report in a graphic format. The report view and editing
displays shall function with the initially supplied reports and all future reports added by
employer.
4.11 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. The
following operations shall be possible:
(a) Failover of each server
(b) Monitoring of servers, device, including workstations, RTUs, FRTUs,FPIs,
status & loading of WAN LANs etc.
(c) Monitoring of the processor resource, hard disk & LAN/WAN
Utilization
(d) Control & monitor of SCADA/DMS functions
4.12 Dynamic Data Presentation
It shall be possible to present any item in the database on any display. All supervisory control
and 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 dedicated screen
areas such as the display heading.
Only standard X Window system or Microsoft windows standard fonts shall be provided with
the SCADA/DMS. All fonts supplied shall be supported on the user interface devices and all
printers supplied with the system. The types of fonts to be used in a particular display shall
be selected at display definition time.
Status and data values shall be presented in the following formats as appropriate:
Page 83 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
(a) Numerical text that presents analogue values shall have the provision forthe
format definition of the text shall include the number of characters, number
of decimal places, and the use of positive /negative sign or flow direction
arrows, etc.
(b) Normally the telemetered MW/Mvar values along with the sign/direction
shall be displayed on the Single line diagram and Network diagram.
However the user shall also be able to display all other telemetered and
calculated/ estimated analog values (I, V, pf etc. for each phase) on the
Single line diagram (SLD) and Network diagram.
(c) Symbols, including alphanumeric text strings for an item, based upon state
changes e.g., circuit breaker (OPEN/CLOSE/ INVALID).
(d) Symbols, including alphanumeric text strings for indicating the data quality
flags.
(e) Colors, textures and blink conditions based upon state or value changes or a
change of data quality, e.g., alarm limits.
4.13 Element Highlighting
Element highlighting techniques shall be provided to draw the attention of Dispatcher to
critical state of the system. The highlighting technique shall include change of color, color
intensity, blinking, Character inversion, Line texture, appended symbols etc. This feature shall
be used to highlight alarms, power system device and measurement status, data quality, data
entry locations on a display and error conditions.
4.14 Display Types
The following indicative list describes the types of displays that are to be included in the
SCADA/DMS system. The user interface shall support the capabilities of all displays as
specified. The User mode, Current Time and date shall be displayed on a screen-basis, not on
a display basis, and shall be always visible.
4.14.1 Dashboard
A suitable dashboard for utility to view vital parameters at a glance shall be created.
4.14.2 SCADA/DMS System Display
A display shall be provided that lists all SCADA/DMS system directory displays. The displays
shall be listed in alphabetical order with suitable separation in the list to enhance readability.
Each entry in the list shall have a cursor target for display selection.
4.14.3 Distribution System Network Display
A graphic overview network display of the distribution system with substations, feeders.
Distribution network color coded by voltage shall be provided. This display shall present the
distribution system in a graphic format provided by employer. Telemetered and calculated
data like Real and reactive power flows shall be displayed as a value with a direction. Lines
that have exceeded their loading limits shall be highlighted. Substationsand power stations
shall be depicted by symbols that reflect the presence of alarms at that substation or power
station. Cursor selection of a substation/ power station symbol shall result in the associated
Single line diagram display for that substation/ power station.
Page 84 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 85 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 86 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
graphical form. The user shall be able to Enable/Disable any communication channel from this
display. Such actions shall be recorded with User ID details
4.14.22 SCADA/DMS Application Program Displays
Application program displays shall be provided to satisfy the user interface requirements of
the system functions stated throughout this Specification. Application program displays shall
be based on a standard user interface design across all applications to provide a common look
and feel. The application's information shall be presented in such a way as to facilitate user
operations.
The required displays for all DMS Applications, as defined in Chapter 2 shall also be made
available to the user.
4.14.23 SAIDI/SAIFI displays
There shall be suitable displays to visualize SAIDI /SAIFI (Planned, unplanned & total ) feeder
wise, Substation wise , Town wise, Distt. wise or any another logical boundary mentioned by
utility on daily, weekly, month, quarterly, FY , Yearly basis with comparison with past years
through suitable navigation
4.14.24 SLA monitoring displays
The display shall capture and maintain record and display historical and current values as per
requirement of monitoring of SLA as per chapter 17
4.14.25 Help Displays
Help displays shall be provided to aid the user in interpreting displayed information and to
guide the user through a data entry or control procedure. Help displays shall be provided for
each display that is provided with the system. Each display shall have a prominent cursor target
that the user can select to request the associated help display. For standard displays, software
aids (such as context sensitivity) shall be used to present pertinent help information in an
expeditious manner. A programmer shall be allowed to modify and create help displays.
Further,e SCADA/DMS dynamic distribution network with GIS land base at the back ground
shall be available for navigation. Operator shall be able to perform all functions & have
features as envisaged in the specification. Suitable GIS adaptor shall be provided to import the
distribution network model & GIS information from GIS system. Refer other GIS details as
mentioned in chapter 1 &2 of this section.
End of Chapter 4
Page 87 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
5.0 General
This chapter describes the characteristics of system software such as Operating system,
RDBMS and support software (programming language compilers, database development and
maintenance, display development, network services, report generation, diagnostics and
backup utilities) to be provided by Contractor and the original software manufacturer as
necessary to support the SCADA/DMS/OMS/RT-DAS applications. This chapter also
describes the standards to be followed for all supplied software. It is necessary that functional,
availability & performance aspects are met. Bidder shall assess the adequacy of software
specified & if any additional software is required to meet all the requirements of the technical
specifications, the same shall also be included in the offer. This chapter is applicable to Group
A,B,C towns as per functional requirements
5.1 Software Standards
All SCADA/DMS software provided by the Contractor, including the Operating system,
RDBMS and support software, shall comply with the industry-accepted software standards
produced by national and international organizations, such as ANSI, ISO, IEC, IEEE, ECMA
in order to facilitate maintenance and enhancement of the SCADA/DMS systems being
supplied. In areas where these organizations have not yet set standards, the software shall
comply with those widely accepted de- facto standards put forth by industry consortiums,such
as OSF and X/Open or equivalent. The Contractor shall commit to meet the "open systems"
objective promoted by industry standards groups by using software products that arebased on
open standards.
5.1.1 Design and Coding Standards for SCADA/DMS applications
All SCADA/DMS applications shall be maintainable by employer using the supplied software
utilities and documentation. The SCADA/DMS software design and coding standards shall
also address the following:
(a) Expansion/ scalability: software shall be dimensioned to accommodate the
ultimate size of SCADA/DMS system envisaged.
(b) Modularity: software shall be modular to minimize the time and
complexity involved in making a change to a program.
(c) User-Directed Termination: Functions taking long execution times shall
recognize and process user requests to abort the processing.
(d) 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 based systems the APIs shall be POSIX- conforming.
(e) SOA architecture: Software shall conform to SOA.
(f) Enterprise service bus (ESB): ESB based architecture is essential toenable
interaction of applications from different product manufacturer, platforms
etc.
(g) Portability & Interoperability: The software shall be designed for hardware
independence and operation in a network environment that includes
dissimilar hardware platforms to the extent possible. The use of system
Page 88 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 89 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
(a) Network file management and transfer, for files containing text, data,
and/or graphics information
(b) Network printing management
(c) Network time synchronization
(d) Network backup over LAN
(e) Task-to-task communications to external computers
(f) LAN global naming facilities.
(g) Remote procedure call
(h) Remote terminal session
5.4.4 Security Services
The security solution shall comprise of comprehensive solution for secured zone Firewalls i..e
LAN Firewall & Gateway Firewall, intrusion Prevention system IPS (Network based & Host
based) & Strong Authentication (multi layered), LDAP , Encryption mechanism. The
contractor shall provide a tightly integrated intrusion detection system to detect and prevent
intrusion
Followings are the functional requirement from the security system:
• System shall have Multilayer (at least network, application layer ) firewall
which shall protect the complete system network from unwanted users.
Further the separate firewall of different OEMs shall be provided to take
care the security of all the servers & shall have High Availability
architecture with No Single Point of Failure (NSPOF).
• Gateway Firewall should be capable of load balancing multiple links from
different service providers.
• LAN Firewall shall provide isolation/security services between the
subsystems installed under SCADA system
• Firewalls deployed should not become a bottleneck. It shall be Robust,
Secure, Scalable and future-proof with Centralized Management.
• Two type of IPS Host based & Network based shall be deployed with
minimum hardware & they should not go blind in peak traffics.
• IPS should have hybrid technology to detect attacks. It should detectthrough
a combination of Protocol Anomaly and Signature matching.
• Shall have Gateway antivirus which will protect from inflow of virus from
the Internet and other WAN locations at the gateway itself with content
filtering without any lag in data transmission.
• Shall have strong authentication containing user name and passwords which
shall be very difficult to compromise.
• SSL over VPN to provide secured link over public network such as with
RTU/FRTU/FPI
5.4.5 Features
Followings are the features specific to each component of security system
5.4.5.1 Firewall
Page 90 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
The Firewall shall be hardware box Firewall system with following features.
• Firewall speed >250 Mbps
• Data encryption supported DES (56 bits) 3 DES (168 bits) and hashing
algorithm like MD5 and SHA-1
• Encryption to offload the main CPU
• It shall have minimum 8 Ethernet 10/100 /1000 ports (4ports for
connectivity to two web servers & 4 Ports for connectivity to LAN
• Support NAT and PAT
• Capability of working in Load sharing and hot standby mode
• Denial of service prevention.
• DNS guard features
• JAVA and ActiveX blocking
• Radius integration
• Web based management interface
• Stateful inspection for web, mail, SQL application etc.
• Detailed system logging and accounting feature
• No. of concurrent TCP Sessions supported shall be more than 5000.
5.4.5.1.1 Intrusion Prevention System (IPS)
The contractor shall provide a tightly integrated intrusion detection & prevention system
Capable for detecting the intrusion attempt that may take place and intrusion in progress and
any that has taken place.
Both Network based and Host based IPS should have centralized Management Console system
which will be either the application server with NMS or any of the workstation. The
Centralized management console shall have integrated event database & reporting system &
it must be able to create and deploy new policies, collect and archive audit log for post event
analysis. The system shall have Integrated Event Database & Reporting System.
Automated Update of the signature for two years shall be provided and there should be
provision for creating customized signature
(A) Intrusion Prevention System (Network Based)
After detecting any intrusion attempt there should be provision to configure to perform the
following functions:
Capability for Detecting the intrusion attempt that may take place,
intrusion in progress and the intrusion that has taken place
Reconfigure the firewall provided in this package.
Send an SNMP Trap datagram to the management console.
The NMS server envisaged under the specification shall be used as
management console also.
Send an event to the event log.
Page 91 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 92 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 93 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 94 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 95 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
periodicity of 5 minutes.
(b) Maintain a graphical display of network connectivity to the remote end routers
(c) Maintain a graphical display for connectivity and status of servers and
peripheral devices for local area network.
(d) Issue alarms when error conditions or resource usage problems occur.
(e) Provide facilities to add and delete addresses and links, control data blocks,
and set data transmission and reception parameters.
(f) Provide facilities for path and routing control and queue space control.
(g.) SLA monitoring - Availability of all devices shall be monitored and SLA shall
be calculated as per SLA requirement specified in FMS chapter
5.4.6.7 Central Cyber security Monitoring & Detection
The Contractor shall implement a unified cyber security Application platform purpose built to
monitor, manage & maintain the security posture of the overall control system network. The
system shall establish mechanisms & processes for detection of cyber security threats, to ensure
cyber security threats or incidents can be responded promptly to. These shall include key
security technologies like central security policy management for host machines, capturing and
& analyzing security event logs from all security/networking assets and continuous threat
detection systems adopted for an operational technology environment.
The proposed deployment shall be based on a vendor agnostic platform, natively supporting
the said cyber security services, while offering flexibility and scalability to provide additional
functionalities needed in the context of security improvement plan.
The software platform shall be designed in conformance to key global standards like IEC 62443
and IEC 62351 while supporting compliance to the country specific guidelines/frameworks.
The central security management server shall be deployed in the De-Militarized zone inside the
control room segregated by suitable firewalls and shall act as an IT/OT interface
All hosts machines shall implement advanced end point protections including antimalware,
application whitelisting, data loss prevention, HIPS etc. The whitelisting and application
control shall allow only list of permitted applications, services and processes to run on each
host; no other processes shall be permitted to be executed on the host. It shall not be possible
for users to circumvent the malicious code protection on a host device.
The Host based IPS shall monitor the characteristics of a host and the events occurring within
that host for suspicious activity. The characteristics which need to be monitored include
network traffic, system logs, running processes, file access & modification, and system &
application configuration changes.
The central policy Orchestrator shall be deployed to enable operators/security administrators to
centrally monitor and manage the security policy for all host workstations. The application shall
allow creation of automated workflows, support creation of reports, customized dashboards to
analyze the performance of each security setting while tracking the deployment of signature
(DAT files) updates date from a single location.
Continuous (24/7) anomaly & threat detection shall be implemented to detect and alert for all
known & unknown threats including Zero days, MITM attacks, DDoS attacks, unauthorized
behavior or malicious activities on the network. The system shall support a wide range of IT &
OT communication protocols including the proprietary protocols, and able to discover
information from the network passively using Deep Packet Inspection by connecting to the
Page 96 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Page 97 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
The standard operating system shall support the monitoring of security on host installed
applications. The system shall support or allow the creation of monitoring for:
Application Software Error Conditions
Application Software Performance Issues
Application Configuration Changes
Authentication activities - login, logout, failure access
Host Security Monitoring:
Security policy changes.
Anti-malware activities - alerts provided by antivirus or whitelist
solutions
Mobile drive activities - USB connection in the system
Windows event logs from Windows Machine System - Windows
patches and activities,
Network monitoring alerts and events:
Configuration update activities - settings and parameters changes in
systems
Unauthorized access attempts events from Security appliances
Application must be simple and intuitive to support OT operators with limited IT skills to
quickly identity the security issues or any unauthorized access to the system and respond to it
before it becomes a major threat to the system. Employer’s personnel shall be trained to be
capable of creating new custom analysis and reports.
The contractor shall propose a centralized patch management solution to securely execute and
manage all necessary systems, security mitigation and signature-related patching in timely
manner. All host machines shall be configured via domain policy to contact patch servers and
check for missing updates. These updates shall be installed manually to avoid cause
unscheduled disruptions.
All the security appliances (Firewalls, Antivirus, central cyber security monitoring & detection
appliances etc) being supplied under this project shall have definition updates for
virus/signatures and updates for software patches for the warranty and complete FMS period.
The signature and patches shall then be deployed to all the respective devices. These
enhancements shall increase security and functionality, without requiring redesigning or
reengineering efforts.
5.5 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 shall describe the state of
the power system at a given point in time and the events that move the system to a new state
at the next point in time. This database is required to support the data access to real time
information and to allow efficient integration and update.
A library of event routines may encapsulate or interface the RTDB with other components of
the system. These event routines shall be the preferred means for application programs to
Page 98 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
interact with RTDB. This way, application programs (and programmers) only need to concern
themselves with callable interface (API) of these routines. Each application shall interact with
the RTDB through the event library. These event routines shall serve as generic APIs for
database access thereby eliminating proprietary database function calls at the application level.
The SCADA/DMS shall include a single logical repository for all data needed to model the
historical, current, and future state of the power system and SCADA/DMS – the Source
Database (SDB). All information needed to describe the models on which the SCADA/DMS
operates, shall be defined once in the SDB and made available to all SCADA/DMS
applications, real-time database, and user interface maintenance tools that need the
information.
Any database update, whether due to local changes or imported network model changes, shall
be able to be placed online in a controlled manner without causing undue interruption to
network operations, including without losing any manually entered data. For example, a
network model update to introduce a new substation shall not interrupt the ability to perform
supervisory control actions or receive telemetry to view the network state. It shall be possible
the changes, local or imported, to be placed online either automatically or under manual control
with proper validation. It shall be possible to easily revert to an earlier databaseVersion, again
without undue interruption to network operations.
The capability to import & export the CIM compliant network model data including the
corresponding telemetry and ICCP data reference in XML format to send it to other parties
shall be provided. The capability to import the CIM compliant network model data from other
parties in XML format shall also be provided.
The SCADA/DMS shall provide a consistent interface to accept XML format data for updates
from other database applications; and provide a consistent interface to import & export data in
XML format.
5.5.1 Software Maintenance and Development Tools
5.5.1.1 General requirements
A set of software shall be provided to enable maintenance of application software and
development of new software in software development mode.
All hardware and software facilities shall be provided to allow creation, modification and
debugging of programs in all languages that are supplied.
The following shall thus be possible:
Program and data editing
Program compiling and assembling
Linking
Loading, executing and debugging program. Version management
Concurrent development
The following features shall be provided:
Library management
Programs allowing to copy and print any data or program file
Backup and restore File comparison Sort and merge
Page 99 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
The database development function shall locate, order, retrieve, update, insert, and delete data;
ensure database integrity; and provide for backup and recovery of database files. The database
development function shall generate and modify all SCADA/DMS data by interfacing with all
database structures. The location of database items shall be transparent to the user
After 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 server
shall be archived such that it is available to replace the new database upon demand. The
archived database shall be deleted only when directed by the user.
Newly generated run-time databases shall only be placed on-line by user command. Following
the assignment of a new database to a server and on user demand, the database management
software shall access each SCADA/DMS server to ensure that all databases are consistent.
Inconsistencies shall be annunciated to the user.
5.6.1.3 On-Line Database Editing
Selected database management functions and changes to a run-time database shall be possible
without requiring a database generation. These shall be limited to viewing functions and
changes to the contents, but not the structure of the database. On-line changes shall be
implemented in all applicable SCADA/DMS run-time databases without system downtime.
Changes shall also be implemented in the global database to ensure that the changes are not
lost if a database regeneration is performed. On-line database editing shall not affect the
SCADA/DMS system's reaction to hardware and software failures nor shall it require
suspension of exchange of data among servers for backup purposes.
5.6.1.4 Tracking Database Changes
The 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 at least last 2 months shall be maintained
and another audit trail maintaining records of who/when performed the edit operation shall be
maintained for a period atleast 2 months.
5.6.1.5 Initial Database Generation
The initial database shall contain all data required by the SCADA/DMS systems. Default
values shall be used in consultation with the employer for data that is not provided by
employer. Population and maintenance of the distribution network model should be possible
by using the database maintenance tools to build the database from scratch.
5.7 Display Generation and Management
SCADA/DMS displays shall be generated and edited using interactive display generation
software delivered with the system. The display generator shall be available on development
system & once the display/ displays creation/ modification activity is complete, the compiled
runtime executable shall be downloaded on all workstations/servers.
The display editor shall support the important construction options like:
Copy/move/delete/modify,
Building at different zoom level,
Linking of any defined graphics symbol to any database point,
Pop-up menus,
Protection of any data field on any display against user entry
based on log- on
identifiers
Activation of new or modified displays for any application or
across all applications of the system by a simple command that
The display generator shall support the construction of display segments consisting of
symbols, primitives, and dynamic linkages to the database and user interface. Typical uses of
display segments are pull-down menus, bar charts, and common circuit breaker
representations. The display generator shall be able to save display segments in segment
libraries for later use. The SCADA/DMS system shall include a base library of segments
commonly used by display builders.
The display generator shall support the addition, deletion, and modification of segments,
including the merging of one segment with another to create a new segment. Segment size
shall not be limited. Segments shall be defined at an arbitrary scale factor selected by the
user.
5.7.1.2 Dynamic Transformation Linkages
Dynamic transformations shall be performed on symbols and display segments based upon
dynamic linkages to database variables. All linkages to the database shall be defined via
symbolic point names. Each symbol or segment stored in a library shall include its dynamic
transformation linkages, although the specific point names shall be excluded. Dynamic
transformation linkages shall support the dynamic data presentation
Executing the report generating functions shall not interfere in any server of the system with
the on-line SCADA/DMS functions.
5.9 System Generation and Build
System generation includes the activity of generating an executable object code of all
databases, displays, and reports as required for SCADA/DMS system. System build is the
process under which all the above executable and the executable provided for SCADA/DMS
application software are ported to the SCADA/DMS system hardware and configuring to make
it operational.
The contractor shall do the complete system generation and build as required for successful
operation of the SCADA/DMS system. The contractor shall also provide the complete backup
of the SCADA/DMS system in electronic media such as tapes, CDs, MO disks etc.
Employer personnel shall be able to restore the SCADA/DMS system at site by using above
backup tapes/CDs etc. The contractor shall provide the procedures necessary to restore the
system from the backup tapes/CDs etc. The DR system shall always have updated set of system
build. It shall be synchronized with the SCADA/DMS control center .
5.10 Software Utilities
All software utilities used to maintain SCADA/DMS software, whether or not specifically
required by this Specification, shall be delivered with the system.
The software utilities shall operate on-line (in background mode) without jeopardizing other
SCADA/DMS application functions that is running concurrently. This utility software shall
be accessible from workstations, programming terminals, and command files on auxiliary
memory. Multiple users shall have concurrent access to a utility program task, provided there
are no conflicts in the use of peripheral devices.
5.10.1 File Management Utility
File 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 on
auxiliary memory and archive storage.
5.10.2 Auxiliary Memory Backup Utility
A utility to backup auxiliary memory of server and workstation files onto a user- selected
auxiliary memory or archive device shall be supplied. The backup utility shall allow for user
selection 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 can backup all server and workstation auxiliary memories on to a single
target auxiliary memory or archive device shall be provided. The backup utility must ensure
that the source auxiliary memory files are captured properly regardless of caching activity.
status data for analyzing the cause of a fatal program failure. The failure information shall be
presented in a condensed, user-oriented format to help the user find the source of the failure.
The information shall be presented on displays and recorded for historical records and user-
requested printed reports.
5.10.4 Diagnostic Utility
The system shall have suitable auto diagnostic feature, on line & offline diagnostic Utility for
on-line and off-line monitoring for equipments of SCADA/DMS system shall be provided.
5.10.5 System utilization Monitoring Utility
Software utility shall be provided in each server and workstation to monitor hardware and
software resource utilization continuously and gather statistics. The monitoring shall occur in
real-time with a minimum of interference to the normal SCADA/DMS functions. The period
over which the statistics are gathered shall be adjustable by the user, and the accumulated
statistics shall be reset at the start of each period. The statistics shall be available for printout
and display after each period and on demand during the period.
5.10.6 Other Utility Services
On line access to user and system manuals for all software/Hardware products (e.g., Operating
System and Relational Database Software/hardware) and SCADA/DMS applications shall be
provided with computer system.
End of Chapter 5
6.0 Introduction
This chapter articulates the hardware requirements for the SCADA/DMS system. The
conceptual hardware configuration diagram of SCADA/DMS control center is indicated in
Figure-1 of chapter 1. The bidders are encouraged to optimize the hardware for servers where
SCADA, DMS & ISR applications can be combined or distributed in any combination with
adequate redundancy. However, quantity of servers shall be as per detailedbill of quantities
for SCADA/DMS defined in chapter 19. Bidder shall assess the adequacy of hardware
specified in the BOQ & if any additional hardware is required to meet all the requirements of
the technical specifications, the same shall also be included in the offer. TheBidder shall offer
the minimum hardware configuration as specified here for various equipment, however if
required, higher end hardware configurations shall be offered to meet all the requirements of
the technical specification. The redundant hardware such as servers (Except DTS,
development server) , CFE, etc. shall work in hot standby manner. It is necessary to ensure
that the functional requirements, availability & performance aspects are met as per
SCADA/DMS system specification. This chapter is applicable to Group A,B,C, Utowns as
per functional requirements
6.1 General Requirements for Hardware
All hardware shall be manufactured, fabricated, assembled, finished, and documented with
workmanship of the highest production quality and shall conform to all applicable quality
control standards of the original manufacturer and the Contractor. All hardware components
shall be new and suitable for the purposes specified. All hardware such as computers,
computer peripherals/accessories etc. and networking products proposed and implemented
shall conform to latest products based on industry standard. All hardware shall be of reputed
make.
All servers and workstations shall include self-diagnostic features. On interruption of power
they shall resume operation when power is restored without corruption of any applications.
The hardware shall be CE/FCC or equivalent international standard compliance. The
specification contains minimum hardware requirement. However, the contractor shall provide
hardware with configuration equal or above to meet the technical functional & performance
requirement. Any hardware /software that is required to meet functional, performance &
availability requirement shall be provided by Contractor & the same shall be mentioned in the
BOQ at the time of bid . If not mentioned at the time of bid, contractor shall provide the same
without any additional cost to the owner The proposed system shall be designed for an open
& scalable configuration, to ensure the inter-compatibility with other systems of the Utility,
the future smooth expansion as well as the easy maintainability. The proposed hardware
configuration should be extended by adding either CPU processors / memory boards / disks
etc.in delivered units or additional units for capacity extension.
The configuration of the SCADA/DMS shall comprise a distributed computing environment
with an open systems architecture. The system architecture shall be open internally and
externally to hardware or application software additions, whether supplied by the original
supplier of the SCADA/DMS or obtained from third party vendors, both for capacity
expansion and for upgrading functionality, without affecting existing SCADA/DMS
components or operation.
To be recognized as a true open computer system, all internal communications among the
SCADA/DMS Servers and all external communications between the SCADA/DMS and other
computer systems shall be based on widely accepted and published international or industry
standards which are appropriate and relevant to the open systems concept or should have a
field proven acceptance among utilities. This applies to the operating system, database
management system, and display management system, as well as to APIs providing
standardized interfacing between System software and application software.
The contractor should ensure that at the time of final approval of hardware
configuration/BOQ, all the above hardware are current industry standard models and that the
equipment manufacturer has not established a date for termination of its production for said
products. Any hardware changes proposed after contract agreement shall be subject to the
following: -
a) Such changes/updates shall be proposed and approval obtained from Employer
along with the approval of Drawings/documents.
b) The proposed equipment shall be equivalent or with better features than the
equipment offered in the Contract.
c) Complete justification along with a comparative statement showing the original
and the proposed hardware features/parameters including technical brochures
shall be submitted to the Employer for review and approval.
d) Changes/updates proposed will be at no additional cost to the Employer.
6.2 Hardware Configuration
In this technical specification all hardware has been broadly classified as server and Peripheral
device. The term "server" is defined as any general-purpose computing facility usedfor hosting
SCADA, DMS & ISR application functions as defined in the specification. The servers
typically serve as the centralized source of data, displays and reports. The term “Peripheral
Device” is used for all equipment other than servers. Peripheral device includes Operator
Workstations, WAN router, LAN, Printer, Time and Frequency system, External Auto loader,
External Cartridge Magnetic tape drive, VPS, RTU/FRTU etc.
6.2.1 Servers
The OEM of servers shall be member of TPC/SPECMARK. can be broadly classified into
the following categories:
A) Application server
SCADA
DMS (Group A /UONLY)
OMS (Group A/U ONLY)
ISR
NMS
Web server
B) Communication server
Front –End server (Communication Front End) FEP(CFE)
ICCP /Inter control center communication server
Storage Array
Controller Cache: 512 MB per controller standard
Integrated RAID controller with an LCD/LED status display
and 256 MB
read/write battery-backed cache (expandable to 512 MB per
controller).
Host Interface: Fiber Channel connection per controller from
the host side
Host Ports per Controller: Dual 2 Gb/s RAID Levels
(EXCEPT RAID 0)
Redundant Controller: Yes
Redundant Web / Active Directory Services Server shall host Web Applications for
SCADA/DMS LAN and the DNS configuration
Redundant NMS server shall be provided to host NMS application
6.2.1.2 Communication Servers:
6.2.1.2.1 FEP ( CFE) Server
The redundant FEP server shall be a functional unit that offloads the task of communication
& pre-processing between RTUs/FRTUS/FPIs & SCADA/DMS servers. All
RTUs/FRTUs/FPIs shall be connected to CFE through IEC 60870-5-104/101 link.. For any
existing RTUs/FRTU/FPI that are to be integrated, interface must be available to use existing
protocols. Free slots shall be made available inside the FEP server, so as additional
communication boards can be plugged-in to meet the network future expansion. Each channel
shall be assigned a different protocol and the front-end shall be able to manage several
protocols in parallel.
The redundancy of front-end servers shall allow handling of RTUs/FRTUs/FPIs connected
either through single channel or redundant channels. In both cases, one FEP server shall be able
to take control of all RTUs/FRTUs/FPIs channels. In order to meet network’s expansion
behind the full capacity of a pair of FE servers, it shall be possible to connect additional FE
servers’ pairs to the LANs. Each communication line shall be able to support its own
communication protocol. The CFE shall comply VPN / SSL based security for connecting
with IEC 60870-5-104 &101 nodes on public networks. Further the nodes and CFE shall be
self-certified by manufacturers as NERC/CIP compliant to comply with future smart grid
requirements.
All FEPs shall not have open ports other than needed for protocol traffic / SCADA traffic, and
shall have an audit trace of all login attempts / connection attempts. This FEP shall exchange
data through secured SSL / VPN and encryption of protocol traffic whether it is a is public
network or a dedicated one. The equipment should take control command from designated
Master IP address only and no other IP.
All RTU/FRTU/FPI shall be connected to the SCADA/DMS Control Center.
RTU Communication Card / Module shall support VPN / SSL Security / Encryption of data
coming to it through Public network, and then send over private & secure Utility network to the
SCADA Control Center.
The Communication Servers shall be able to process time – stamped data and can be directly
connected to GPS device for time synchronization
6.2.1.2.2 ICCP Server /inter control center communication server
Depending upon the protocol i.e ICCP o other intercontrol center protocol used as permissible
as per this specification for , the server shall be called as ICCP or inter control center
communication server. The redundant ICCP//inter control center communication server
servers shall be installed at each SCADA/DMS control centers of eligible towns of the state
and DR center & shall be used to retrieve, transmit and process data to and from remote
sources i.e. remote control centers. Data retrieved and processed from remote sources maybe
stored in communication servers, which then distributes the data to other servers periodically
or on demand. The server may also be used by utility to exchange data with StateLoad Dispatch
Centers (SLDC) of the state where scheme will be implemented for exchange of scheduling
data.
6.2.1.2.3 Network Management System (NMS) Servers
Redundant NMS servers shall be used for configuration management, fault management &
performance monitoring of servers, workstations, routers & LAN equipments etc. Part of the
above functions may be performed by other servers as per the standard design of offered
product.
6.2.1.2.4 Web servers with Active directory:
Redundant Web servers with active directory LDAP, DNS shall be provided.
6.2.1.3 Demilitarized/ Security servers
6.2.1.3.1 Web servers with Firewalls and IPS:
Redundant Web servers shall be provided to allow the access of SCADA/DMS system data,
displays by outside users. One router shall be provided which shall be connected to the
external LAN/WAN communicating SCADA/DMS system. The external LAN/WAN users
shall be able to access SCADA/DMS data through the Web server system through this router.
Web servers shall also be provided with host based Intrusion prevention & detection system
(IPS ). The host-based IPS will be installed in both the Web-servers. The Network based IPS
shall be supplied for both the SCADA/DMS dual LAN and DMZ dual LAN.
All necessary hardware & software for Web Servers with firewalls and IPS shall be supplied
by the contractor.
The design & configuration, permertization, placement of DMZ shall be such that SCADA
/DMS system shall be protected from intrusion /vulnerabilities from outside world as per
IEC62443, IEC 62351-3, ISO/IEC27001. The cyber security shall be certified on SAT by
CERT.IN empanelled agency/ NCIIPC or any GoI agency before Operational acceptance by
SIA . The same shall be required to be verified at least once annually or Major upgrade or
change on the system or data of validity of certification which ever earlier during the FMS
period also and maintain required performance and functional requirements
6.2.1.3.2 Firewall:
Two firewalls shall be provided, one between Web servers & SCADA/DMS dual LAN and
another between Web servers & W eb server dual LAN. Specification of the firewall is given
in the chapter for software requirements.
Contractor shall provide equivalent tools such as Apache etc.for Web servers if UNIX
or LINUX O/s is used to meet the security requirement as envisaged in the
specification.
6.2.1.4 Training & development system server
6.2.1.4.1 DTS server;
A non - redundant server to host DTS applications shall be provided to impart the training.
6.2.1.4.2 Development server
A non- redundant server to host Developmental applications shall be provided
6.2.1.5 Data recovery cum communication server
Redundant DR server shall be provided with common external memory for mass historical
data storage and retrieval. The external memory shall comprise of multiple hot pluggable type
hard disks configured in RAID configuration. (Except RAID-0) The external memory shall
be connected either directly to the ISR server through SCSI/SAS interface or directly on the
LAN (Network Attached Storage). Alternatively, the bidder may offer RAID with each server
to meet the mass storage requirement in place of common external memory.. The minimum
requirement for external RAID for ISR servers is as below. The SCADA shall include
historical data storage configured to store historical data at the storage rates, for the required
period of time, and for the Ultimate historical database sizes given in chapter 19
Storage Array
Controller Cache: 512 MB per controller standard
Integrated RAID controller with an LCD/LED status display and 256 MB
read/write battery-backed cache (expandable to 512 MB per controller).
Host Interface: Fiber Channel connection per controller from the host side
Host Ports per Controller: Dual 2 Gb/s FC enabled
RAID Levels(EXCEPT RAID 0)
Redundant Controller: Yes
6.2.2 Operator Workstations
The operator Workstation console shall be used as a Man Machine Interface (MMI) by
despatcher for interacting with all SCADA/DMS system. Operator Workstation consoles shall
also be used as development console to take up developmental/ maintenance activities such
as generation/updation of database, displays etc.& to impart training through DTS
workstation consoles.
Each workstation shall consist dual monitors & single keyboard and a cursor positioning
device/mouse.
Workstation consoles for development system shall also be available with single TFT monitor
Operator workstation consists of a console driving single/ dual monitors as defined in the
BOQ.The user shall be able to switch the keyboard and cursor-positioning device as a unit
between both monitors of console. The minimum hardware configuration of operator
workstation shall be:
Multi core , Processor Speed : 3.2Ghz or better.
16GB Main memory (RAM)
the respective project area viz FO, radio, V-SAT etc.by network bandwidth service
provider(NBSP ) part of SIA team. The router shall support the OSI and TCP/IP protocols.
The Wide Area Links are planned for 2Mbps or higher Bandwidth capacity from ISPs (BSNL,
MTNL or any other NBSP)
The Router offered shall deliver high performance IP/MPLS features and shall support Layer
3 MPLS VPN connection. It shall support PPP/Frame Relay transport over MPLS.
The Routers shall be configurable and manageable through local console port, http interface,
NMS software and as well through Telnet.
The Router shall provide built-in monitoring and diagnostics to detect failure of hardware.
The Router shall be provided with LED/LCD indication for monitoring the Operational status.
The configuration changes on the Router should take effect without rebooting the router or
modules.
1) Memory Flash: Minimum 2GB
2) Console Port: 01 No. for configurations and diagnostic tests
3) LAN/WAN Port: The router shall support variety of interfaces as per the
concerned utility's requirement at site like V.24/V.35, E1, Channelized E1 etc.
along with following minimum number of ports:
Two fixed 10/100Mbps high speed Ethernet ports
Two fixed Serial ports with synchronous speed up to 2 Mbps and
with interface support for V.35/V.24 ports
Two fixed ports of G.703 E1 (2 Mbps) interface
One AUX port
Total no of ports shall be determined by the connectivity requirement.
All the interface cables for interconnecting all LAN/WAN ports as well as
connection to SCPC/MCPC/ leased E1 – V.35 ports etc. shall be in the scope
of bidder.
4) Scalability: Should have provision of at least 100% additional number of free
ports for future scalability
5) Network Protocol: TCP/IP and support for IP version 6. Shall provide IP address
Management
6) Routing Protocols:
RIP v1 (RFC 1058), RIPv2 (RFC 1722 AND 1723), OSPFv2 (RFC1583 & RFC
2328), OSPF on demand (RFC 1793), BGP4 with CIDR implementation as per
RFC 1771. The implement should be compliant as per RFC1745 that describes
BGP4/IDRP IP OSPF interaction. It shall provide Policy routing to enable changes
to normal routing based on characteristics of Network traffic. IS-IS protocol
support (RFC 1195).
7) WAN Protocols:
Frame Relay(LMI & Annexed & ITU Annex A), PPP (RFC1661), Multi-link PPP
12) Switching Performance: should be SD-WAN ready and should support current (200 Mbps)
upgradable up to 1Gbps
The following routers will be required as minimum, The minimum port
requirement is specified above. However, bidder shall determine no. of ports
requirement on the basis the interface & performance, availability & functional
requirements & shall provide additional features/ ports over and above minimum
requirement specified:
o SCADA/DMS router
o Intranet router at/DMZ
o DR router
o Router at S/S & remote VDUs locations
The router shall conform to UL 60950 or IEC 60950 or CSA 60950 or EN 60950
Standards for Safety requirements of Information Technology Equipment.
The router shall conform to EN 55022/32 Class A/B or CISPR22/32 Class A/B or
CE Class A/B or FCC Class A/B Standards for EMC (Electro Magnetic
Compatibility) requirements or equivalent BIS standard
6.2.6 Printers
Except for the output capabilities unique to any printer type (such as extended character sets,
graphic print and colouring features), there shall be no limitations on the use of any printer to
perform the functions of any other printer. All the SCADA/DMS system printers shall have
dual LAN interface either directly or through internal/external print servers. Printers for DTS
& development system shall have single LAN interface. The characteristics for each type of
printer are described below:
6.2.8 Digital Light Processing (DLP) Laser based Video Projection System
The contractor shall provide a video projection system based on modular DLP (Digital Light
Processing) Laser technology. All the screen modules of the VPS system, shall be suitableto
form combined high resolution projection images. The VPS system will be used to project
displays of SCADA/DMS system independently of workstation console monitors. All the
operations envisaged from workstation console (dispatcher) shall be possible from VPS also.
The Contractor shall supply all necessary hardware and software, including the multi- screen
drivers, adapters and memory to seamlessly integrate the video projection system with the
user interface requirements described in the specification.
The video projection systems shall be rear projection systems and shall be complete with all
projection modules, supporting structures and cabling. Design & installation of the video
projection systems shall be coordinated with the Employer during project implementation.
The requirement for each modular video display system include:
a) VPS screen with 3x4 matrix with each module minimum 70” diagonal and depth
of module 700mm max
b) VPS screen shall form a seamless rectangular array, using modules. (0.5mm)
max
c) VPS Graphics controller shall be interfaced to the SCADA/DMS system
through dual LAN connectivity.
d) Each projector shall provide a minimum resolution of 1920x1080 pixels per
module. The rear projection screens shall be capable of displaying full resolution
of the Laser source.
e) The VPS shall be capable of supporting multiple display modes in which one or
more modules show one or more SCADA/DMS displays concurrently as selected by
the user.
f) This system shall provide the same functional display capability as the full
graphics workstations.
6.9 Consumables
The Contractor shall supply, at its own expense, all consumables required for use during all
phases of the project through completion of the system availability test. The consumable
items shall include as minimum :
(a) Printer paper
(b) printer toner, ink. Ribbons and cartridges
(c.)storage devices like bluray disc /CD in line with storage device of Server
or Workstation
1. Each SCADA /DMS control center and ZSCC shall have 1 DTS at
control center .
2. Each DISCOM can have maximum 1 common or Disaster Recovery
center for SCADA/DMS cities (Group A) . However, as per
availability of infrastructure by utility , the same may corresponding
to each control center .
3. Each DR for ZSCC
4. For (Group B&C) or combined can be considered as per
infrastructure availability by utility
5. Workstation
For S/S - 2 minimum and 1 per each 20s/s and maximum upto 5
workstations
For network - 1minimum and 1 per each per 100 FPIs locations
and maximum upto 3 workstations
6. Remote VDUs shall be required at one each at Circle, Division, Sub-
division office, HQ (Common for all towns) , control center in-
charge.
End of Chapter 6
(a) Primary State: In primary state, a server performs any or all of the on-line functions
described in this specification and is referred as primary server. A primary server
shall concurrently perform maintenance functions (e.g. update of database, display
and reports).
(b) Backup State: A server in backup state is referred as backup server. A backup server
replaces a primary server/primary server group in the event of primary
server/primary server group failure or upon user command. It shall communicate
with the primary server(s) to maintain backup databases and monitor the state of
the primary server(s). A backup server shall concurrently perform maintenance
functions.
(c) Down State: A server in down state shall not communicate with the computer
system and is not capable of participating in any system activity
7.4 Peripheral Device States
Each peripheral device shall be assigned to one of the following states:
(a) Primary state: A device in primary state is referred as primary device. The
primary device is logically attached to a primary server or primary server
group. If the primary server or primary server group fails and its functions are
reassigned to a backup server or backup server group, the device shall follow
the reassigned functions.
(b) Backup state: A device in backup state is referred as backup device. A backup
device is used to replace a primary device in the event of primary device failure.
It shall communicate with the primary server or primary server group to inform
its readiness for it’s assignment as a primary device. A device may be assigned
to the backup state by the server function and by user action.
A backup device may participate in on-line activity alongwith the primary
device as can be the case with LAN s. For such cases, failure of any one device
shall cause other device to take up the role of both devices.
(c) Down state: A device in down state is referred as down device.
A down device cannot be accessed by the computer system.
7.5 Functional Redundancy
Every critical function must be supported by sufficient hardware redundancy to ensure that no
single hardware failure will interrupt the availability of the functions for a period exceeding the
automatic transfer time.
Non-critical functions are those that support maintenance and development of database,
application software and training of users. No hardware redundancy is envisaged for these
functions.
7.6 Backup Databases
Copies of all databases shall be maintained on the Backup server so that system operations may
continue in the event of Primary server, peripheral device or software failure. The backup
databases shall be updated with the current contents of the primary databases such that all
changes to a primary database are reflected in the backup database within 60 seconds of the
change. The backup databases shall be maintained in such a manner as to be protected from
corruption due to server and device failure. Backup databases shall be preserved for system
input power disruptions of any duration. The information maintained in the backup databases
shall include:
a) Telemetered, calculated, and manually-entered values and their attributes, including
quality codes, control inhibit state, and tag data
b) Data and associated attributes maintained by the Information storage and Retrieval
function
c) Alarm, event, and summary displays (such as off-normal, control inhibit, and alarm
inhibit displays) or sufficient information to rebuild the displays in their entirety
(including the time and date of the original data entries, not the time and date the display
is newly created)
d) Application function execution, control, and adaptive parameters and input and output
data, including DMS functions save cases.
e) Changes resulting from the addition or deletion of items and restructuring of databases
in an existing database shall be automatically accommodated in the backup database.
7.7 Error Detection and Failure Determination
All servers, peripheral devices, on-line software functions, and maintenance functions in
SCADA/DMS/OMS system shall be monitored for fatal error and recoverable errors. All errors
shall be recorded for review by maintenance personnel. Each type of error (e.g., server failure,
memory access violation, device reply time-out, or message checksum error) shall be recorded
separately with a date and time tag.
7.8 Server and peripheral device Errors
The Server/Device shall be declared as failed in case of fatal error. Server and peripheral device
failure shall be detected and annunciated to the user within 10 seconds of the failure. For
each type of recoverable error the programmer shall assign a threshold. When the count of
consecutive recoverable errors exceeds this threshold, a warning message shall be issued to the
operator.
7.9 Software Errors
Execution errors in on-line and maintenance functions that are not resolved by program logic
internal to the function shall be considered fatal software errors. Examples of errors that may
be resolved by internal program logic include failure of a study function to achieve a solution
due to violation of an iteration limit or arithmetic errors (such as division by zero) which are
caused by inconsistent input parameters or data. These errors shall produce an alarm informing
the user of the error but shall not be considered fatal software errors. Fatal software errors shall
result either in termination of the function or shall be handled as a fatal Server error. The action
to be performed shall be defined by the programmer for each on-line function and each
maintenance function. If the function is to be terminated, future executions of the function shall
also be inhibited until the function is again initiated by the programmer.
On the occurrence of each fatal software error, Server and operating system error codes and
messages shall be recorded in the SCADA/DMS/OMS system.
7.10 Server Redundancy and Configuration Management
Each server or server group supporting the CRITICAL functions described in the specifications,
shall include at least one redundant server. The redundant server shall normally be assigned to
the backup state and shall take the role of a primary server in the event of failure or upon user
command.
When a failure of a primary server in a redundant group is detected, the SCADA/DMS computer
system shall invoke the appropriate failover and restart actions so that on- line functions
assigned to the failed server are preserved. The on-line functions of the failed primaryserver shall
be assigned to the backup server by execution of a function restart within 30 seconds after
detection of server failure, except for ISR function. For ISR server function the corresponding
time shall be within 120 seconds after detection of server failure in case of failure of ISR sever,
the ISR data shall be stored in the SCADA/DMS system till the failover of ISR server is
completed to avoid data loss. This stored data shall be transferred to the ISR server automatically
after restoration of ISR server.
If on-line functions are restarted in a backup server, the server's state shall be changed to
primary. If backup servers are not available to perform the required functions, the
SCADA/DMS computer system shall attempt to restart the failed primary server. A complete
restart of the System, including full update from the field, shall not more than the stipulated time
as specified above. No data shall be lost during the transfer of operation.
A failover (transfer of critical functions) to an alternate Server shall occur, as a minimum, under
any one of the following situations:
all real time data values. Server startup shall be completed within 10 minutes and all applications
shall be operational within 15 minutes of application of power.
Hot Start: In which the memory resident version of database shall be used for continued
operation. No reload of saved data shall be performed, although application software restarts.
The intent is that after hot restart, only the operations being performed at the time of failure may
be lost. All on line applications shall be operational not more than failover time.
7.12 Peripheral Device Redundancy and Configuration Management
The device failover shall result in an orderly transfer of operations to a backup device in the
event of failure of primary device. The device failover function may replace a failed device with
an identical backup device or with a backup device that is different from the normal device.
Device failover actions shall be completed and the backup device shall be operating within 30
seconds of detection of the device failure. All device failures shall be annunciated by alarms.
7.13 System Configuration Monitoring and Control
Required displays shall be provided for the user to review the system configuration and to
control the state of the equipment. The following operations shall be possible:
Fail-over, switching of states and monitoring of Servers and peripheral devices.
Control of the resource usage monitoring function and display of server resource
utilization
The user shall be provided with the capability to interact with all functions using
displays. It shall be possible to atleast Stop, Start, inhibit /enable and Restart any
of the functions.
Displays to view and control the status of backup databases shall also be
provided.
End of Chapter 7
This chapter describes the specific requirements for testing and documentation of the SCADA/DMS
system. The general requirements of testing and documentation are covered in chapter 18. This chapter is
applicable to Group A, B, C , U towns as per functional requirements.
8.1 Type testing –
Equipment wherever mentioned in the specification for type testing shall conform to the type tests listed
in the relevant chapters. Type test reports of tests conducted in NABL accredited Labs or internationally
accredited labs with in last 5 years/ or validity of test of certificate whichever is lower from the date of
bid opening may be submitted. In case, the submitted reports are not as per specification, the type tests
shall be conducted without any cost implication to employer before approval during design & engineering.
Further, the equipment indicated in the MoP oder no 12/34/2020-T&R dtd 08.06.21 & CEA
/PLG/R&D/MII/2021 dtd 11.06.21 and any amendment from time to time shall be adhered to. If there is
a difference between the type test requirement mentioned above specification and type test requirement
mentioned in the respective sections, the above shall prevail
8.2 Ad –doc testing
Utility may optionally ask SIA to stage ad-doc testing in presence of team comprising of PFC, utility.
Other members may also be opted like, by like CEA, Discom , Nodal agency . for basic of prototype of
SCADA/DMS /OMS functions of offered product with simulated offered at least 2 RTU & FRTUs.and
balance by simulation for one sample project area . The same may be considered in design & engineering
stage
8.3 Factory Acceptance Tests (FAT)
For each SDCC , ZSCC , SCADA/DMS/OMS system including DR center (DR is part of theproject area)
shall be tested at the Contractor's facility. All hardware and software associated with the SCADA/DMS
/OMS system and atleast two RTUs alongwith, LDMS, 1 type of numerical relays and one SCADA
enabler each (if part of supply under this project) &10 FRTUs & all Remote VDUs, shall be staged for
the factory testing and all remaining RTUs/FRTUs/FPIs shall be simulated for the complete point counts
(ultimate size). The requirements for exchanging data with other computer systems like DR (if DR is not
a part of the project area), data exchange with other envisaged shall also be simulated.
Each of the factory tests described below (i.e. the hardware integration test, the functional performance
test, integrated system test and unstructured tests) shall be carried out under factory test for the
SCADA/DMS system. The factory tests, requiring site environment, shall be carried out during the Field
Tests after mutual agreement for the same from owner.
8.3.1 Hardware Integration Test
The hardware integration test shall be performed to ensure that the offered computer hardware, conforms
to this Specification requirements and the Contractor- supplied hardware documentation. All the
SCADA/DMS system hardware shall be integrated and staged for testing. Applicable hardware
diagnostics shall be used to verify the hardware configuration ofeach equipment. The complete hardware
& software bill of quantity including software licenses & deliverables on electronic media shall also be
verified
8.3.2 System Build test
After completion of hardware integration test, the SCADA/DMS system shall be built from the backup
software on electronic media (CDs/ Tapes) to check the completeness of backup mediafor restoration of
system in case of its crashing/failure. The software deliverables shall includeone copy of backup software
on electronic media.
Page 128 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
c) the mapping of SCADA database with RTU /FRTU/FPI database for all
RTU/FRTU/FPI points
d) the mapping of SCADA database with displays and reports
The Contractor shall provide the details of all the variances observed and corrections carried
out during end to end test.
8.4.3 Field Performance Test
The field performance test shall concentrate on areas of SCADA/DMS/OMS operations that
were simulated or only partially tested in the factory (e.g., system timing and loading while
communicating with a full complement of RTUs/FRTU/FPI and data links and system reaction
to actual field measurements and field conditions). Further the validity of factory test results
determined by calculation or extrapolation shall be examined.
After the end to end test, the Contractor shall conduct the field performance test to verify the
functional performance of the system in line with the technical specification which includes the
following:
a) the communication of other system envisaged, if any e.g. IT , SLDC, DR system with
SCADA/DMS/OMS system
b) Mapping of SCADA/ISR database with other system database e.g. IT , SLDC, DR
system , NPP (SAIFI ,SAIDI data) with SCADA/DMS/OMS system
c) Verify that all the variances observed during the Factory test are fixed and
implemented.
d) Conduction of the Factory tests deferred (tests requiring site environment)
e) Functional tests of SCADA/DMS /OMSsystem
f) Verify the execution rates of all SCADA/DMS/OMS application
g) Verify update rate & time for data update & control command execution as per
specification requirements
h) Verify the response time of all SCADA/DMS/OMS applications.
i) Verify the response time for User interface requirements
j) Testing of all features of the database, display, and report generation and all other
software maintenance features on both the primary and backup servers. Online
database editing shall also be tested on primary server.
k) Conduction of unstructured tests as decided by the Employer
8.4.4 Cyber security compliance
Compliance of cyber security without threatening vulnerabilities by CERT.IN empaneled
agency shall be carried out. DISCOM CISO shall also be available during this verification.
Further, the equipment indicated in the MoP order no 12/34/2020-T&R dtd 08.06.21 & CEA
/PLG/R&D/MII/2021 dtd 11.6.21 and any amendment from time to time shall be adhered to.
8.5 System Availability Test (360 hours)
Contractor shall provide & approve theoretical and practical figures used for this calculation
at the time of detailed engineering. The calculation shall entail reliability of each individual
unit of the System in terms of Mean Time between Failures (MTBF and a Mean time to Repair
(MTTR) as stated by OEM. Reliability figures of existing equipment shall be supported by
evidence from operational experience at similar types of installation / figure given by OEM.
From those data, the unavailability of each sub-system shall be calculated taking in account
each item redundancy. The global availability shall then be calculated from those different
unavailability data. This calculation shall lead to the failure probability and equivalent global
MTBF data for the control center system.
The overall assessment of System availability shall be provided in the form of an overall
System block diagram with each main item shown, complete with its reliability data. The
calculation of overall availability shall be provided with this diagram.
System availability tests shall be conducted after completion of the field tests. The system
availability test shall apply to the SCADA/DMS/OMS system (hardware and software)
integrated with its RTUs/FRTU/FPIs and legacy system envisaged However, the non-
availability of RTUs/Data Concentrators/ FRTU/FPI , legacy IT system etc. & Communication
System shall not be considered for calculating system availability. However, RTU/FRTU,
communication equipment’s auxiliary power supply shall be tested as per the provisions given
in their chapters.
The SCADA/DMS system (hardware and software systems) shall be available for
99% of the time during the 360hours (15 days) test period. However, there shall not be any
outage /down time during last 85 Hours of the test duration. In case the system availability falls
short of 99%, the contractor shall be allowed to repeat the system availability test after fixing
the problem, failing which the system shall be upgraded by the contractor to meet the
availability criteria without any additional cost implication to the owner.
Availability tests of RTUs/FRTUs /FPI shall be conducted along with System availability test
for 360 hours. Each RTU/FRTUs shall exhibit minimum availability of 98%. In case the
RTU/FRTU availability falls short of 98%, the contractor shall be allowed to repeat the
RTU/FRTU availability test (for failed RTU/FRTU/FPI only) after fixing the problem, failing
which the equipment shall be upgraded by the contractor to meet the availability criteria
without any additional cost implication to the owner.
In the event of unsuccessful reruns of the availability test, employer may invoke the default
provisions described in the General Conditions of Contract.
The system availability tests will be performed by the owner by using the SCADA/DMS
system and RTUs/FRTU/FPI for operation, control and monitoring of distribution system and
using Contractor supplied documentation. The owner will also be required to generate daily,
weekly and monthly reports. The supplied system shall be operated round the clock.
The SCADA/DMS/ OMS system shall be considered as available if
a) one of the redundant hardware is available so that all the SCADA/DMS/OMS
applications are functional to ensure the design & performance requirement as
envisaged in the specification
b) At least one of the operator console is available
c) At least one of the printers is available (off-lining of printers for change of ribbon,
cartridge, loading of paper, paper jam shall not be considered as downtime)
d) All SCADA applications are available
e) All DMS, OMS applications are available
f) All SCADA/DMS/ OMS functions described in the specification are executed at
periodicities specified in the specification. without degradation in the response times
8.6 Documentation
The complete documentation of the systems shall be provided by the contractor. Each revision
of a document shall highlight all changes made since the previous revision. Employer's intent
is to ensure that the Contractor supplied documentation thoroughly and accurately describes
the system hardware and software.
The contractor shall submit the paper copy of all necessary standard and customized
documents for SCADA/DMS in 2 sets for review/approval by the Employer for necessary
reference which includes the following:
a) System overview document
b) Cross Reference Document
c) Functional design document
d) Standard design documents
e) Design document for customization
f) System Administration documents- software utilities, diagnostic programs etc.
g) Software description documents
h) Bill of Quantity & List of software and hardware deliverable
i) protocol implementation documents
j) point address document
k) IP addressing plan document
l) Software User document for dispatchers
m) Software Maintenance document
n) Training documents
o) Real time & RDBMS documents
p) Database settings, Displays and Reports to be implemented in the system
q) Test procedures
r) Test reports
s) Hardware description documents
t) Hardware User documents
u) Hardware Maintenance documents
v) Data Requirement Sheet (DRS) of all Hardware
w) Site specific Layout, Installation, GA, BOQ, schematics and cabling details
drawings/documents
x) SCADA & IT Integration Plan Document using GIS Adapters & Messaging
Interfaces.
y) Cyber Security Plan & Mitigation document (or Cyber Crisis Management Plan
(CCMP)) for the system if Public Networks are used.
z) Interoperability profiles/ Tables
After approval two sets of all the above documents as final documents shall be
End of Chapter 8
battery backup to hold data in SOE buffer memory & also maintaining the time
& date.
(i) As the SCADA/DMS system will use public domain such GPRS/MPLS-
4G/CDMA etc., therefore it mandatory to guard the data/ equipment f r o m
intrusion/damage/breach of security & shall have SSL/VPN based security.
(j) Shall have SNMP
(K) Conformance to IEC62351-3/ IEC62443 standard for cyber security
Support Feature:
All support feature as mentioned below will not be used now & may require in future. However,
the same shall be tested in routine /Factory Tests. Further, it should be possible to have
following capabilities in the RTU by way of addition of required hardware limited to addition
of I/O modules & communication card or protocol converter & using the same firmware at later
date:
a) Support for Analog output in form of standard current loops viz 4-20Ma
etc
b) Support for IEC61850 /protocols & ability to act as a gateway for Numerical
relays/ Smart Meters may have to be interfaced if need be
c) Have required number of communication ports for simultaneous
communication with Master station(s), /MFTs and RTU configuration &
maintenance tool.
(d) PLC support
(e) Communication with at least two master stations simultaneously on IEC]
60870-5-104
(f) Receiving and processing analog commands from master station(s) and
Capability of driving analog output card.
(g) RTU shall be capable of acquiring analog values through transducers having
output as 4-20 mA, 0-10 mA, 0-+10 mA or +/- 5 volts etc. using analog
input modules.
(h) Capability of time synchronization with GPS receiver which may be
required future.
9.3 Communication ports
The RTUs shall have following communication ports to communicate with master station,
existing /MFTs and configuration & maintenance terminal.
a) RTU shall have two TCP/IP Ethernet ports for communication with Master
station(s) using IEC 60870-5-104.
b) RTU shall have required number of RS 485 ports for communication with
MFTs to be connected in daisy chain using MODBUS protocol. Minimum 15
analog values (including 4 energy values) to be considered per energy meter The
RTU shall be designed to connect maximum 5 MFTs. Further , bidder to
demonstrate during testing that all analog values updated within 2 sec. The
updation time shall be demonstrated during FAT(routine) & SAT testing . The
The RTU analog-to-digital (A/D) converters shall have a digital resolution of at least twelve
(12) bits plus sign. The overall accuracy of the analog input system shall be at least 0.2%(i.e.
99.8%) at 25 ºC of full scale . Mean accuracy shall not drift more than 0.002% per degree C
within the temperature range of –5 to +55 degree Linearity shall be better than 0.05%. The RTU
shall be designed to reject common mode voltages up to 150 Vac (50 Hz). For dc inputs,normal
mode noise voltages up to 5 Vac shall be rejected while maintaining the specified accuracy.
Each input shall have suitable protection and filtering to provide protection against voltage
spikes and residual current at 50 Hz, 0.1 ma (peak-to-peak) and overload. Loading upto150% of
the input value shall not sustain any failures to the RTU input.
The ability of the RTU to accommodate dc inputs shall include the following signal ranges:
Unipolar Voltage:0-0.5V, 0-1V, 0-5V, 0-10V, Unipolar Current:0-1mA, 0-10mA,
0-20mA, 4-20Ma, Bipolar Voltage: 0.5V, 2.5V, 5V, -20-0-20mA (- to +)
The total burden imposed by the RTU/DC analog input circuit shall not exceed 0.5 volt-ampere
for current and voltage inputs. As an option, contractor may also provide transducer less
solution to connect direct CT/PT secondaries.
9.5 Status input
RTU shall be capable of accepting isolated dry (potential free) contact status inputs. The RTU
shall provide necessary sensing voltage, current, optical isolation and de-bounce filtering
independently for each status input. The sensing voltage shall not exceed 48Vdc.
The RTU shall be set to capture contact operations of 20 ms or more duration. Operations of
less than 20 ms duration shall be considered no change (contact bounce condition). The RTU
shall accept two types of status inputs i.e. Single point Status inputs and Double point status
inputs.
To take care of status contact chattering, a time period for each point and the allowable number
of operations per time period shall be defined. If the allowable number of operations exceed
within this time period, the status change shall not be accepted as valid
Single point status input will be from a normally-open (NO) or normally-closed
(NC) contact which is represented by 1-bit in the protocol message.
The Double point status input will be from two complementary contacts (one NO and one NC)
which is represented by 2-bits in the protocol message. A switching device status is valid only
when one contact is closed and the other contact is open. Invalid states shall be reported when
both contacts are open or both contacts are closed.
All status inputs shall be scanned by the RTU from the field at 1 millisecond periodicity.
9.6 Sequence of Events (SOE) feature
To analyse the chronology or sequence of events occurring in the power system, time tagging of
data is required which shall be achieved through SOE feature of RTU. The RTU shall have an
internal clock with the stability of 10ppm or better . The RTU time shall be set from time
synchronization messages received from master station using IEC 60870-5- 104 protocol. In
addition, the message can be transmitted using NTP/SNTP. SOE time resolution shall be 1ms
or better
The RTU shall maintain a clock and shall time-stamp the digital status data. Any digital status
input data point in the RTU shall be assignable as an SOE point. Each time a SOE status
indication point changes the state, the RTU shall time-tag the change and store in SOE buffer
within the RTU. A minimum of 1000 events can be stored in the SOE buffer. SOE shall be
transferred to Master Station as per IEC 60870-5-104 protocol. SOE buffer & time shall be
maintained by RTU on power supply interruption.
9.7 IED pass through
The Master Station user shall be able to perform a virtual connection with any IED connected to
the RTU/DC, provided the communication protocol functionality, to support the information
transfer from and to the IEDs. For example, the Master Station shall gather on-demand IED
data, visualize IED configuration parameters, and IED source code depending upon the IED
capabilities. On the other hand, the Master Station shall be able to download to the IEDs
configuration parameters, code changes, etc. depending upon the IED capabilities. This feature
is a support function considering in future implementation. The capability can be demonstrated
with the upload & download of data from master station with IEDs connected to the RTUs
using the support of protocols specified in this chapter. Numerical relays Analog data viz
voltage ,current, sag swell instantaneous, momentary , temporary, over voltage, under voltage,
over current , phasor measurement , THD, current TDD & current unbalance ratio etc. at
numerical relays if installed at bay of S/S
b) Minimum core cross-section of 2.5 mm2 for PT cables, 4 mm2 for CT cables, ifapplicable
and 2.5 mm2 for Control outputs and 1.5mm2 for Status inputs
c) Rated voltage Uo/U of 0.6/1.1KV
d) External sheathing of cable shall have oxygen index not less than 29 & temperature
index not less than 250. Cable sheath shall meet fire resistance testas per IS 1554 Part- I.
e) Shielding, longitudinally laid with overlap.
f) Dielectric withstand 2.5 kV at 50 Hz for 5 minutes
g) External marking with manufacture's name, type, core quantity, cross-section, and
year of manufacture.
h) Armored Cables shall be used in the area where cable will pass through openarea
which may experience loading.
i) The Communication cable shall be of shielded twisted pairs and of minimum0.22sq
mm size.
9.19 Terminal Blocks (TBs)
Terminal blocks shall be having provision for disconnection (isolation), with full- depth
insulating barriers made from moulded self-extinguishing material. Terminal blocks shall be
appropriately sized and rated for the electrical capacity of the circuit and wire used. No more
than two wires shall be connected to any terminal. Required number of TBs shall be provided for
common shield termination for each cable.
All terminal blocks shall be suitably arranged for easy identification of its usages such as CT
circuits, PT circuits, analog inputs, status inputs, control outputs, auxiliary power supply
circuits, communication signals etc. TBs for CT circuits shall have feature for CT shorting (on
CT side) & disconnection (from load side) to facilitate testing by current injection. Similarly,
TBs for PT circuit shall have feature for disconnection to facilitate voltage injection for testing.
End of Chapter 9
10.0 General
The Feeder Remote Terminal Unit (FRTU) shall be installed at Ring Main Units (RMUs),
Sectionalizers locations FRTU shall also be used for control of switching devices such as
breaker, isolator switches etc. inside RMU panel, Sectionalizers etc. from Master station(s). The
supplied FRTUs shall be interfaced with the RMUs, FPI, communication equipment, power
supply distribution boards; for which all the interface cables, TBs, wires, lugs, glands etc. shall
be supplied, installed & terminated by the Contractor. Further, the equipments indicated in the
MoP oder no 12/34/2020-T&R dtd 08.06.21 & CEA /PLG/R&D/MII/2021 dtd 11.6.21 and any
amendment from time to time shall be adhered to. This chapter is applicable to Group A towns
as per functional requirements
10.1 Design Standards
The FRTUs shall be designed in accordance with applicable International Electro- technical
Commission (IEC), Institute of Electrical and Electronics Engineer (IEEE), American National
Standards Institute (ANSI), and National Equipment Manufacturers association (NEMA)
standards, unless otherwise specified in this Technical specification. In all cases the provisions
of the latest edition or revision of the applicable standards in effect shall apply. The FRTU shall
comply to IEC62351-3/ IEC62443 standard for cyber security
10.2 FRTU Functions
All functional capability described herein shall be provided by the Contractor even if a function
is not initially implemented.
As a minimum, the FRTU shall be capable of performing the following functions:
a) Acquiring analog values from Multifunction Transducers or alternatively through
transducer- less modules and the status inputs of devices from the substation,
processing and transmitting to Master stations. Capability to acquire analog inputs
from analog input cards receiving standard signals viz current loops 4-20Ma , RTD
etc.
b) Receiving and processing digital commands from the master station(s) (c) Data
transmission rates - 300 to 19200 bps for Serial ports for MODBUS and 10/100 mbps for
TCP/IP Ethernet ports
c) Use of IEC 60870-5-104/101 protocol to communicate with the Master station(s) at
least 2 Use of MODBUS over RS485 interface , Protocol to communicate with the
MFTs.
d) Have required number of communication ports for simultaneous communication
with Master station(s), MFTs and FRTU configuration & maintenance tool.
e) FRTU shall have the capability of automatic start-up and initialization following
restoration of power after an outage without need of manual intervention. All
restarts shall be reported to the connected master stations.
f) Remote database downloading of FRTU from master station from SCADA/ DMS
control center.
g) Internal battery backup to hold data in SOE buffer memory & also maintaining the
time & date.
analog values shall also be reported to Master station by exception on violation of a defined
threshold limit. All the analog values and status data shall also be assigned to scan groups for
integrity check by Master stations at every 10 minutes configurable up to 60 minutes FRTU
wise.
FRTU shall report energy values to master station periodically. The periodicity shall be
configurable from 5 minutes to 24 hours (initially set for 15 minutes)
10.3.2 Communication Protocol between FRTU & MFTs
The FRTU shall acquire data from the MFTs using the MODBUS protocol. In addition, usage
of IEC 60870-5-101/104 protocols is also permitted. The MFT will act as slave to the FRTU.
The FRTU shall transmit these values to the master station in the frame of IEC 60870-5-
104/101 protocol.
10.4 Analog Inputs
The real time values like, Active power, Reactive Power, Apparent power three phase Current
& Voltage and frequency, power factor & accumulated values of import /export energy values
will be acquired FRTU from the following in the given manner:
1. MFTs installed in RMU/DTs
2. RTU shall also take 4-20 mA, 0-20mA, 0- -10mA, 0-+10mA, 0-5V etc.as analog
inputs to acquire DC power supply voltage etc.
The FRTU analog-to-digital (A/D) converters shall have a digital resolution of at least twelve
(12) bits plus sign. The overall accuracy of the analog input system shall be at least 0.2%(i.e.
99.8%) at 25 ºC of full scale . Mean accuracy shall not drift more than 0.002% per degree C
within the temperature range of –5 to +55 degree Linearity shall be better than 0.05%. The
FRTU shall be designed to reject common mode voltages up to 150 Vac (50 Hz). For dc inputs,
normal mode noise voltages up to 5 Vac shall be rejected while maintaining the specified
accuracy. Each input shall have suitable protection and filtering to provide protection against
voltage spikes and residual current at 50 Hz, 0.1 ma (peak-to-peak) and overload. Loading upto
150% of the input value shall not sustain any failures to the FRTU input.
The ability of the FRTU to accommodate dc inputs shall include the following signal ranges:
Unipolar Voltage:0-0.5V, 0-1V, 0-5V, 0-10V,
Unipolar Current: 0-1mA, 0-10mA, 0-20mA, 4-20Ma, Bipolar
Voltage: 0.5V, 2.5V, 5V, -20-0-20mA (- to +)
The total burden imposed by the FRTU analog input circuit shall not exceed 0.5 volt-ampere
for current and voltage inputs. As an option, contractor may also provide transducer less
solution to connect direct CT/PT secondaries.
10.5 Status input
RTU shall be capable of accepting isolated dry (potential free) contact status inputs. The RTU
shall provide necessary sensing voltage, current, optical isolation and de-bounce filtering
independently for each status input. The sensing voltage shall not exceed 48 Vdc/220VAC.
The RTU shall be set to capture contact operations of 20 ms or more duration. Operations of
less than 20 ms duration shall be considered no change (contact bounce condition). The RTU
shall accept two types of status inputs i.e. Single point Status inputs and Double point status
inputs.
To take care of status contact chattering, a time period for each point and the allowable number
of operations per time period shall be defined. If the allowable number of operations exceed
within this time period, the status change shall not be accepted as valid
Single point status input will be from a normally-open (NO) or normally-closed (NC) contact
which is represented by 1-bit in the protocol message.
The Double point status input will be from two complementary contacts (one NO and one NC)
which is represented by 2-bits in the protocol message. A switching device status is valid only
when one contact is closed and the other contact is open. Invalid states shall be reported when
both contacts are open or both contacts are closed.
All status inputs shall be scanned by the FRTU from the field at 1 millisecond periodicity.
10.6 Sequence of Events (SOE) feature
To analyze the chronology or sequence of events occurring in the power system, time tagging of
data is required which shall be achieved through SOE feature of RTU. The RTU shall have an
internal clock with the stability of 100ppm or better. The RTU time shall be set from time
synchronization messages received from master station using IEC 60870-5- 104 protocol. SOE
time resolution shall be 10 ms or better
The RTU shall maintain a clock and shall time-stamp the digital status data. Any digital status
input data point in the RTU shall be assignable as an SOE point. Each time a SOE status
indication point changes the state, the RTU shall time-tag
The change and store in SOE buffer within the RTU. A minimum of 300 events can be stored in
the SOE buffer. SOE shall be transferred to Master Station asper IEC 60870-5-104 protocol. SOE
buffer shall be maintained by FRTU on power supply interruption.
10.7 Control Outputs
The FRTU shall provide the capability for a master station to select and change the state of
digital output points. These control outputs shall be used to control power system devices such
as Circuit breakers, isolator, reset, relay disable/enable and other two-state devices, which shall
be supported by the RTU.
A set of control outputs shall be provided for each controllable device. On receipt of command
from a master station using the select check-before-execute operate (SCBO) sequence, the
appropriate control output shall be operated for a preset time period which is adjustable for
each point from 0.1 to 2 seconds.
Each control output shall consist of one set of potential free NO contact. The output contacts
shall be rated for atleast 0.2 Amp. at 48 Vdc. These output contact shall be used to drive heavy
duty relays. In case Control output module of FRTU does not provide potential free control
output contact of this rating, then separate control output relays shall be provided by the
contractor. These relay coils shall be shunted with diodes to suppress inductive transients
associated with energizing and de-energizing of the relay coils & shall conform to the relevant
IEC requirements.
10.7.1 Heavy duty control output relays
The control output contact from the FRTU shall be used for initiating heavy duty relays for
trip/close of switching devices. The contractor shall provide heavy duty relays. Each control
output relays shall consist of atleast 2 NO contacts. The output contacts shall be rated for at least
5 Amps Continuous at 220Vdc and shall provide arc suppression to permit interruptions of an
inductive load. Relay coils shall be shunted with diodes to suppress inductive transients
associated with energizing and de-energizing of the relay coils. The relays shall conform to the
IEC255-1-00 and IEC 255-5 requirements.
10.7.2 Control Security and Safety Requirements
The FRTU shall include the following security and safety features as a minimum for control
outputs:
a) Select- check-before-operate operate (SCBO) sequence for control output.
b) No more than one control point shall be selected/ executed at any given time.
c) The control selection shall be automatically cancelled if after receiving the
"control selection" message, the "control execute" command is not received
within the set time period.
d) No control command shall be generated during power up or power down of
FRTU.
10.7.3 Local/Remote selector switch
A manual Local/Remote selector switch shall be provided for each FRTU to disable all control
outputs by breaking the power supply connection to the control output s. When in the "Local"
position, the Local/Remote switch shall allow testing of all the control outputs of FRTU without
activating the control outputs to field devices. A status input indication shall be provided for the
Local/Remote switch to allow the SCADA system to monitor the position of the switch.
10.7.4 Dummy breaker latching relay
The Contractor shall provide a latching relay to be used to simulate and test supervisory control
from the Master station. The latching relay shall accept the control signals from the FRTU to
open and close, and shall provide the correct indication response through a single point status
input.
10.8 Contact Multiplying Relays (CMRs)
Contact Multiplying Relays (CMRs) are required to multiply the contacts of breaker, isolators
and protection relays etc. The contacts of these relays shall be used to provide status inputs to
the RTUs.
The relays shall be DC operated self-reset type. The rated voltage for relay operation shall be
on 24/48/110/220V DC depending on the station DC supply. The relay shall be able to operate
for +/-20% variation from nominal voltage.
The relay shall have a minimum of two change over contacts, out of which one shall be used
for telemetry purposes. The contacts shall be rated to carry minimum current capacity of 5A.
The relay shall conform to following requirement.
a) Power Frequency withstands voltage–2KV for 1 minute as per IEC 255-5.
b) Insulation Resistance of 100M ohms measured using 500V DC megger.
c) 5KV Impulse test as per IEC 255-5
The relays coils shall be shunted with diodes to suppress inductive transients associated with
energizing and de-energizing of the relay coils. The relays shall conform to the IEC 255-1-00
and IEC 255-5 requirements. The relays must be protected against the effects of humidity,
corrosion & provide with a dust tight cover. The connecting terminals shall be screw type &
legibly marked. The relays may optionally have a visual operation indicator. The relays are to be
mounted in junction /termination box and therefore shall be equipped with suitable mounting
arrangements. In case suitable space is not available in junction /termination box the same shall
be mounted in FRTU panel.
10.9 Time facility
The internal FRTU time base shall have a stability of 100 ppm. The RTU shall be synchronised
through synchronisation message from master station at every 5 minutes (configurable from 5
minutes to 60 minutes) over IEC 60870-5-104/101/NTP/SNTP
10.10 Diagnostic Software
Diagnostic Software shall be provided to continuously monitor operation of the FRTU and
report RTU hardware errors to the connected master stations. The soft- ware shall check for
memory, processor, and input/output ports errors and fail- ures of other functional areas defined
in the specification of the RTU.
10.11 Input DC Power Supply
The FRTU will be powered from a 48 V DC power supply system. The RTU shall not place
additional ground on the input power source. The characteristics of the input DC power supply
shall be
(a) Nominal voltage of 48 Vdc with variation between 40.8 and 57.6
Vdc.(i.e. 48(+20%/-15%)
(b) Maximum AC component of frequency equal to or greater than 100 Hz and
0.012 times the rated voltage peak-to-peak.
The FRTU shall have adequate protection against reversed polarity, over current and under
voltage conditions, to prevent the RTU internal logic from being damaged and becoming
unstable causing mal-operation. Utility may opt any other voltage level such as 12, 24, 110
VDC etc. and permissible ranges and applicable standards specified shall be adhered to
accordingly. The interface components like CMRs , HDRs MFT etc. may also be selected
accordingly.
10.12 Environmental Requirements
The FRTU will be installed in inside RMU Panel or in open environment with no temperature
or humidity control. The RTUs shall be capable of operating in ambient temperature from -20
to +60 degree C with rate of temperature change of 20 degree C/hour and relative humidity less
than 95%, non-condensing. FRTUs to be installed in the hilly region with the history of
snowfall, the same the lower ambient temperature limit shall be -20 degree C. Utility may
specify location with altitude more than 2000m above MSL for compliance of FRTUs to be
installed in that project area
10.13 FRTU Size and Expandability
FRTU shall be equipped for the point counts defined in the BOQ (Basic+20% spare (wired &
hardware). It shall be possible to expand the FRTU capability for additional 100 % of the basic
point counts by way of addition of hardware such as modules, racks, panels, , however, FRTU
software and database shall be sized to accommodate such growth without requiring software or
database regeneration.
10.14 FRTU Panels
At least 50% of the space inside each enclosure shall be unused (spare) space that shall be
reserved for future use. The Contractor shall provide required panels conforming to IEC 529 for
housing the FRTU modules/racks, relays etc. and other required hardware. The panels shall meet
(b) shall have maintenance access to the hardware and wiring through lockable doors.
(c) shall have the provisions for bottom cable entry
(d) The safety ground shall be isolated from the signal ground and shall be connected
to the ground network. Safety ground shall be a copper bus bar. The contractor
shall connect the panel’s safety ground of to the owner’s grounding network.
Signal ground shall be connected to the communication equipment signal ground.
(e) All panels shall be supplied with 230 Vac, 50 Hz, single-phase switch and
15/5A duplex socket arrangement for maintenance.
(f) All panels shall be provided with an internal maintenance lamp, space
heaters and gaskets.
(g) All panels shall be outdoor, dust-proof with rodent protection, and meet class of
protection. IP41 if housed in RMU panel & IP54 in case of in open outdoor.
(h) There shall be no sharp corners or edges. All edges shall be rounded to
(j) All materials used in the enclosures including cable insulation or sheathing, wire
troughs, terminal blocks, and enclosure trim shall be made of flame retardant
material and shall not produce toxic gasses under fire conditions.
10.15 Wiring/Cabling requirements
The FRTU panels shall gather all signals from and to the devices located in Control
& Relay panels in the substation control room. All wires that carry low-level signals shall be
adequately protected and separated as far as possible from power wiring. All wires shall be
identified either by using ferrules or by color coding. In addition, cables shall be provided with
cable numbers at both ends, attached to the cable itself at the floor plate where it enters the
cubicles.
Shielded cables shall be used for external Cabling from the FRTU panels. The external cables
(except communication cables) shall have the following characteristics:
a) All cables shall have stranded copper conductor.
b) Minimum core cross-section of 2.5 mm2 for PT cables, 4 mm2 for CT cables, if
applicable and 2.5 mm2 for Control outputs and 1.5mm2 for Status inputs
c) Rated voltage Uo/U of 0.6/1.1KV
d) External sheathing of cable shall have oxygen index not less than 29 &
temperature index not less than 250. Cable sheath shall meet fire resistance test as
per IS 1554 Part- I.
e) Shielding, longitudinally laid with overlap.
f) Dielectric withstand 2.5 kV at 50 Hz for 5 minutes
g) External marking with manufacture's name, type, core quantity, cross- section,
and year of manufacture.
The Communication cable shall be of shielded twisted pairs and of minimum 0.22sq mmsize.
10.16 Terminal Blocks (TBs)
Terminal blocks shall be having provision for disconnection (isolation), with full- depth
insulating barriers made from moulded self-extinguishing material. Terminal blocks shall be
appropriately sized and rated for the electrical capacity of the circuit and wire used. No more
than two wires shall be connected to any terminal. Required number of TBs shall be provided for
common shield termination for each cable.
All terminal blocks shall be suitably arranged for easy identification of its usages such as CT
circuits, PT circuits, analog inputs, status inputs, control outputs, auxiliary power supply
circuits, communication signals etc. TBs for CT circuits shall have feature for CT shorting (on
CT side) & disconnection (from load side) to facilitate testing by current injection. Similarly, TBs
for PT circuit shall have feature for disconnection to facilitate voltage injection for testing.
End of Chapter 10
line ranges specified in analog input card in clause for analog input shall be selected. The
accuracy of transducer shall be ±0.5%
11.3 Transformer Tap Position Transducer
The transformer tap position indications shall be either of two types based on field requirement..
(i) Variable resistance type
(ii) Lamp type
The Contractor shall provide suitable resistance tap position transducers which shall have the
following characteristics
(a) The input measuring ranges shall be from 2 to 1000 ohms per step, which is
tuneable at site with at least 25 steps.
(b) Dual output signal of 4 to 20 mA DC, 0.5% accuracy class as per IEC 688 shall be
provided. One output will be used for driving a local digital indicator (to be
provided by the contractor) and the other will be used for interfacing with the
RTU. Alternatively for RTU, MODBUS link may be used. In case of lamp type,
additional resistance/potentiometer unit shall be provided to convert the dry type
contacts to a variable resistance as defined in (a) above, suitable for the remote
indication
11.4 Modems
The modem shall have suitable interface facility to connect with the meter by using the
RS232 /485cable. It shall have dual SIM facility
The offered modems should be capable of operating on Threephase supply drawn from
the FPI input itself. Auxiliary Power supply will not be acceptable form Modem at FPI
The operating voltage range for the modem should be 90 V ac P-P to 440 V ac P-P.
However the modem should also be capable of operating on single phase 230 V, 50 Hz
power supply. The modemvoltage surges. Modem at FRTU locations should be
capable of operating on dc voltage in line with FRTU voltage . The offered Modem
should be capable to transfer the entire data as per the FRTU data requirement of
FRTU/FPI at control center shall be suitably protected against
The offered Modem should be capable to transfer the entire data as per the FRTU data
requirement of FRTU/FPI at control center i.e. 4G /5G as per site signal condition
The offered Modem should be supplied with power cable, antenna with co-axial cable
of length, RS 232 /485connecting suitable cable, mounting adopter etc
Sealing :- The modem cover and body should have arrangement for sealing. In addition
to this, the SIM card holder cover should also have arrangement for sealing.
Antenna :- The Modem should have flexible external antenna to enable placement of the
antenna at the location of strongest signal inside the Metering Cubicle. Bidders are
requested to quote separately for multiple gain antenna, such as OdBi/3dBi/10dBi with
screw mount / Wall mount arrangement. The actual requirement of these Modem
Antennas of various gains may vary as per the requirement at site. Bidder will be
required to supply the exact requirement as per site conditions and will be paid as per
the separate unit rated quoted for different Gain Antennas.
Before supply of GSM/CDMA modem, the bidder is requested to ensure the availability
of appropriate signal and operation of GSM/CDMA Modem in all the areas to be covered
by making physical survey or otherwise. Before making the actual supply of Modems
for FPI & FRTU locations , the Bidder is requested to assess the exact
requirement and should supply a high gain antenna or any other suitable alternate
communication network for collecting data in such area.
In the event of an outage, the modem should be able to initiate separate call or send SMS
to predefined number to notify the outage event with data and time of occurrence and
restoration
The Modem should act a completely transparent channel i.e. the Commands
received from SCADA/DMS Control center should be conveyed to FRTU/FPI and
data from FRTU/FPI should be conveyed to SCADA/DM control center without any
changes in the modem.
Data collection from FRTU/FPI should take place only after connection is established
between Control center and FRTU/FPI. Data should not reside in the modem before the
time of transmission to Control center, to avoid chances of tampering of data at Modem
end.
The Modem should be capable of operating with SIMs of local GSM/CDMA Service
provider in the area.
Modem should be capable for continuous working for 24 hours every day under field
conditions
Modem should be a compact model housed in a polycarbonate /engineering plastic
/ Metallic enclosure. The modem should comply with IP55 degree of protection for
FPI locations & IP41 for FRTU as the same shall be housed in the FRTU panel.
Modem should be Dual Band modem capable of operating at 900 and 1800 MHz
transmission. GSM Modem should support bothData and SMS transmission. It should
have both GSM and GPRS/MPLS-4G/EDGE feature
Modem should have an RS232 Interface through a 9 pin or 15 pin D type
Connector for connection to FRTU/FPI. The SIM interface should be a 3 V
Interface in accordance with GSM 11.12 phase 2 with a retractable SIM
cardholder, which should be fully inserted inside the modem. The holder opening
should have a sliding cover with provision for sealing after placing of the SIM card.
The modem shall accept the standard SIM Card. Modem should have a SMA
Antenna connector
Storage Temperature : -20 degrees to +70 degree Celsius
Operating Temperature: -10 degrees to +60 degree Celsius
Humidity:- 95% RH ( Non - Condensing)
Utility may specify location with altitude more than 2000m above MSL for
compliance of FRTUs to be installed in that project area
Maximum Power Output should be 2 W at 900 MHz (Class 4) and 1W at 1800
MHz (Class 1).
Sensitivity :- GSM 900 : <-100 dBm GSM 1800 : <-100 dBm
Standard AT Command set (GSM 07.05, GSM07.07)
TCP/IP stack access via AT
Internet Services : TCP, UDP, HTTP, FTP, SMTP, POP3
Max. Baud Rate: for GSM -9600
GPRS/MPLS-4G Class B Multi slot class 12 or class B Multi slot class 10 Packet channel
support : PBCCH
EDGE (EGPRS/MPLS-4G) Multi slot class12 or Multi slot class 10Mobile station Class
B Modulating and coding schemes : MCS 1 to 9 Packet channel support : PBCCH
SMS Features: - Text and PDU Point to point (MT/MO, Cell broadcast
The Modem should have LED indications for transmit data, received data carrier detects
and Power ON, etc. to indicate Power on position and to indicate the availability of
signal at the place of installation.,
11.5 WAN router
RTU shall communicate with control center through MPLS network. The router specification
shall be suitable to communicate with Control center. Industrial Grade Router should support
QUAD core 1.2GHz CPU, DRAM of 2GB & usable Flash Memory of 2GB. Should support
WAN port on Combo Gigabit Ethernet (RJ45/SFP slot)Gateway should have Four
10/100BASE-T Fast Ethernet LAN ports with 4KV isolation for Electrostatic Discharge (ESD)
protection. Router should support 1 RS-232 serial ports Gateway should have mini Type B
USB Console port, Dual SIM for 3G/4G/5G
The Router should have built-in security features like SSL VPN for remote access, Next gen
encryption such as AES-256, SHA-384, and SHA-512, IP Sec tunells, NAT Transparency,
VRF Aware Ipsec and Ipsec over IPv6.
Gateway should also have built in firewall features like Zone based policy firewall, VRF-aware
stateful inspection routing firewall, Advanced application inspection and control, Dynamic and
static port security
Router should have SDWAN so that dynamic path selection feature can be achieved to select
the best available path out of multiple routes based on delay, jitter, and latency.
Router should support IPv6 name resolution, IPv6 DHCP and IPv6 NAT features, IP SLA,
OSPFv2 and OSPFv3, BGP & EIGRP.
Router should support IEC 60870 T101, T104 protocol translations. Comply with IEEE 1613
and IEC 61850-3 standards
Router should be able to operate in the temperature range of -40 to 60 degree celcius. Gateway
should support both In-band and out-of-band management using Telnet and SNMP, including
MIB II and other extensions. Hazardous certification : ANSI/ISA ,EN
End of Chapter 11
CHAPTER –12
TEST EQUIPMENTS FOR RTU/FRTU
12.0 RTU/FRTU Configuration and Maintenance Tool
Test equipment for RTU/FRTU shall have Configuration and maintenance tool consisting of
the followings:
12.1 RTU/FRTU Data base configuration & Maintenance software tool
The RTU/FRTU database configuration & Maintenance software tool shall be required to
perform the database modification, configuration, compilation and documentation. The
database compiler shall provide error detection services. It shall also perform the downloading
of the compiled database into the RTU database.
12.2 Master station-cum-RTU/FRTU simulator & protocol analyzer software tool
The Master station cum RTU/FRTU simulator tool shall be used to test the communication
interfaces of Master station, RTU/FRTU and Electronic MFT. The Master station simulator tool
shall be capable of emulating the master station for IEC 60870-5-104,101 and MODBUS
protocols. The RTU/FRTU simulator shall be capable of emulating the slave protocols for both
the IEC 60870-5-104,101, and MODBUS protocols for MFTs. It shall also be possible to
prepare illegal messages for transmission, such as messages having invalid checksum.
The protocol analyzer shall be used to monitor all communication traffic on a channel (between
Master station & RTU/FRTU and between RTU/FRTU & MFT without interfering channels
operation. Channel traffic captured in the active or passive modes of operation shall be
displayed.
The Master station simulator and protocol analyzer tool shall also have following features:
Each received message shall be checked for validity, including the check sum.
The tool shall maintain and display error counters so that the number of errors
during a period of unattended testing can be determined.
All fields of a message shall be displayed. A pass/fail indication for the
message shall be included.
In case of usage of IEC 103/61850/ IEC62056 for data acquisition, the feature of the same also
be provided with same or additional tool
12.3 Laptop PC for above software tools along with interfacing hardware
A laptop PC shall be used for the above mentioned software tools. The laptop PC shall be provided
with all hardware accessories including cables, connectors etc. required for interfacing with
Master station, RTU/FRTU and MFT. A suitable Hub shall be provided to use the tool in monitor
mode. A carrying case and a suitable power adaptor (input 230VAC, 50Hz) for laptop PC shall
also be supplied.
End of Chapter 12
13.2 Documentation
The Contractor shall submit 3 sets of all the standard and customized RTU/FRTU documents for
review and approval which includes the following:
a) RTU/FRTU Function design document
b) RTU/FRTU Hardware description document & all the documents referred
therein to meet all the clauses of the specification.
c) RTU/FRTU Test equipment user documents d) RTU/FRTU user guide
d) RTU/FRTU Operation & Maintenance document f) RTU/FRTU Training
documentation
e) RTU/FRTU database document h) RTU/FRTU I/O list
f) RTU/FRTU Test procedures
g) Data Requirement Sheet (DRS) of all items
h) Protocol documentation including implementation profile etc.
i) RTU/FRTU installation and Layout, GA, BOQ, schematics and internal wiring
drawings for each RTU/FRTU site
j) RTU/FRTU to C&R panels/ field device cabling details for each RTU/FRTU Site
k) Cyber security compliance certificate /document by manufacturer incl
international agencies like KEMA / TuV etc.
After approval of all the above documents, the Contractor shall submit three sets as final
documents. The site-specific drawings as indicated at item (i) and (j) above shall be submitted
in three sets for each site before installation of RTU/FRTU. In case some
modifications/corrections are carried out at site, the contractor shall again submit as built site-
specific drawings in three sets after incorporating all such corrections as noticed during
commissioning of the RTU/FRTU.
Table-1: List of Tests on RTU/FRTU
Test DESCRIPTION OF THE TEST Type Routine Field
Nos. test test test
A FUNCTIONAL TESTS FOR RTU/FRTU
1. Check for BOQ, Technical details, Construction & Wiring as per √ √ √
RTU/FRTU drawings
2. Check for database & configuration settings √ √ √
Check the operation of all Analog inputs, Status input & Control √ √ √
3. output points of
RTU/FRTU
4. Check operation of all communication ports of RTU/FRTU √ √ √
Check for communication with master stations including remote √ √
5. database downloading from master station
6. Check for auto restoration of RTU/FRTU on DC power recovery √ √
after its failure
7. Test for self-diagnostic feature √ √
(Test 33)
Power frequency
Level 30 A/m of magnetic field strength
magnetic field ON A
3 (Continuous duration sine wave)
(Test 34)
Power frequency No break
voltage withstand down or
(Test 35) OFF - 1 KVrms for 1 minute flashover
shall
occur
1.2/50μs impulse No break
voltage withstand down or
(Test 36) OFF - flashover
2 kVp shall
occur
Insulation Measure Insulation resistance using As per
Resistance 500 V DC Megger before & after manufact
OFF -
Test Power Freq & Impulse voltage urer
(Test 37) withstand tests standard
Dry heat test Continuous operation at 550 C for 16
ON - 0
(Test 38) hrs
Damp heat test
ON - at 95% RH and 400 C 0
(Test 39)
End of Chapter 13
14.0 General
This chapter describes the technical requirements for Auxiliary Power Supply System. The
BOQ for Auxiliary Power Supply system equipments required for SCADA/DMS control
center, RTU/Data Concentrator, FRTU Communication equipment & remote VDU locations
The components of Auxiliary Power Supply system are Uninterruptible Power Supply (UPS),
48V DC power supply (DCPS), the batteries for UPS and DCPS. The technical requirements
for all the above components are described in the various subsequent clauses.
The Bidder is encouraged to offer their standard products and designs. The UPS, DCPS,
Battery shall be manufactured & tested as per the relevant IS/IEC/ EN/BS standards. However,
the Bidder shall conform to the requirements of this specification and shall provide any special
interface equipment necessary to meet the requirements stated herein.
All equipment except Batteries shall be designed for an operating life of not less than 15 years,
however, batteries shall have a minimum expected operating life of 5 years under normal
operating conditions or 1200 charge/discharge cycles (whichever is earlier). The Contractor
shall demonstrate the functionality of the equipment during tests in the factory. After the
equipment is installed, the Contractor shall demonstrate all of the functions during well-
structured field tests. This chapter is applicable to Group A, B, C towns as per functional
requirements
14.1 Uninterruptible Power Supply (UPS)
The technical requirements for the Uninterruptible Power Supply (UPS) System and
associated equipments to be provided by the contractor are described below.
The UPS system shall include the following:
UPS equipments supplying load at 0.8 lagging power factor
VRLA batteries for UPS system with backup duration
UPS input and output AC Distribution Boards.
Power, control and network cables
14.1.1 UPS Functions
The UPS shall be designed for continuous-duty, on-line operation and shall be based on solid-
state design technology to provide uninterrupted power supply for computer system and
associated items. The control of the UPS system shall be microprocessor based providing
monitoring and control of rectifier/charger, Inverter, static switches, firing and logic control.
Each UPS system provided by the Contractor shall include all of the following sub- systems
as well as any other components and support hardware necessary for complete and proper
operation of the UPS:
a) Rectifier/charger unit Inverter unit
b) Battery Low Voltage Disconnect device
c) Static bypass switches
d) Manual maintenance bypass switches
e) Isolation transformer
14.1.5 Invertors
The invertors shall normally operate in synchronism with the mains AC power source. Upon
loss of the mains AC power source or its frequency deviating beyond a preset range, the
invertors shall revert to their own internal frequency standard. When the mains AC source
returns to normal, the invertors shall return to synchronized operation with the mains AC source.
Such reversal of operation of inverters from synchronous to free running mode and vice-versa
shall not introduce any distortion or interruption to the connected loads. A suitable dead band
for frequency may be provided to avoid unnecessary frequent reversal of inverter operation
between free running mode and synchronized mode under fluctuating frequency conditions.
The invertors shall have the following characteristics:
(a) Inverter unit shall be based on Pulse Width modulation (PWM) technique.
(b) The nominal output voltage shall be 415 Volt ±1%, 3-phase, 4-wire AC up to
rated load.
(c) The transient voltage response shall not exceed 4% for the first half-cycle
recovering to 1% within ten cycles for a 100 percent step load application or
removal.
(d) The free running frequency shall not deviate by more than + 0.1 % for the rated
frequency of 50 Hz.
(e) The invertors shall be synchronized to the main AC source unless that source
deviates from 50 Hz by more than 1% (adjustable to 1/2/3/4/5 %).
(f) The output voltage harmonic distortion shall not exceed 5% RMS and no single
harmonic component shall exceed 3%.
(g) The invertors shall be capable of resistive load operation & deliver at least 80%
of the nominal capacity at the rated power factor and be capable of operation
with loads ranging from the rated through unity power factor. Inverter shall also
accept 100% load at crest factor of at least 3:1 for Switching Mode Power
Supply (SMPS) load of computer system equipments without de-rating.
(h) The invertors shall provide protection logic to automatically shut down and
isolate itself from the load when the battery voltage drops below a preset
voltage.
(i) The invertors shall provide interrupter switch to isolate the unit from the load
on failure of the unit. The interrupter switch shall be rated to carry full continuous
load and to interrupt the inverter under full fault load.
(j) The invertors shall be capable of supporting a start-up surge or overload of 150
percent of rated output for up to 60 seconds.
In case the inverter subsystem does not include an internal load transformer, an external load
transformer of delta-wye configuration, 3-phase, 50Hz, 415 V AC, suitable for the inverter shall
be provided.
14.1.6 Static Bypass Switches
Each UPS system shall include static bypass switch to facilitate automatic transfer of loads
from the inverter sub-system output to bypass AC source though isolation transformer.
Isolation transformer shall be rated for at least two times the rating of single UPS sub system.
However, in case of parallel-redundant UPS systems, the transfer to Static bypass must occur
only when the invertors of both the UPS systems have failed.
The transfer to Static Bypass from the inverter shall take place under the following fault
conditions:
(a) The inverter load capacity is exceeded
(b) An over- or under-voltage condition exist on the inverter output
(c) Inverter failure.
The static bypass switches shall be high-speed devices rated to transfer and carry full rated
load. The static bypass switches shall provide protection to prevent out of phase transfers. The
switching speed of the static bypass switches shall be less than 1 millisecond. During the
changeover, the output voltage should not fall below 205V A.C, 50Hz +5%, in order to avoid
any disruption to computer load supply. An automatic transfer back to the inverter subsystem
shall occur if the transfer from the inverter subsystem was caused by a temporary overload and
the load has returned to normal or by a temporary over/under voltage condition on inverter
output and the voltage has returned to normal.
The transfer back to the inverter subsystem, both automatic and manual, shall be inhibited
under the following conditions:
a. The frequency of bypass AC source is outside the frequency band of ± 1% of
50Hz (adjustable to 1/2/3/4/5 percent).
b. The inverter output voltage and frequency are beyond the preset
range.
c. An overload exists.
14.1.7 Manual Maintenance Bypass Switches
Manual bypass switches are provided to facilitate maintenance of the UPS system and shall
provide transfer of the connected load from one UPS output to the other UPS system. These
switches shall be rated to transfer and carry continuous full rated load.
14.1.8 Batteries
UPS system shall have a set of storage batteries designed for continuous UPS application. The
battery set shall have sufficient capacity to maintain output at full rated load for the specified
backup duration after 8 hour charging. The backup duration of the battery shall be as specified
in the BOQ. The battery set shall be maintenance free VRLA type Batteries. The detailed
requirement of batteries is given under clause 14.4.
14.1.9 Battery Breaker for UPS system
A 2-pole MCCB of suitable rating shall be provided near the battery bank (at suitable location
on the frame of the battery bank) to allow disconnection of the batteries from the
rectifier/charger unit and inverter. This shall also provide over-current protection to the battery
circuits.
14.1.10 UPS Control/Monitoring
The Contractor shall supply control panel to permit automatic & manual operation of UPS,
display of associated alarms and indications pertaining to the UPS. In each UPS system, a local
display of the following analog and status/alarm signals/indications as a minimum shall be
included Analog signals for the following measurements:
AC input voltage (to display each phase)
i. AC output voltage (to display each phase)
connections.
14.1.15 Testing of UPS
14.1.16 Type Test of UPS
The Contractor shall supply type tested UPS equipments. The Contractor shall submit the UPS
type test reports of earlier conducted tests (including performance & EMC requirements) on
the same make, model, type & rating as offered, as per IEC 62040 or equivalent EN/BS
standards. For type testing requirements in addition to provisions of chapter 18 is also to be
complied.
14.1.17 Factory Acceptance Test of UPS
A factory acceptance test shall be conducted on all the equipments and shall include, but not
be limited to the following, appropriate to the equipment being tested:
(a) Verification of all functional characteristics and requirements specified
(b) Voltage drop and transients generated during switching operations
(c) System efficiency tests
(d) Verification of all features and characteristics included in all the delivered
equipments and also as per specification requirements.
(e) Inspection and verification of all construction, wiring, labeling
14.1.18 Documentation, and completeness of the hardware
Before the start of factory testing, the Contractor shall verify that all change orders applicable
to the equipment have been installed. As a part of the factory tests, unstructured testing shall
be performed to allow Employer representatives to verify proper operation of the equipment
under conditions not specifically tested in the above structured performance test. A minimum
of 8 hours of the factory test period shall be reserved for unstructured testing. The Contractor's
test representative shall be present and the Contractor's technical staff members shall be
available for consultation with Employer personnel during unstructured test periods. All
special test facilities used during the structured performance test shall be made available for
Employer’s use during unstructured testing.
The respective factory acceptance tests for UPS are listed in Table 4.1
14.1.19 Environmental Conditions
UPS & all other hardware and components shall be capable of continuous operation at rated
load without failures in the following environmental conditions:
Temperature/humidity - Ambient temperature of 00 to 500C and upto 95 percent humidity,
non-condensing. However, air conditioned environment shall be provided for VRLA batteries.
loads in the control center. The number of feeders and their ratings in the output ACDB shall be
decided during detail engineering. At least five spare feeders in the output panel shall be
provided.
All MCCBs shall conform to IEC-60947-2 & IS 13947-2/IEC 947-2, IEC-60898 and IS8828
and shall be of Four (4) Pole type of requisite rating. MCBs used for load feeders in output
ACDB shall be of minimum curve B characteristics. The load feeders shall be coordinated with
requirement of loads of computers and other loads.
14.2.1 Enclosures/Panels
The equipments of ACDBs shall be physically mounted in freestanding enclosures/panels.
MCCBs and sub-assemblies shall be easily replaceable and maintainable. Cable entry shall be
from the bottom/top of the enclosures (to be finalized during detailed engineering). The
Contractor shall state the type, size and weight of all enclosures and indicate the proposed
manner of installation. The applicable degree of protection of enclosures shall be at least IP21.
The thickness of the structural frames and load bearing members shall be minimum 2.0 mm and
for front & rear, sides and top covers shall be minimum 1.6 mm. For wall mounted type of
output ACDB the above requirements shall not be applicable.
14.2.2 Equipment/Panel Earthing & Surge Protection
Each enclosure shall include suitable safety earth networks as per clause 14.2.3.5. . Surge
protection devices shall be installed in the input ACDB to provide adequate protection against
current and voltage transients introduced on input AC due to load switching surges. These
protection devices shall be in compliance with IEC- 61312, IEC- 61024 and VDE 0100-534
for following surges:
a) Low Voltage Surges (Class C)
Between Requirement
R, Y, B & N In ≥ 10 kA, 8/20 µS for each phase
N & PE In ≥ 20 kA, 8/20 µS
In= Value of Nominal Discharge Current.
14.2.3 Cabling Requirements
The contractor shall supply, install and commission all power cables, control cables, network
interface cables and associated hardware (lugs, glands, cable termination boxes etc.) as
required for all equipment. The contractor shall be responsible for cable laying and termination
at both ends of the cable. The Contractor shall also be responsible for termination of owner
supplied cables if any at contractor’s equipment end including supply ofsuitable lugs, glands,
terminal blocks & if necessary cable termination boxes etc. All cabling, wiring and
interconnections shall be installed in accordance with the following requirements.
14.2.3.1 Power Cables
All external power cables shall be stranded aluminum/Copper conductor, armoured
XLPE/PVC insulated and sheathed; 1100V grade as per IS 1554 Part-I. The conductor for the
Neutral connection from UPS to Output ACDB shall be sized 1.8 times the size of the Phase
conductors to take care of the non-linear loads. However, the cable between UPS & Battery
bank shall be of copper conductor (armoured type).
14.2.3.2 Cable Identification
Each cable shall be identified at both ends, which indicates the cable number, and the near-end
and far-end destination. All power cables shall have appropriate color for identification of each
phase/neutral/ground. Cable marking and labelling shall comply with the requirements of the
applicable standards.
14.2.3.3 Cable and Hardware Installation
The Contractor shall be responsible for supplying, installing, and terminating all cables and
associated hardware (lugs, glands, etc.), required to mechanically and electrically complete the
installation of facilities for the project.
14.2.3.4 Enclosures/Panels design
Enclosures/panel shall be of freestanding type of design. Cable entry shall be from the
bottom/top of the enclosures (to be finalized during detailed engineering). The enclosures shall
not have doors that are wider than 80 cm and doors shall be hinged with locking as per standard
design of the manufacturer. Keyed locking is required with identical keys for all enclosures.
The enclosures shall not exceed 220 cm in height. The thickness of the structural frames and
load bearing members shall be minimum 2.0 mm and for others shall be minimum
1.5 mm. The panels/boards shall be equipped with necessary cable gland plates. The Contractor
shall state the type, size and weight of all enclosures and indicate the proposed manner of
installation.
Wiring within panel shall be neatly arranged and securely fastened to the enclosure by non-
conductive fasteners. Wiring between all stationary and moveable components, such as wiring
across hinges or to components mounted on extension slides, shall allow for full movement of
the component without binding or chafing of the wire. Conductors in multi-conductor cables
shall be individually color coded, and numbered at both ends within enclosures.
The enclosures shall be painted inside and outside. The finish color of all enclosures shall be
aesthetically pleasing and shall be approved by the owner. Further, finish color of external
surfaces shall be preferably of same color for all enclosures/panels.
Maintenance access to the hardware and wiring shall be through full height lockable doors.
Each panel shall be supplied with 240 VAC, 50Hz single-phase sockets with switch. Each
ACDB and equipment within ACDB enclosures shall be clearly labelled to identify the
enclosure/equipment. All labelling shall be consistent with Contractor-supplied drawings.
14.2.3.5 Enclosure/Panel Earthing
Each enclosure shall include suitable earth networks within the enclosure. Earth network shall
be a copper bus bar, braid or cable inside enclosures.
The safety earth network shall terminate at two/more studs for connecting with the earthing
grid. Safety earthing cables between equipment and enclosure grounding bus bars shall be of
minimum size of 6 mm2, stranded copper conductors, rated at 300 volts. All hinged doors shall
be earthed through flexible earthing braid.
For all enclosures requiring AC input power, the green earthing wire from the AC input shall
be wired to the safety-earthing stud. The Contractor shall provide all required cabling between
enclosures for earthing. The contractor shall connect safety and signal earths (as applicable) of
each enclosure to the nearest earth grid/earth riser through suitable 50X6 sq. mm. GI/25x3 Cu
strips. The contractor may use the existing grid wherever available. In case the suitable earthing
grid is not available the same shall be made by the contractor.
The signal earthing network shall terminate at a separate stud connection, isolated from safety
ground. The stud connection shall be sized for an external earthing cable equipped with a
suitable lug.
All earthing connections to equipment shall be made directly to each equipment chassis via
earthing lug and star washer. Use of the enclosure frame, skins, or chassis mounting hardware for
the earthing network is not acceptable.
14.3 DC Power Supply System
The DC Power Supply system shall be capable of meeting the load requirements for various
Telecom equipments, RTUs and other associated equipment located at indoor, i.e. at the
substations, the control centers and customer care system. The AC input to the ACDB shall be
provided from the ACDB described under clause 14.2 at control center. At other locations the
AC input to the DCPS system shall be single phase AC which will be provided from the existing
system. At these locations the class B & C level of surge protection (between phase-neutral and
neutral – protective earth) as specified under and conforming to IEC 61312, IEC 61024 and
VDE 0100-534 shall be installed in the DCPS system.
Surge protection devices shall be installed in the DCPS panel to provide adequate protection
against current and voltage transients introduced on input AC due to load switching and low
energy lightning surges. These protection devices shall be in compliance with IEC- 61312,
IEC- 61024 and VDE 0100-534 for following surges:
a) Lightning Electromagnetic impulse and other High Surges (Class B):
Between Requirement
Ph & N Iimp ≥ 50 kA, 10/350 µS for each phase
N & PE Iimp ≥ 100 kA, 10/350 µS
Iimp= Value of Lightning Impulse Current
The system shall be sufficiently flexible to serve any load depending on manufacturer‟s design,
rating and number of SMPS modules used in panel and system configuration. To cater for
higher load requirements, same type of SMPS modules mounted in the same rack or different
racks shall be capable of working in parallel load sharing arrangement. The DCPS system shall
be suitable for operation from single phase A.C. mains.
14.3.2 Operational/Component Requirements
The basic modules shall operate at specified ratings and conform to requirements stipulated in
this specification. The DCPS system shall meet requirement of the latest TEC specification /
IEC/BS for other parameters not specified in this specification. The component parts of the
equipment shall be of professional grade of reputed manufacturer to ensure prompt and
continuous service and delivery of spare parts. The component shall confer to relevant IEC/IS
standards. The contractor shall obtain Employers approval of major component before
procurement of the same. Conceptual diagram is for DCPS is shown in figure 4-2.
The DCPS shall be suitable for operation at ambient temperature of 0-50 deg and relative
humidity up to 95 %. Utility may specify requirements as per site conditions
14.3.3 Wiring
All insulated conductors except those within the confines of a printed circuit board assembly
shall be of the rating enough to withstand the maximum current and voltage during fault and
overload. All insulated conductors/cables used shall conform to IS 1554 or equivalent
international standard.
All wiring shall be neatly secured in position and adequately supported. Where wires pass
through any part of metal panel or cover, the hole through which they pass shall be suitably
secured.
14.3.4 Bus Bars
High conductivity Cu bus bar shall be provided and shall be sized to take care of the current
of ultimate DCPS system capacity for which it is designed. However, it shall not be less than
25mm X 5mm.
14.3.5 Earthing
Two earth terminals shall be provided in the frame of the system. The Contractor shall connect
these earth terminals to the earth bus. All modules and devices shall be connected to these
earth terminals. The hinged door shall be connected to the panel with braided Cu at two points
at least.
14.3.24 Termination
Suitable termination arrangements shall be provided in the panel for termination of inter cubicle
cables from other equipment such as owners ACDB, Telecom and other associated equipments
and alarm cables. All the termination points shall be easily accessible from front and top. AC
and DC terminals shall be separated by physical barriers to ensure safety. All theterminals
except AC earth shall be electrically isolated.
14.3.25 4.3.25 DC Terminations
All terminations including through MCBs shall be through lock and screw type terminations.
Load and batteries shall be connected to DCPS through appropriate MCBs. The isolation of
any of the battery from the load shall create an alarm. DC distribution shall be provided with
adequate no of feeders (with three no of spare) with appropriate MCBs (6 Amp thru 32 Amp)
for termination of the loads. Actual rating of the MCBs and no of feeders shall be finalized
during the detail engineering.
DC distribution may be done either on wall mounted panel or on the DCPS panel. The proper
rated MCB shall be provided at the combined output of the SMPS modules (if not provided at
each SMPS module). All the AC, DC and Control/alarm cabling shall be supplied with the
Panel. All DC +ve and –ve leads shall be clearly marked. All conductors shall be properly
rated to prevent excessive heating.
14.3.26 Power Cables
All power cables shall be stranded copper conductor XLPE/PVC insulated and PVC sheathed,
single core/two core/three core/four core, 1100V grade as per IS 1554 Part-I.
14.3.27 Earthing Cables
Earthing cables between equipment and grounding bus bars shall be minimum size 70 mm2
stranded conductors copper/copper strip, rated at 300 volts. All hinged doors shall be earthed
through flexible earthing braid. Signal and Safety earthing shall be provided separately.
14.3.28 Alarms
Following Visual indications/display such as LEDs, LCDs or a combination of both shall be
provided to indicate:
Functional Indications for local monitoring:
a) Mains available (not mandatory if provided at module level)
b) DCPS/SMPSs in Float
c) DCPS/SMPSs in Charge Mode
Alarm Indication for local monitoring:
a) Load Voltage High /Low
b) DCPS module/SMPS fail
c) Mains out of range
d) System Over Load
e) Mains “ON”/Battery Discharge
f) Temp. Compensation fail
g) Battery fail/isolated
on discharge to its rated capacity. The battery sets shall have a minimum expected operational
life of 5 years at normal operating conditions or 1200 charge / discharge cycles (whichever is
early).
14.4.12 Routine Maintenance of Battery system
For routine maintenance of battery system, the contractor shall supply 1 set of following tools:
a. Torque wrench.
b. Tool for opening /closing of pressure regulation valve of battery.
c. H a n d held digital Multimeter for measurement of resistance, AC/DC
Voltages.
14.4.13 Testing of Battery
The contractor shall supply type tested battery as required for DCPS and UPS system. The
Contractor shall submit the Battery type test reports of earlier conducted tests on the same
make, model, type & rating as offered as per the IEC 60896 or equivalent IS/EN/BS standards.
These Type test reports shall be submitted for the highest rating battery to be supplied under
the contract. For type testing requirements in addition to provisions of this chapter 18 is also
tobe complied. The tests mentioned in the Table 4.2 shall be conducted on the battery at site
andfactory.
14.7 Documentation
The following specific document for items covered under this chapter shall be submitted which
shall be in addition to the applicable general document required under chapter 18
Data Requirement Sheets (DRS)
Battery sizing calculations
Cable sizing calculations
Inventory of the hardware
Panel General Arrangement drawing
Panel Internal General Arrangement drawing indicating modules, major
devices/components location etc.
Installation drawings
Schematic drawings
Type Test reports
End of Chapter 14
All outdoor metal enclosures shall be treated in 7 tank Pre-treatment process &
should be painted with UV Resistant Pure Polyester Powder coating. The
powder coated sheet steel fabrication shall fulfill 700 Hrs of Salt spray test. The
thickness of Painting/Powder coating shall be of 100+/-25 microns to withstand
tropical heat and extremes of weather.
15.1.8.3 Immunity to Electrical Stress and Disturbance
The electrical and electronic components of the RMU shall conform to relevant standards
concerning insulation, isolation, and the product shall comply with IEC 60270 Immunity
to electrical stress & disturbance. The ability to meet these requirements shall be verified by
type tests carried out by accredited test laboratories that are independent of the bidder and/or
the manufacturer of the RMU components. Certified copies of all available type test
certificates and test results shall be included as part of the bidder’s proposal.
15.1.8.4 Minimum Insulation of Equipment
The RMUs shall be of SF6 gas-insulated type with a maximum gas operating pressure up to
1.2 BAR @ 20 deg C.
15.1.8.5 Nameplate Information
RMU nameplate information shall be determined in agreement with the Employer. This
information may include for example:
Name of manufacturer and country
Type, design, and serial number
Rated voltage and current
Rated frequency
Rated symmetrical breaking capacity
Rated making capacity
Rated short time current and its duration
Rated lightning impulse withstand voltage
Purchase Order number and date
Month and year of supply
Each RMU shall also exhibit a Danger Board to indicate the presence of high voltage
(11,000 V).
15.1.9 Interconnecting Cables, Wiring, Connectors, and Terminal Blocks
The Contractor shall provide all interconnecting wires, cables, connectors, terminations and
other wiring accessories such as terminal blocks required by the RMU.
15.1.9.1 Metallic Cables
All metallic cables and wiring shall be of required cross-section solid or multiple strands of
round copper conductors and have flame retardant insulation. All wiring shall be neatly laced
and clamped.
All wire and cable connectors and terminators shall be permanently labeled for identification.
All connection points for external cables and wires shall be easily accessible for connection
Parameter Value
Parameter Value
Parameter Value
Parameter Value
The RMU switchgear shall be capable of withstanding the specified currents without damage
in accordance with the latest versions of IEC 60694 (Common Specifications for High-
Voltage Switchgear and Control Gear Standards) and IS 3427 (AC Metal Enclosed
Switchgear and Control Gear for Rated Voltages above 1 kV and up to and including 52 kV).
The equipment offered shall be as per the standards specified in the bid specification
and if the offered equipment is tested with any other international standards which is
superior to the standards specified they can also be considered and the bidder has to
submit the documentary evidence for the same to Utility
15.1.13 Design Details
The RMU shall be designed to operate at the rated voltage of 12 kV.
It shall include, within the same metal enclosure, On-load break switch, circuit breakers and
earthing switches for each Load Break Switch/Circuit Breaker.
Suitable fool-proof interlocks shall be provided to the earthing switches to prevent inadvertent
or accidental closing when the circuit is live and the concerned Load Break Switch/Circuit
Breaker is in its closed position.
The degree of protection required against prevailing environmental conditions, including
splashing water and dust, shall be not less than IP 54 as per IS 12063.
The active parts of the switchgear shall be maintenance free. Otherwise, the RMU shall be of
low-maintenance type.
The tank shall be made of minimum 2.0 mm thickness of stainless steel.
The Stainless Steel tank should be completely welded so as to ensure IP 67 degree of
protection and shall be internal arc tested.
The RMU shall be suitable for mounting on its connecting cable trench.
For each RMU enclosure, a suitably sized nameplate clearly identifying the enclosure and the
electrical characteristics of the enclosed devices shall be provided.
The access to the cable compartment should be from the front of the switchgear only to
have minimum operating & maintenance space at site.
The RMU design shall be such that access to live parts shall not be possible without the use
of tools.
The design shall incorporate features that prevent any accidental opening of the earth switch
when it is in the closed position. Similarly, accidental closing of a Circuit Breaker or Load
Break Switch shall be prevented when the same is in an open position.
The RMU tank must be equipped with a suitable pressure relief device. The pressure relief
must ensure that the escaping gases are dissipated to the rear / top/ bottom of the switchgear.
The complete RMU shall be tested in an accredited INDIAN or FOREIGN laboratory and
designed for an Internal Arc.
15.1.14 Earthing
There shall be continuity between metallic parts of the RMUs and cables so that there is no
dangerous electric field in the surrounding air and the safety of personnel is ensured.
The RMU frames shall be connected to the main earth bars, and the cables shall be earthed
by an Earthing Switch having the specified short circuit making capacity.
The Earthing Switch shall be operable only when the main switch is open. In this respect, a
suitable mechanical fail-proof interlock shall be provided.
The Earthing Switch shall be provided with a reliable earthing terminal for connection to an
earthing conductor having a clamping screw suitable for the specified earth fault conditions.
The connection point shall be marked with the earth symbol. The flexible connections
between the earthing blade and the frame shall have a cross-section of at least 50 mm2 copper
or equivalent in GI
The Earthing Switch shall be fitted with its own operating mechanism. In this respect, manual
closing shall be driven by a fast acting mechanism independent of the operator's action.
15.1.15 Incomer Load Break Switches
The Load Break Switches shall be maintenance free. With outdoor canopy doors open, the
position of power contacts and earthing contacts shall be clearly visible from the front of the
RMU through the Mimic facia.
The position indicator shall provide positive contact indication in accordance with IS 9920.
In addition, the manufacturer shall prove the reliability of indication in accordance with IS
9921. These switches shall have three positions (or states), i.e., Open, Closed, and Earthed,
and shall be constructed in such a way that natural interlocking prevents unauthorized
operations.
The switches shall be fully assembled, tested, and inspected in the factory.
In case of Manual operation without motors, opening and closing shall be driven by a fast-
acting mechanism independent of manual operator action.
The Load Break Switches shall be provided with a motorized operating mechanism suitable
for SCADA control.
A facility shall be provided with an electrical operating mechanism allowing an operator at
the RMU site to operate the Load Break Switches without any modification of the operating
mechanism and without de-energizing the RMU.
The switch and earthing switch mechanisms shall have a mechanical endurance of at least
1,000 operations.
15.1.16 Circuit Breakers
The Circuit Breakers shall be maintenance free and, when standing in front of the RMU with
outdoor canopy doors open, their positions shall be clearly visible, through the Mimic facia.
The position indicator shall provide positive contact indication in accordance with IS 9920.
The breakers shall have three positions (or states), i.e., Open, Closed, and Earthed, and shall
be constructed in such a way that natural interlocking prevents unauthorized operations. They
shall be fully assembled, tested, and inspected in the factory.
An operating mechanism shall be used to manually close the Circuit Breaker and charge the
mechanism in a single movement. It shall be fitted with a local system for manual tripping.
There shall be no automatic reclosing. The Circuit Breaker shall be capable of closing fully
and latching against the rated making current. Mechanical indication of the OPEN, CLOSED,
and EARTHED positions of the Circuit Breaker shall be provided.
Each Circuit Breaker shall operate in conjunction with a suitable protection relay under
transformer feeder/ circuit phase and earth fault conditions. In addition, the Circuit Breaker
shall be provided with a motorized operating mechanism that can be remotely controlled by
the SCADA.
15.1.17 Cable Termination
Bushings shall be conveniently located for working with the specified cables and shall allow
for the termination of these cables in accordance with the prevailing practice and guidelines
of cable manufacturers. The dimensions of the terminals shall be in accordance with IS 10601.
A non-Ferro-magnetic cable clamp arrangement shall be provided for each cable to be
terminated in the RMU.
A suitable arrangement for the Circuit Breakers, Earthing Switches, and Load Break Switches
shall be provided so that these devices can be padlocked in the "Open" and "Closed" positions.
A permanent "Live Cable" indication as per IEC 61958 shall be provided for each cable using
a capacitor voltage divider.
It shall be possible to test the core or sheath insulation of the cables without disconnecting
the cables in the cable compartment, after accessing the cable compartment. The cable end
kits including the supply and erection is in the scope of the successful bidder.
Two earth pits of 10 ohms each shall be provided diagonally and earthing to the equipment
shall be done as detailed in the scope of supply.
15.1.18 Safety of Equipment
With respect to the RMU’s SF6-filled equipment, any accidental overpressure inside the
sealed chamber shall be limited by the opening of a pressure-limiting device in the enclosure
so that the gas will be released away from the operator and to the rear bottom or top of the
tank without endangering the operator or anyone else in the vicinity of the RMU.
All manual / motorized operations, monitoring of open/close position of switches/breakers,
live line indicators, FPI indication, SF6 gas pressure indication and access to the cable
compartment shall be carried out from the front of the RMU only.
15.1.19 Current and Voltage Transformers.
The RMU shall be provided with current and voltage transformers. These CTs & PTs shall
meet the electrical and mechanical ratings as per the relevant standards.
15.1.19.1 Current Transformers
3 Nos. ring type, single core CTs shall be provided in each incoming load break switch for
metering purposes. A similar arrangement shall be provided in each circuit breaker cable
compartment to mount a 3 Nos. single-core, ring type CT for protection purposes.
The CTs shall conform to IS 2705. The design and construction shall be sufficiently robust to
withstand thermal and dynamic stresses during short circuits. Secondary terminals of CTs
shall be brought out suitably to a terminal block, which will be easily accessible for testing
and terminal connections.
Further characteristics and features distinguishing CTs used for metering from CTs used for
protection are listed as follows:
15.1.19.1.1 CTs for Metering:
Material : Epoxy resin cast
Burden : 2.5VA
Ratio : 400-200-100/1 A
Accuracy Class : 0.5
15.1.19.1.2 CTs for Protection:
Material : Epoxy resin cast
Burden : 2.5VA
Ratio : 400-200-100/1 A
Accuracy Class : 5P10
The RMU’s other CTs / sensors, i.e., those used by Fault Passage Indicators (FPIs), shall be
supplied by the FPI manufacturer. These CTs/sensors shall be an integral part of the FPI’s
design to ensure that they properly match the requirements of the FPI.
15.1.19.2 Voltage Transformers
A 3 phase single or 3 nos. single phase potential transformers shall be provided. These should
be housed in a separate air insulated PT Panel, directly connected to the RMU through main
bus. The burden per transformer shall not be more than 50 VA and the voltage ratio shall be
11000 V/ root 3 /110 V/ root 3. The accuracy class shall be 0.5.
HRC fuses shall be provided on the HV side.
The PTs shall be of cast epoxy-resin construction, and they shall conform to IS 3156. Their
design and construction, in particular, shall be sufficiently robust to withstand the thermal
and dynamic stresses during short circuits.
15.1.20 Fault Passage Indicator for RMU
The FPI shall facilitate quick detection of faulty section of line. The fault indication may be
on the basis of monitoring fault current flow through the device. The FPI should be self-
powered and should have internal lithium battery for external indication and setting of FPI in
the absence of current.
15.1.20.1 The FPIs shall include:
Fault detection - Phase to phase and Phase to earth faults.
One potential-free output contacts for hardwiring to FRTUs. On this basis, the SCADA/DMS
will be able to monitor phase / earth fault condition.
Local fault indications - LCD display on FPI front panel along with LED indication on front
panel of RMU enclosure.
Multiple reset option –
End of time delay (Adjustable from 2 to 16 Hrs)
Remote reset (Via potential free input contact of FPI)
Manual reset (Reset button on front panel of FPI)
For IDMT delay multiplication, the Time Multiplier Setting (TMS) shall be adjustable from
0.01 to 0.1 in 0.01 steps.
The relay shall also be provided with:
1. Alphanumeric Liquid Crystal Display (LCD) for relay setting.
2. Communications via a MODBUS RS232/RS485 port to provide the FRTU (and hence
the DMS) with phase current measurements. It is also desirable that this same means of
communication can be used by the FRTU to send setting and control commands to the
relay.
3. Parameter change capability that is password protected.
4. LED indication on front panel eg battery , cable test
FPI shall have atleast 2000 hours of flashing hours and support site tEst functions
15.1.21 Power Supply and auxiliary power transformer
Each RMU shall be fitted with a power supply, including batteries and battery charger,
suitable for operating the motors of the On-load Isolators and Circuit Breakers. On this basis,
the following operational specifications shall apply:
The power supply unit shall conform to the following requirements:
1) Input: 230 V AC nominal from the RMU’s auxiliary power transformer allowing for
possible variations from 190 to 300 V AC
2) Output: Stable 24 V DC.
3) Batteries: 24 V DC (2 Nos of 12 V DC each) SMF VRLA.
The auxiliary power transformer shall be of suitable rating as per the load calculation and the
Auxiliary power transformer inputs shall be equipped with surge protection devices in
accordance with IEC 62305.
The 24 V DC batteries shall have sufficient capacity to supply power to the following devices
with a nominal backup of 4 hours:
1) RMU’s motors for a minimum of five (5) operations
2) RMU’s trip coils, close coils, FPI.
The batteries shall be of sealed lead acid VRLA and shall have a minimum life of five
(5) years at 25oC.
The battery charger shall be fully temperature compensated.
To prevent deep discharge of the batteries on loss of AC power source, the battery charger
shall automatically disconnect all circuitry fed by the batteries following a user-adjustable
time period or when the battery voltage falls below a preset value. If the battery voltage falls
below the preset value, the time to fully recharge all batteries shall not exceed twenty-four
(24) hours.
An automatic battery checking device shall be provided to check the battery’s health and
initiate a battery-failed alarm signal in case battery deterioration is detected. Such detection
may be based on comparing measurement values with set values (e.g., internal resistance,
voltage, etc.).
The battery charger shall be provided with an alarm displayed at the local control panel and
remotely at the DAS to account for any of the following conditions:
1) Low battery voltage 2 ) Charger failed
polyurethane based powder paint, the overall paint layer thickness including Zinc spraying
shall be of the order of 80 to 90 microns
A metal pocket attached to the inside of the front door to hold documentation, maintenance
log sheets, and other such information.
Door opening mechanism with built-in key-lock facility suitable for padlocking. An opening
mechanism that is less prone to breaking than a projecting door handle is preferred, e.g., a
push-button opening mechanism.
A grounding terminal including grounding bolt and lock washer for connecting a 50 mm 2
copper or galvanized steel grounding conductor. The grounding bolt and lock washer shall be
made of stainless steel/Zinc Passivated mild steel .
Means of preventing moisture from condensing on electronic components mounted inside the
enclosure proposed for housing the FRTU. If necessary, heaters providing adjustable
thermostat-control within the range 20 to 60 ºC shall be installed in the enclosure for this
purpose.
Means of protection against rain water, and high levels of airborne dust, should be provided.
Means of enabling the SCADA to monitor the open/closed status of the enclosure door. A
SCADA equipment alarm shall be produced whenever the enclosure door is open.
The outdoor RMU shall include having a minimum protection class of IP 54. It shall be tested
in accordance with the latest IEC 60529 standard.
The outdoor canopy shall have a hinged front access door with a two-point latch locking
system with a latch operating lockable handle. The door shall be fitted with a perimeter flange
and gasket (rubber or neoprene) to prevent the entrance of water. In addition, a means of
monitoring and indicating that the door is open shall be provided.
15.1.25 Motors
The RMU shall be fitted with spring charging 24V DC motors of high insulation class
allowing the circuit breakers and load break switches to be operated without manual
intervention.
In addition to allowing circuit breaker tripping by the RMU’s protection relays, the motorized
operating mechanism shall be suitable for remote control by the SCADA.
The motors along with the supplied control card and push buttons shall allow Utility’s
personnel to electrically operate the circuit breakers and load break switches at site without
any modification of the operating mechanism and without de-energizing the RMU.
15.1.26 Inspection and Test
Inspections and tests shall be performed to ensure RMU compliance with these Technical
Specifications. Responsibility for conducting the inspections and tests shall rest with the
Supplier. The Utility representatives will participate in the RMU inspections and will witness
the testing as described in the following sub-clauses.
15.1.26.1 Inspections
Utility’s representatives shall be allowed access to supplier’s facility where the RMU or its
parts are being produced or tested. Such access will be used to verify by inspection that the
RMUs are being or have been fabricated and tested in accordance with the Technical
Specifications.
The supplier shall give the utility’s representatives 15 days’ notice in writing concerning the
date and place at which the equipment will be ready for inspection or testing. The supplier
shall provide all the necessary assistance and facilities to utility’s representatives to carry such
inspections and test witnessing.
The supplier shall provide any and all documentation that is necessary to complete the
inspections. The representatives shall be allowed to inspect the supplier’s quality assurance
standards, procedures, and records. Inspections, as a minimum, shall include checks on
inventory, general appearance, cabling, drawing conformance, and labeling.
15.1.26.2 Test Procedures
The supplier shall provide test plans and detailed procedures for all required testing. The plans
and procedures shall ensure that each test is comprehensive and verifies proper performance
of the RMU under test and, in this respect, shall be submitted for review and approval by the
Utility.
The test plans shall include all routine tests and acceptance tests as per relevant BIS/IEC
standards and shall describe the overall test process including the responsibilities of the test
personnel and how the test results will be documented.
The test procedures shall describe the individual tests segments and the steps comprising each
segment, particularly the methods and processes to be followed.
15.1.26.3 Test Reports
The tenderers should, along with the tender documents, submit copies of all Type test
certificate of their make in full shape as confirming to relevant IS/IEC of latest issue obtained
from a International/National Govt. Lab/Recognized laboratory.
The above type test certificates should accompany the drawings for the materials duly signed
by the institution that has type test certificate.
The supplier shall maintain complete records of all test results. The records shall be keyed to
the test procedures.
Upon completion of each test, the supplier shall submit a test report summarizing the tests
performed and the results of the tests.
15.1.26.4 Factory Acceptance Test
A formal factory acceptance test shall be conducted to ensure that the RMUs have been
designed to meet the utility’s functional requirements in all respects. Utility representatives
shall witness the test on a representative RMU, and the test shall be carried out in accordance
with the supplier’s test plan and procedures as approved by the Utility. Should the factory
acceptance test prove unsatisfactory in any way, the Utility reserves the right to have further
tests conducted and, if applicable, request further improvements in the supplier’s RMU
design.
15.1.26.5 Routine Factory Tests
These tests shall be carried out during RMU manufacture as a quality control measure, i.e.,
to ensure each RMU to be delivered meets the Employer’s minimum requirements including
all relevant standards. Recording and reporting the routine test results shall be the
responsibility of the Supplier.
At the Utility’s discretion, Utility representatives will witness such testing. This may include
requesting the Supplier to perform tests on RMUs selected at random from each batch of
RMUs that the Supplier deems ready to be delivered to site. Should any such test prove
unsatisfactory, the Utility reserves the right to have further tests conducted and for delivery
not to take place until a mutually agreed course of action has been reached.
Further for additional reliability of the manufactured RMU it is mandatory to have the
complete assembled tank tested for partial discharge.
15.1.27 Operating Manuals
The Supplier shall submit, operating manuals for all RMU components including items such
as FPI, Relay, and other equipment provided by the bidder. These manuals shall be in English.
They shall include the RMU operating instructions. Context sensitivity shall be used to go
directly to the appropriate place in the manual.
The manuals shall be organized for quick access to each detailed description of the operator
procedures that are required to interact with the RMU functions. This shall include the
procedures to define, build, edit, and expand all data points provided with the RMU.
The manuals shall present in a clear and concise manner all information that operators,
including maintenance personnel, need to know to understand and operate RMUs
satisfactorily. The manuals shall make abundant use of diagrams and/or photographs to
illustrate the various procedures involved.
15.1.27.1 As-Built Documents and Drawings
The supplier shall submit as built documents including applicable drawings for review and
approval. All deliverable documents and drawings shall be revised by the supplier to reflect
the as- built RMU components including all the FPI, LLI & Relay. Any errors in or
modifications to an RMU resulting from its factory and/or site acceptance test shall be
incorporated. Within this same context, all previously submitted documents that are changed
because of engineering changes, contract changes, errors, or omissions shall be resubmitted
for review and approval. The successful bidder has to provide his quality document to Utility.
15.2 11 KV Auto-recloser
Description Standard
11 kV Auto recloser
Requirements for overhead, pad mounted, dry vault, and submersible ANSI/IEEEC37.60-
automatic circuit recloser and fault interrupters for AC systems 1981
(RI993) IEC 62271-111
Electrical relays IEC 60255
High-voltage alternating-current circuit breakers. Amendment No. IEC 60056:1987
1:1 992.
Degrees of protection provided by enclosures (IP Code). IEC 60529:1989
Description Standard
Auto reclosers
Requirements for overhead, pad mounted, dry vault, and ANSI/IEEEC37.60-1981/
submersible automatic circuit reclosers and fault interrupters IEC 62271-111
for AC systems (RI993)
Electrical relays IEC 60255
High-voltage alternating-current circuit breakers. Amendment IEC 60056:1987/ IEC 62271-1
No. 1:1 992.
Degrees of protection provided by enclosures (IP Code). IEC 60529:1989
The cabinet shall make provision for bottom entry of three cables (excluding the cable
connected to the AR). All holes shall be pre-punched, two with a diameter of 20 mm
and one with a diameter of 32 mm. The holes shall be suitably blanked off.
Ventilation holes shall be provided to drain water and avoid hydrogen build-up.
The cabinet shall be fitted with an external M12 earthing stud with a nut, lock nut and
a serrated washer.
The door of the cabinet shall be fitted with a robust locking arrangement that is capable
of being secured by a padlock that has a shackle of 10 mm diameter. A minimum of
two latching points shall be provided. The cabinet door shall be removable for
replacement in the field.
A door stay shall be fitted to keep the door open while operators are attending the unit.
Front door entry shall allow access to the operator interface, accessory equipment and
communication cables. If an internal swing panel is fitted, the panel shall have a door
stay fitted, shall weigh less than 5kg, shall not have any sharp edges and there shall not
be any danger of pinching or guillotining an operator’s fingers or hands
All connections that could potentially expose the operator to dangerous voltages will
be shielded to IP2X. These connections include the terminals used for current
transformers, primary power supply and voltage measurement inputs.
The controller shall provide following integrated features:-
Local human machine interface (HMI) shall be menu driven via 6 menu display groups.
Protection flags and counters displayed on LCD.
Large 4 lines by 40 characters LCD or as per manufacturers std.
Four configurable quick keys.
Operator Interface turns on when opening the door.
Close and Open indications LEDs.
Trip & close circuit isolation shall be through large rocker switches/ user configurable
function keys.
Front mounted isolated RS 232 data port for local communication at site.
It shall be with automatic and manual battery health monitoring.
Electronic modules shall perform continuous diagnostic monitoring and shall contain
hardware and software watchdog checking.
Protection, Measurement & Power Quality characteristics.
Following protection element shall be provided with at least 4 independent protection group
settings.
Phase Instantaneous Overcurrent
Earth Instantaneous Overcurrent
Phase Time Overcurrent.
Earth Time Overcurrent.
Changes to any of the protection parameter to any of the not active protection group
shall not affect the protection functionality of the active protection group.
Information about activation of any of the protection group shall be recorded in history
and shall be easily assessable. Information about protection trip shall clearly indicate
the protection group, active at the time of fault.
AR and Control element shall have the facility for Automatic protection group
selection. Automatic Protection Group Selection shall have the facility to be turned ON
or OFF with pass-word protection or other form of access control.
The auto re-closures shall have the facility including the software of connecting in
LOOP AUTOMATION. Supply outage management is in the scope of bidder.
The Modem required for the Auto recloser will be provided by the SCADA
Implementing agency (SIA).
The earthing of auto recloser as per the standard including providing of earth pit, and
connection to the control cabinet and other allied equipment is in the scope of bidder.
15.2.5 Auto recloser Operation parameters
The number of sequential trips to reach lockout shall be selectable to be either 1, 2, 3 or 4.
Reset times shall ideally be separately selectable for SEF and the combination of over-current
and earth fault functions. The reset time shall be selectable from 5s to 120s in 1s steps.
Dead times shall ideally be separately selectable for SEF and the combination of over-current
and earth fault functions. The dead time between each -successive recloser shall be
independently selectable from instantaneous to 5s for the first recloser and from a minimum of
2s up to a maximum of 120s for subsequent reclosers.
A close instruction initiated locally or remotely during a dead time shall result in lockout if the
fault is still present upon closure.
15.2.6 Auto Recloser Statistical Measurement Functions
The Measurement shall be done with one of the following methods i.e. three-phase-3-wire
method; and or the three-phase-4-wire method and made available at HMI and remote location.
Quantities to be measured/calculated with specified accuracy are:
Phase Voltage (V) ±2.5% of auto-recloser rated voltage.
Line Voltage (V) ±2.5% of auto-recloser rated voltage.
Phase Current (A) ±2.5% of auto-recloser rated current.
Three phase active Power (kW) ± 5 %;
Three phase reactive power (kVAr) ± 5 %;
Total three-phase active energy (kWh) ± 5 %;
Power factor ± 5 %;
Maximum demand ± 5 %.
Phase Angle ± 10 deg.
Total Pwr (KW, KVA, KVAr) ± 5 %.
The real power energy and maximum demand measurement shall be integrated with respect to
time. Energy values shall be calculated with selectable time integration periods of 30 min. The
data buffer shall work on the FIFO principle and a minimum size for the data buffer shall store
values for 4 months on the 30 minutes integration period.
Supply Outage management (SOM) which is a part of SCADA system.
The following parameters shall be recorded in SCADA
Cumulative total number of outages.
Cumulative total outage duration.
Time and duration of each outage
15.2.7 Power Quality analysis characteristics
Waveform Capture It shall capture the Waveform and store in flash memory filtered
and scaled raw data (32 samples per cycle ) of the 3 line to earth or 3line to line
voltages and 4 currents for a predefined time window either side of a user-defined
trigger. The user shall be able to configure a pre and post trigger time ratio for data to
be stored.
Harmonic Analysis: It shall able to calculate for voltages and currents of 2nd to 7th
harmonic and Total Harmonic DistortIon (THD) for 4 currents and 3 line to line
voltages or 3 line to earth voltages.
Sag and Swell monitoring, when sag/surge is identified then an event shall be logged.
The same shall be downloadable at the remote through communication interface.
15.2.7.1 Local Engineering
The AR controller shall contain a real time clock (with leap year support) that can be set both
locally and remotely.
A facility for selecting all the protection, operating and communications characteristics shall
be locally available in the control cabinet. Optional password protection against unauthorized
changes shall be available.
15.2.7.2 Event Records
The controller shall provide, non-volatile memory storage shall be sized to store
at least 3,000 logs :
All operating, protection and communications parameters.
An event record containing at least 3,000 events.
All setting change logging.
Maximum demand shall have the facilities to be configured for weekly or monthly
demand.
Demand Logging shall be daily, weekly, monthly.
It shall record wide range of parameters such as current, voltage, including the
monitoring of the battery and its healthiness, gas pressure etc. with IEC 104 /
101/103/ Modbus
It shall also record specific information including temperature pertaining to
Control box
One battery and constant voltage charger with current limiting shall be part of the AR. Battery
standby time shall not be less than 24 hours and shall allow for a minimum of ten (10)
sequences of LRC trip-close operations and a transmit/receive standby duty cycle of 10/90
percent with respect to the GPRS/MPLS-4G modem. The battery shall recharge to 80 % of its
capacity in a maximum of 15 h. The total number of circuit-breaker operations under the above
communications scenario shall be at least 10 AR operations preventing closing if the battery
will not have enough stored energy to open the circuit- breaker for a protection trip condition.
Batteries shall be disconnected at the manufacturer's specified minimum voltage.
Battery Low' indication shall be available locally and remotely and shall include a battery test.
The indication of "Battery Low" status shall allow for a further ten AR operations.
The minimum battery life expectancy shall be 5 years. Details of the guaranteed life
expectancy of the battery shall be stated in the tender documentation.
15.2.7.6 Maintenance and commissioning
All the communications equipment shall be easily accessible in the control cabinet. Wiring of
"communications links in the control cabinet shall permit the connection of a temporary
protocol-Monitor. It shall be possible to perform secondary injection testing while the AR is
communicating with the center.
It shall be Possible to disconnect the AR circuit breaker and connect a simulated breaker to
the control cabinet for testing purposes.
The AR shall not malfunction while the modem is transmitting via an antenna in close
proximity and the control cabinet door is open.
Provision shall be made in the control cabinet for individually isolating the power supply
to/from the following:
Battery;
Battery charger;
GPRS/MPLS-4G modem; and
Primary supply to the control cabinet electronics.
15.2.7.7 Rating Plate
Each AR shall bear a rating plate of an intrinsically corrosion-resistant material, indelibly
marked with the sea-level rating for which the equipment has been type tested. The rating
plate shall be indelibly marked with:
The manufacturer's name;
The equipment type designation and serial number of the AR;
The mass, in kilograms;
The date of manufacture;
The voltage transformer ratio, class and burden.
Auxiliary supply voltage (if applicable).
Purchase Order number and date.
Each AR shall also exhibit a Danger Board to indicate the presence of high voltage.
Documentation
Each AR shall be supplied complete with the documentation specified in Items, together with
the routine test certificates specified above.
15.3 11 KV Sectionalizer
Description Standard
11 kV Sectionalizers
High Voltage Switches IEC 60265-1
Degrees of protection provided by enclosures (IP Code). IEC 60529:1989
Description Standard
15.3.3 Construction
15.3.3.1 General
The Sectionalizer / load break switch shall be suitable for use on non-effectively earthed and
effectively earthed networks and under the system conditions and service conditions as
follows:
Also referred to as "Reclosing Interval". This is the time between the instant that the current is
interrupted by the AR and the instant the contact of the AR closes as a result of an automatic
reclose operation.
Definite time:
A fault detect event occurs if the current exceeds the fault threshold setting for a time equal to
the definite time setting.
Effectively earthed system:
An earthed system in which the healthy phase power frequency phase-to-earth over voltages
associated with earth faults are limited to 80% of the highest phase-to-phase voltage of the
system.
Pickup:
The fault detection elements are monitored and an element “picks up” when the measured
current exceeds the preset level of the specific element. Typical detection elements are Phase,
Earth and Sensitive Earth Fault (SEF).
Pole-mounted remote terminal unit (PMFRTU):
A remote terminal unit that is designed for pole mounting and that operates specific pole-
mounted equipment remotely.
Sequence reset time:
The time duration after a supply interruption occurred before the sectionalising sequence resets
if the sectionaliser does not detect another fault.
Sectionalising:
The ability of the load break switch to count the operations of an upstream AR and to open
during the dead time of the AR after a configurable number of supply interrupts.
Secure control:
A single mechanically non-latching switch that effects one state of a control function only. An
example of which is either a non-latching switch or two separate push buttons that affect one
state of a control function only in each position. If a control is activated repeatedly it only
effects that state and does not change the state of the control.
Sensitive earth fault (SEF):
A relay that is sensitive to very low earth fault currents and in which the operating settings are
for current magnitude and definite time delay.
Supervisory:
Remote control and indications of an LBS or a PMRTU by means of a telecommunications
link.
Supply Interruption:
A fault pickup followed by a “no current” and “no voltage” condition is called a Supply
Interruption. This condition typically occurs when an upstream recloser trips due to a
downstream fault.
Toggled control:
A single mechanically non-latching switch/push-button that enables a single control function
on the first operation of the switch/push-button and disables the function on the second
operation of the same switch/push button.
15.3.5 Testing
The specified Sectionalizer shall be subject to type tests, routine tests, and acceptance tests.
Where applicable, these tests shall be carried out as per the standards stated above. Prior to
acceptance testing, the supplier shall prepare and submit a detailed test plan.
15.3.6 Mounting of Sectionalizer
The LBS shall be suitable for single pole mounting and shall be provided with mounting
brackets. Adequately rated lifting eyes shall be provided and they shall be designed to allow
the completely assembled LBS. The diameter of the eyes shall be a minimum of 30mm.
Suitable mounting brackets for surge arresters shall be provided. The LBS shall be fitted with
an external M12 Earthing stud, complete with a nut, lock nut and spring washer. The earth
stud shall be welded to the tank for optimal Earthing connection. All support structures and
associated bolts and nuts with these parts, shall be hot-dip galvanized.
The earthing of sectionalizer as per the standard including providing of earth pit, and
connection to the control cabinet and other allied equipment is in the scope of bidder.
15.3.7 Bushings
The preferred arrangement for termination is an insulated bushing arrangement achieved by
using epoxy resin bushing/ HECP. The material for bushing shall be outdoor aromatic epoxy
resin with silicon rubber boots details of the type and Creepage shall be provided.
15.3.8 Finish
All interior and exterior ferrous surfaces of the LBS and control cabinets shall be
manufactured from marine grade 304 or 316 Stainless steel.
15.3.9 Control Equipment
Control cabinet
Cabinets that house equipment for detection and control shall be mounted independently of
the LBS. The cabinet shall be manufactured from 304 or 316 grade stainless steel.
Suitable ultraviolet-resistant cable shall be provided to connect the LBS to the control cabinet.
It shall be possible to disconnect the cable at the LBS while the LBS is connected to the power
system, without causing damage or mal-operation: care shall be taken that CTs are not open
circuited.
A robust, multi-pin weather proof connector shall be supplied. Preference will be given to
products supplying connectors at both the LBS and the control cabinet.
Cabinets shall be adequately sealed and dust protected and shall be internally treated to prevent
moisture condensation. The degree of protection shall be suitable for purpose.
The control cabinet shall be for all – weather access & vandal resistant.
The door of the cabinet shall be fitted with a robust fastening arrangement that is capable of
being secured by a padlock that has a two point locking mechanism system.
The cabinet shall be fitted with an external Earthing stud with a nut, lock nut and a serrated
The control cabinet shall house Control and detection enclosure, which shall incorporate all
the electronic modules. These electronic circuits shall fulfill the functions ,detection ; Network
SEF a primary earth fault current of 4A to 20A in steps not exceeding 1A shall be detectable.
The LBS and Control element shall support multiple detection groups and this shall meet the
requirements specified below:
The LBS shall have minimum 4 independent detection groups. The Detection Groups
shall have clear indication and shall be marked as "I, II, III, IV" or "A, B, C, D"
Each detection group shall have the facility to configure O/C, E/F and SEF fault
detection current and definite time.
Changes to any of the detection parameter to any of the not active detection group shall
not affect the detection functionality of the active detection group.
Information about activation of any of the detection group shall be recorded in history
and shall be easily assessable. Information about fault detection shall clearly indicate
the detection group, active at the time of fault.
LBS and Control element shall have the facility for Automatic detection group
selection.
Automatic Detection Group Selection shall have the facility to be turned ON or OFF
with password detection or other form of access control.
Sectionalizing function
The number of detected faults to trip shall be selectable to be either 1, 2, 3 or 4.
Reset times shall ideally be separately selectable from 5s to 120s in 1s steps.
Statistical measurement functions
The Measurement shall be done with the three-phase-4-wire/ three phase 3 wire method and
the data shall be made available at control center for further integration
Quantities to be measured/calculated with specified accuracy are:
Phase Voltage (V) ±2.5% of Sectionalizer rated voltage.
Line Voltage (V) ±2.5% of Sectionalizer rated voltage.
Phase Current (A) ±2.5% of Sectionalizer rated current.
Three phase active Power (kW) ± 5 %;
Three phase reactive power (kVAr) ± 5 %;
Total three-phase active energy (kWh) ± 5 %;
Power factor ± 5 %;
Maximum demand ± 5 %.
Phase Angle ± 10 Deg.
Total Pwr (KW, KAV, KVAr) ± 5 %.
The real power energy and maximum demand measurement shall be integrated with respect
to time. Energy values shall be calculated with selectable time integration periods of 5 min,
15 min, 30 min or 60 min. The data buffer shall work on the FIFO principle and a minimum
size for the data buffer shall store values for 4 months on the 30 minutes integration period.
Supply Outage management (SOM), LBS and Control element shall have the facilities to
record the number and duration of outages. The information shall be assessable locally or
remotely using SCADA/DMS system.
The following parameters shall be recorded as,
Cumulative total number of outages.
Cumulative total outage duration.
Time and duration of each outage
15.3.11 Power Quality analysis characteristics
Waveform Capture It shall capture the Waveform and store in flash memory filtered and
scaled raw data (10 x 3200 samples per second) of the 3 line to earth or 3 line to line voltages
and 4 currents for a predefined time window either side of a user-defined trigger. The user
shall be able to configure a pre and post trigger time ratio for data to be stored.
Harmonic Analysis It shall able to calculate 2nd to 7th harmonics and total harmonics
distortion an over 40ms period for 4 currents and 3 line to line voltage or 3 line to earth
voltage.
Sag and Swell monitoring, when sag/surge is identified then an event shall be logged. The
same shall be downloadable at the remote through communication interface.
Local Engineering
The LBS controller shall contain a real time clock (with leap year support) that can be
set both locally and remotely.
A facility for selecting all the detection, operating and communications characteristics
shall be locally available in the control cabinet. Optional password detection against
unauthorized changes shall be available.
Event Recording
The controller shall provide, Non-volatile memory storage shall be sized to store at least 3,000
logs as:
All operating, detection and communications parameters.
An event record containing at least 3,000 events.
All setting change logging.
Maximum demand shall have the facilities to be configured for weekly or monthly
demand.
Demand Logging shall be daily, weekly, monthly.
It shall record wide range of parameters with the configurable history, such as current,
voltage, total power, auxiliary voltage, battery voltage, gas pressure.
It shall also record specific information pertaining to Control module temperature,
Switchgear Temperature and battery temperature.
Facility for configuring the interval time in minutes shall be provided.
A pointer shall be provided to indicate up to where the data was last read. This will
enable regular uploading of the data without re-loading of previously read data.
All events shall be time and date stamped with a resolution of at least 10 ms relative to
the onboard real time clock.
15.3.12 Tele Control Requirements
The LBS controller shall detect and report disconnection of the control cable between
the controller and LBS.
It shall be possible to operate LBS change the active detection group, turn Sectionalizer
functionally ON/OFF and turn E/F and SEF ON/OFF remotely using the protocol
specified.
15.3.13 Communication
As a minimum, one independent RS-232, one RS-485 communication ports & one Ethernet
communication ports that allow for simultaneous operation shall be provided, to be used as
follows
USB port shall be provided to upload the non-volatile data to and from a personal computer.
To interface to remote communications equipment (modems, radio-modems,
GSM/GPRS/MPLS-4G andFiber Optic).
As a minimum, it shall be possible for serial ports to operate at the following speeds :
-1200 bps
-2400 bps
-9600 bps
- 19200 bps
Provision shall be made for mounting GPRS/MPLS-4G modems
It shall be possible to disconnect the RS-232-to-modem interface to facilitate local protocol
and communications troubleshooting. Alternatively, a low-level protocol monitor shall be
integrated in the software and accessible via the diagnostic port.
The protocol to be supported by the AR controller for remote communications shall be IEC
60870-5-104 Protocol
The serial ports shall have IEC 60870-5-101 protocol and shall be available as a backup port.
15.3.14 Power Supplies
The Sectionalizer system shall provide power for the electronics, operation of the Sectionalizer
and Controller operation of the inbuilt FRTU and Modem being provided separately by
SCADA Implementing agency (SIA). The Dry type (Resin Cast) 11000V/230V Control
Transformer so used shall be capable of supplying at least 100 VA or higher suitable for self-
operation of Sectionalizer and Modem.
Primary supply: Preference will be given to the ability to obtain primary power directly from
the HV power system requiring no additional primary supply connection.
Test supply: The LBS shall accept an external AC 230 V 50 Hz supply.
Auxiliary supply: An auxiliary supply with the following minimum characteristics shall be
provided
One SMF VRLA Battery and Constant Voltage charger with current limiting shall be part of
the Sectionalizer. Battery standby time shall not be less than 24 hours and shall allow for a
minimum of ten (10) sequences of LRC trip-close operations and a transmit/receive standby
duty cycle of 10/90 percent with respect to the GPRS/MPLS-4G modem. The battery shall
recharge to 80
% of its capacity in a maximum of 15 h. The total number of circuit-breaker operations under
the above communications scenario shall be at least 10Sectionalizer operations preventing
closing if the battery will not have enough stored energy to open the circuit- breaker for a
protection trip condition.
Batteries shall be disconnected at the manufacturer's specified minimum voltage.
Battery Low' indication shall be available locally and remotely and shall include a battery test.
The indication of "Battery Low" status shall allow for a further ten LBS operations.
The minimum battery life expectancy shall be 5 years. Details of the guaranteed life expectancy
of the battery shall be stated in the tender documentation.
15.3.15 Maintenance and Commissioning
All the communications equipment shall be easily accessible in the control cabinet. Wiring of
"communications links in the control cabinet shall permit the connection of a temporary
protocol- Monitor. It shall be possible to perform secondary injection testing while the LBS is
communicating with the center.
It shall be Possible to disconnect the LBS circuit breaker and connect a simulated breaker to
the control cabinet for testing purposes.
The LBS shall not malfunction while the GPRS/MPLS-4G Modem is transmitting via an
antenna in closeproximity and the control cabinet door is open.
Provision shall be made in the control cabinet for individually isolating the power supply
to/from the following:
Battery;
Battery charger;
GPRS/MPLS-4G modem; and
Primary supply to the control cabinet electronics.
15.3.16 Rating Plate
Each LBS shall bear a rating plate of an intrinsically corrosion-resistant material, indelibly
marked with the sea-level rating for which the equipment has been type tested. The rating
plate shall be indelibly marked with:
The manufacturer's name;
The equipment type designation and serial number of the LBS;
The mass, in kilograms;
The date of manufacture;
The voltage transformer ratio, class and burden.
Auxiliary supply voltage (if applicable).
Purchase Order number and date.
Each Sectionalizer shall also exhibit a Danger Board to indicate the presence of
high voltage.
15.3.17 Additional Information
The following shall be submitted with the tender.
Load Break switch details
Manufacturer;
Type designation;
Place of manufacture;
Fault make capacity; 3s 1s
Critical current (maximum instantaneous peak).
A schematic-wiring diagram of the LBS offered.
A general-arrangement drawing of the LBS offered.
Details of the maintenance and operating equipment and procedures needed and a detailed parts
List of the various components.
A description of the LBS operation, with instruction and maintenance manuals, including
maintenance schedules, detection characteristics, communications facilities, the method of
applying settings to relays and controls, together with any software required and the cost
thereof. The software requirements shall be stated in the tender documentation.
Details and the cost of any available portable calibration and diagnostic test set that may be
used to perform the functionality described.
A list of recommended spares and tools, quoting the prices of each item and its availability.
If detection setting changes are accomplished by resistors, electronic cards or modules or
computer programs, the price and range of such items. The method of changing detection
settings shall be stated in the tender documentation.
Details of technical back-up facilities available. These details shall be stated in the tender
documentation.
Details of the class, ratio(s) and burden of the detection current transformer and voltage
transformer, if supplied, shall be stated in the tender documentation.
The supplier shall include the following details of measurement current transformers (not
internal to the LBS) that can be supplied with the LBS. The following details shall be provided:
- Available ratio(s) and accuracy class;
- Method of fitting; and
- Effect on Creepage distance and BIL
Details of LBS service history:
- How many in service, where and for what period;
- Contact names and numbers.
Details of LV trip/close motor if available as an option
Power requirements for a close operation
The maximum achievable separation between the control unit and the circuit breaker.
Full details of the protocol implementation and the complete point database.
15.3.18 Test
The LBS / Sectionalizer shall have been type tested in accordance with, and found to comply
with, the requirements of either IS or IEC/ANSI/IEEE C37.63-2005 for the following, and the
appropriate. Values shall be stated.
Operating duty.
Making current.
Insulation (dielectric tests).
Radio interference voltage.
Temperature rise.
Mechanical operations.
Control equipment surge withstand capability.
The control cabinet and associated electronics shall have been type tested in accordance
with
Control Apparatus for Generating Stations and Substations: Electromagnetic
Compatibility
Test records (on identical equipment) in the form of validated copies of test certificates
issued by a recognized testing authority shall be submitted with the tender
documentation.
7.12.2 Routine tests
Routine tests, as required in the relevant standards, shall be carried out as a normal
requirement of the contract and, unless otherwise agreed upon, shall be witnessed by
the purchaser or by his appointed representative. No additional charge shall be levied
for such tests or for the production or presentation of documentation related to routine
tests.
Duplicate copies of routine test certificates shall be supplied together with the
equipment when the latter is delivered to the final destination stated in the order.
15.3.19 Packing/Documentation
Packing
All equipment shall be carefully packed to prevent damage or deterioration during normal
transportation, handling and storage. Each container shall bear the following information on
the outside of the container:
The address of the destination
The gross mass, in kilograms
The name of the manufacturer
The purchaser's order number and port of destination
Documentation
Each LBS shall be supplied complete with the documentation specified in Items, together with
the routine test certificates specified above.
15.3.20 Auxiliary Supply to the Controller Unit of Auto Recloser and Sectionliser
15.3.20.1 STD: IS 3156-1992: voltage transformers
For charging the batteries of the each auto recloser and Sectionalizer unit. They shall be
supplied with a suitable Dry Type Resin Cast 100 VA or more capacity auxiliary PT
according to the equipment load requirement or any other arrangement for the supply. The
auxiliary PTs shall be provided with HT jumper and control cable. For providing auxiliary
supply an external voltage transformer shall be mounted on the pole. The primary of the
transformer shall be connected to the HV mains and secondary (LV) shall be connected to the
control cubical to provide auxiliary power.
The minimum requirement of Auxiliary PT as follows,
Voltage ratio : Primary 11 KV (Phase to Phase), Dry Type Resin Cast
Voltage ratio : Secondary 230 V AC
Highest Service voltage : 12 KV
VA burden : 100 VA
Insulation level : 12/28/75KVP
Voltage factor: 1.2 continuous and 1.9 for 8 hrs.
Winding wires of PT shall be of grade 3 doubled enameled
THE HV terminal shall be adequately long from the bushing epoxy material such that
the connecting lug shall not rest directly on the bushing epoxy
15.3.21 Fault passage indicators
15.3.21.1 Environmental specifications
Mechanical resistance to vibration and shocks
The equipment shall have vibration resistance in accordance with
Description Standard
10 to 500 Hz; 0.7 mm peak to peak from 10 to 59Hz and 5g from 59 IEC 60068.2.6
to 500 Hz.
40g / 6 ms / 2000 positive and 2000 negative shocks in each direction, IEC 60068.8.77
in the three directions
Dielectric withstand
Description Standard
Insulation (50 Hz/1 min.): 2 kV IEC 61010
Impulse wave (1.2/50 µs): 5 kV EN 60-950
Electromagnetic compatibility
Description Standard
Electrostatic discharge IEC 1000-4-2 Level 3
Radiated fields IEC 1000-4-3 Level 3
Radio frequency IEC 1000-4-6 Level 3
Magnetic immunity, 50 Hz IEC 1000-4-8 Level 4
Emissions EN 55011 Class A
15.4 Fault Passage Indicator (Communicable with FRTU/ Direct to Control Centre )
15.4.1 Scope
This specification applies to a system allowing to remotely monitor appearance of faults on
an Overhead Medium Voltage network so that to localize faulty sections and send patrols for
reconfiguration of the network accordingly.
The system shall be made of Fault detection systems with wireless communication to be
installed on Medium Voltage Overhead Electric networks.
15.4.2 Quality Assurance
The Bidder shall supply documentary proof that the manufacturer possesses ISO:9001/
ISO:14001 Quality assurance certification, from an independent internationally recognized
body, for the design, manufacture and testing of Fault Indicators and remote monitoring and
control equipment for medium voltage lines
15.4.3 Wireless communication Fault detection systems
15.4.3.1 General information
System parameters
The Fault detection systems shall be designed to operate on a Medium Voltage overhead
network with the following characteristics:
Nominal Operation Voltage 7 to 69 kV
System Maximum Voltage 69 kV
Frequency 50 Hz
Type of MV neutral earthing through a resistor or solidly grounded
Conductor diameter 5 to 42 mm
One single product shall be proposed to cover the whole range of above characteristics:
Particularly, the same product should be installed on any network from 7 to 69 kV.
Offers requiring to have in stock 2 or more different product references depending on
the Line Voltage or on the conductor diameter shall not be considered.
Service conditions
The Fault detection system shall be designed to operate in the following environmental
conditions:
Symmetrical Fault Current 12.5 kA/1s (maximum phase current that the system
shall withstand)
Shocks & vibrations 120 minutes of sine vibrations and 2000 negative and
2000 positive shocks, in OX, OY and OZ axes
Lightning surge As per relevant IS standard
Maximum Ambient 55° C
Temperature
Maximum annual average 30° C
temperature
Humidity At least 95% temperature up to +55°C according to IEC
68-2-30
Purpose of equipment
The main functions of the equipment are:
To detect phase-to-phase and phase-to-earth fault currents on the MV network.
To detect voltage presence interruptions.
To time stamp faults and Voltage dips and store them in memory
To transmit information to the control center spontaneously via the
GSM/GPRS/MPLS-4Gnetwork.
To provide a local light indication of fault.
To provide operators with all useful information for fault finding and preventive
maintenance.
To be self-supplied at all times, including during outages.
15.4.4 Constitution
15.4.4.1 Components
The equipment shall be made of the following parts:
Fault Passage Indicators clipped on the overhead lines. One such device shall be clipped
on each phase so that to detect current and Voltage presence in this phase and compute
fault detection algorithm accordingly.
FPI shall commnucte to control entre thorugh GPRS/MPLS-4G modem and link or through
DCU
/Mini RTU ( SIA to provide configuration to meet SLA )
The auxiliary power source shall be provided 11000V/230V, 100VA Potential
Transformer (Dry type) along with Charger and Batteries (SMF VRLA),
appropriately dimensioned to continuously supply the GSM/GPRS/MPLS-4G
communication interface.
External GPRS/MPLS-4G Modem with Communication protocol to the control center
shall be IEC 60870-5-104 (so that FPIs sends the monitoring data to the SCADA server
and receives thetrol command sent by the SCADA server to achieve bidirectional
controllable operation.)
The maintenance free Battery shall have a warranty of at least 5 years or FMS period
whichever is higher & shall be replaceable. Low battery alarm shall be provided at
remote location.
The Fault Passage Indicators shall be designed to be clipped on the Overhead MV line. 3 Fault
Passage Indicators shall be clipped on one line, one on each phase. It shall include the following
functions:
Measurement of current running in the phase it is clipped on
Detection of Voltage absence/presence on the phase it is clipped on
From the 2 previous functions, detection of phase-to-phase and phase-to-earth faults
Short-range radio communication with a Mini RTU GSM/GPRS/MPLS-4G
communicationinterface at a maximum distance of 100m at least.
It shall be self-supplied from a lithium battery of a minimum life time 8 years, in the
temperature conditions specified above, including at least 1 short range radio communication
with the GSM/GPRS/MPLS-4G communication interface every hour and 300 hours flashing
for fault indication all over these 8 years.
The Fault Passage Indicators shall be suitable for outdoor use in the tropical climate condition
stipulated in the relevant paragraph. The components used in the Fault Passage Indicators shall
be suitably protected from direct sunlight to prevent malfunctioning due to solar radiation. The
maximum operating temperature shall be 70° C. The Fault Passage Indicators shall be suitable
for mounting on live line conductors of a diameter ranging between 5 and 42 mm, with clamps
designed so that the Fault Passage Indicator can withstand winds of 150km/h without falling
from the line. The Fault Passage Indicator shall be fully self-contained type without any
external connection, indicator or sensors. The Fault Passage Indicators shall be suitable for use
on multiple lines supported by the same pole.
15.4.5 Installation:
The FPIs shall be suitable for installing on overhead line conductors using hot sticks, while line
is in charge condition. The supplier shall supply hot sticks free of charge along with supply of
FPIs. The ratio of FPIs v/s hot sticks shall be 10 hot sticks per 30 sets of FPI.
15.4.5.1 Inrush Restraint:
The FPI shall be equipped to filter out the inrush current due to transformer magnetizing
currents thus avoiding the possible false indication of faults.
15.4.5.2 Reset
Once the fault is cleared, the FPI shall reset itself upon the power return, it shall also have a
facility of resetting with settable time duration and the manual reset.
15.4.5.3 Transient fault evolution:
If FPI is busy in flashing on transient fault and if the permanent fault occurs, the FPI shall
automatically change the priority and shall start flashing differently to show the permanent
fault; thus helping maintenance crew to review the priorities.
15.4.6 Operational specifications
15.4.6.1 Fault detection
Fault detection shall be performed by the Fault Passage Indicator described above. Fault
sensing shall be made from current measurement and Voltage presence detection, based on
detection of the electromagnetic field and its variations.
The Fault Passage Indicator shall be of the programmable type, suitable for sensing:
Short-circuit faults up to 12.5 kA for 1s.
Low earth leakage faults (referred to as “unbalance”) down to 6A.
The Fault Passage Indicators shall detect faults based on 2 simultaneous tripping
criteria:
In order to detect strong fault currents (typically phase-to-phase faults), it shall trip
when the phase current exceeds an absolute threshold for a fixed duration of about 20
to 30 ms. This absolute threshold must be configurable to at least 8 different values
between 100 and 800A.
In order to detect low fault currents (typically resistant phase-to-earth faults), it shall
trip when it detects the phase current increase within a fixed duration (about 20 to 30ms)
exceeds a relative threshold. This threshold must be configurable to at least 6 different
values between 6 and 80A.
It shall be possible to disable this second tripping criteria. When a fault occurs on the network,
the upstream protection will trip within 70ms maximum (inverse time protection). Therefore,
in order to prevent tripping due to a load increase, on detection of one of the above criteria, the
Fault Passage Indicators shall confirm the fault by checking if the voltage disappears within
the next 70ms, and start to indicate the fault only under this condition. In case of faults, the
Fault Passage Indicators which are detecting the variation of the electromagnetic field due to
fault current (Fault Passage Indicators installed between the circuit breaker and fault point)
shall provide a fault indication, while Fault Passage Indicators downstream the fault or on non-
faulty branches shall not provide any indication.
The fault indication shall be provided:
By the means of a flashing light system offering a good contrast against sunshine (red color is
preferred) and an MTBF of the light emitting system at least 45 000 Hours (LEDs for
instance). It shall provide a light of an intensity of 40 Lumen minimum and give a 360°
visibility from at least 50m in sunny day conditions, and at least 300m at night.
By an alarm sent to the GSM/GPRS/MPLS-4G interface which shall itself forward the
alarm to the control center according to its configuration.
The Fault indication shall remain until:
a time-out, configurable to at least 4 possible values between 2 and 16 hours, has
expired,
the medium voltage is back,
the Fault Passage Indicator is reset manually,
Whatever condition comes first.
Caution: since the load current might be very low upon MV return, load current reset
is not acceptable.
The Fault indication reset shall consist in:
Stopping the local light indication flashing
Sending an alarm to the GSM/GPRS/MPLS-4G interface which shall itself forward
this alarm tothe control center according to its configuration.
The Fault Passage Indicator shall include some self-test possibility usable when it is on the
line (powered or not).
The Fault Passage Indicator shall be selective in action as indicated below
It shall not respond to any sudden variation (increases/decrease) in load current
It shall not respond to a over current not due to a fault
It shall not respond to high magnetizing inrush currents, created upon line energizing.
Detection of voltage presence and absence
The Fault Passage Indicator shall send a message to the GSM/GPRS/MPLS-4G interface as
soon as it detects disappearance or appearance of Voltage on the MV conductor. The
GSM/GPRS/MPLS-4G interface shall then memorize the information as a time-stamped
event and send an alarm to the control center according to its configuration.
Communication with the control center
Communication between the FPI and the control center shall be through GSM/GPRS/MPLS-
4G network, dual-band 900 MHz – 1800 MHz, and using any standard protocol.
GPRS/MPLS-4G modem 4G /5G as per site signal availability, will be supplied by DISCOM/
SCADA Implementingagency (SIA)
It shall allow communication in 2 ways:
At any time, based on configured periodic calls or on operator action, the pole mounted
RTU shall be ready to receive a call from the control center
Whenever a monitored information declared as alarming in the pole mounted RTU
configuration changes status, the pole mounted RTU shall make a call to the control
center and send it an alarm.
Each monitored information (fault current detection, voltage absence/presence, digital inputs
etc…) shall be configurable as "alarming" when changing state, individually and
independently of others. If used with GSM communication, as an addition to the alarm to the
control center, it shall be possible to configure FPIs so that it send an SMS message to a defined
mobile phone. The configuration software shall allow to define the mobile phone number and
SMS messages service center number through modem to be provided by the SCADA
Implementing agency (SIA)
Monitored information configurable as “alarming” shall include at least the following,
consisting both of MV network diagnostic information and monitoring equipment internal
faults for self-diagnostic purpose:
Fault detection appearance with indication of Fault Passage Indicator reporting the fault
and tripping criteria tripped.
Fault detection disappearance with indication of Fault Passage Indicator reporting the
fault and tripping criteria tripped.
Voltage absence
Voltage presence
Change of state of a digital input
Fault Passage Indicator absent (failure of the pole mounted RTU communication
interface to communicate with it through short range radio)
Description Standard
Description Standard
Description Standard
The protection relay shall provide one USB port on the front panel for local
configuration and data extraction.
The protection relay shall have 2 no RJ45 port at the rear with IEC 61850
communication. The protection relay shall support RSTP and PRP/HSR redundancy
protocols. The protection relay shall support IEC 61850 edition 1 and edition 2.
The protection relay shall support IEC 61850 GOOSE communication.
The protection relay shall support simultaneously IEC 61850 (MMS) clients.
The protection relay shall provide the enhanced Cyber Security function with the
security logs, setting control ,maintenance passwords and the full central security
management for Role Based Access Control (RBAC) using an industry standard
protocol.
The protection relay shall secure any firmware upgrade with a firmware signature to
avoid unauthorized or malicious firmware downloads and to guarantee the source of
the firmware.
The relay shall be compliant to IEC 62443 standard, and compliant to NERC CIP
requirements.
15.5.1 Engineering Tools
The protection relay PC-installed configuration tool shall, as a minimum, provide the
following functions: Setting configuration, Mimic configuration, Logic configuration,
LEDs, function keys, digital inputs and outputs configuration, Measurement auto-
reading, Events/ fault records/ disturbance records reviewing, Protection status
reviewing, Control command execution.
The protection relay shall support Web-HMI (web browser-based HMI) with secured
communication to provide the similar functions as the PC configuration tool above.
The protection relay and corresponding software tool shall offer the possibility to
simulate energy injection to test and validate the protection settings.
The IEC61850 configuration tool shall support importing and exporting of valid IEC
61850 files (ICD, CID, SCD, IID).
15.5.2 Standards Compliance and Certificates
For Products safety, the protection relay shall meet the product safety requirements
according to IEC 60255-27.
For electromagnetic compatibility (EMC), the protection relay tested under min setting
shall meet the EMC requirements according to IEC 60255-26.
For mechanical robustness, the protection relay shall meet the mechanical test
requirements according to IEC 60255-21-1, -2, -3, Class 2 for vibration, shock, bump,
earthquakes compliance.
The protection relay must have an IEC 61850 Edition 2 certificate from an accredited
Level A testing laboratory.
The protection relay shall be compliant to RoHS and REACH and it shall be provided
with PEP and EoLI certificates.
The protection relay shall be compliant to Security assurance Level 1 (SL1) with the
3rd party certified for IEC 62443-4-1 and IEC 62443-4-2.
Relay Hardware
The protection relay shall have requisite CT inputs and VT inputs. The relay shall provide
requisite digital inputs, digital outputs and a watchdog contact.
The polarity of the digital outputs of the protection relay shall be settable, as Normally
Open or Changeover.
The protection relay shall have settable digital inputs voltage thresholds from 24V –
220V DC or 220AC.
The protection relay shall provide the same wiring terminals for the 1A or 5A rated CT
connection of the phase current inputs and residual current input.
The protection relay shall support a very sensitive 1A rated CT input for residual current
sensing.
The protection relay shall have programmable function keys and freely programmable
and pre-assigned LEDs.
15.5.3 Protection and Control
The protection relay shall provide the following protection functions:
1) Multi stage non-directional or directional phase overcurrent protection.
2) Multi stages non-directional or directional earth fault protection
3) The instantaneous trip time at set shall be less than 30 ms.
4) Earth fault protection with optional memory mode to extend the transient fault
information and quickly clear the fault.
5) Inrush detection, Cold load pickup and Selective overcurrent logic for non-
directional and directional phase overcurrent and earth fault protection
6) Broken conductor , negative sequence overcurrent ,negative sequence overvoltage
protection
7) Multi-stages under voltage protection and overvoltage protection with settable any
phase or all phases tripping logic
8) Multi- stages neutral overvoltage protection, with neutral voltage either calculated
from the three phase voltages or measured from broken delta VT.
9) Thermal overload protection
10) CB Failure protection with independent backup trip timer and re-trip timer
11) Switch onto fault protection
12) Fault locator function
For non-directional / directional phase overcurrent protection and earth fault protection,
the protection relay shall provide the inverse definite minimum time (IDMT)
characteristics as per standard IEC, IEEE, ANSI, RI operating curves. The relay shall
provide at least three fully user programmable IDMT curves.
For non-directional / directional phase overcurrent protection and earth fault protection,
the protection relay shall operate correctly based on the current sample values under
primary CT saturation conditions.
The protection relay shall support controllable objects (CB, Switches, etc), with Select-
Before-Execute or Direct Control principles via local HMI, remote communication,
digital input or function keys.
15.5.4 Measurement, Power Quality and Records
The protection relay shall offer a complete set of measurement functions, including 3
phase currents and voltages, zero-sequence/ negative-sequence/ positive-sequence
currents and voltages.
Within the range of ±5 Hz of the nominal frequency, the protection relay shall provide
the current accuracy 0.5% (I > 0.05 In), the voltage accuracy 0.5% (V > 0.5 Vn), the
frequency accuracy 0.01 Hz.
The protection relay shall provide the power factor, active power, reactive power,
apparent power and active energy, reactive energy measurements.
The protection relay shall provide harmonic for current and voltage.
The protection relay shall support at least 1000 sequence-of-events associated with time
stamps with 1 ms accuracy stored in the relays non-volatile memory.
The protection relay shall support at least 20 fault recorders associated with time stamps
with 1 ms accuracy stored in the relays non-volatile memory
15.6 General Requirements
15.6.1 Documentation
Each device shall be supplied with a user manual for installation and commissioning on site.
15.6.2 Labels/Name Plate
Equipment should be provided with name plate giving full details of manufacture, capacities
and other details as specified in the relevant ISS/SS. The purchase order No. date and words
Funded under RDSS , MoP , GoI Scheme & PFC/REC ( Nodal agency for state ) name and
logo Utility Name must be etched on the name plate.
Scheme Name (RDSS Govt. of India)
Manufacturer’s name or trade mark
Purchase Order number
Year of manufacture
Purchasers name with Serial no
The color and finish may be in accordance with the Manufacturer standards for the service
conditions specified, subject to Buyer’s approval. The equipment to be supplied shall work
satisfactorily under tropical conditions
15.6.3 Surface Treatment and Painting Of Steel Parts
Before painting all un-galvanized parts shall be completely cleaned and made free from
rust scale and grease and all external rough surface cavities on castings shall be filled
by metal deposition.
The interior parts and internal structural steel work shall be cleaned of all scale and rust
by sand blasting or other approved method.
All external surfaces shall receive a minimum of 3 coats of paint.
All equipment furnished by the contractor shall be completely painted for final use,
with the exceptions of those parts or surfaces that are expressly designated as unpainted
for instance Aluminum Alloy parts.
The contractor shall perform all painting work in his shop before dispatch and only a field
touch-up shall be performed after installation. (The paint used for field touch up shall be
delivered by the supplier, and shall be of the quality and color shade as used in shop painting).
The paint shall be guaranteed for 5 years from the date of receipt of the material or end of FMS
whichever is higher.
15.6.4 Workmanship:
a) Workmanship shall be of the highest grade and conform to the best modern practice
for the manufacture of high grade machinery and electrical equipment.
b) Field welding of the equipment is to be avoided and erection at site shall be kept to a
minimum. Sub-assemblies erected and tested in the factory are limited only by the
transport conditions and handling facilities at site.
15.6.5 Drawing and Literatures ETC
The drawings with plan elevation and cross section of the equipment to be supplied with
complete dimensions and weights of module shall be enclosed. The drawings shall include
control circuit drawings, Technical literature covering instruction booklet and O&M manuals
of the equipment shall be enclosed to the offer. Tenders not accompanied by the above are
liable to be rejected. Six sets of these drawings and literature (Instruction booklets and O&M
manuals). The photographs (front and side views) of the equipment offered shall be furnished.
15.6.6 Overall Dimensions
The manufacturer shall give the necessary information as regards to the overall dimensions
of the equipment to be supplied. All the equipments shall be packed in suitable crates with
suitable steel bands so as to withstand rough handling and storage at destination.
15.6.7 Tests & test certificates
The tests shall be carried out as per relevant IS/IEC latest versions and test certificates shall
be furnished for approval. The tenderer shall indicate the details of the equipment available
with him for carrying out the various tests as per relevant IS/IEC latest versions. The tenderer
shall indicate the source of all materials and collaborators if any. They shall also indicate the
name of the supplier and make of constructional steel etc. Copy of the type test certificates
for the equipment offered shall be enclosed or in case not available, the same shall be provided
during finalization of equipment. The bidder shall confirm the same and shall provide the
equipment with requisite compliances
15.6.8 Guarantee
The Equipments shall be guaranteed for Seven years from the date of operation
The manufacturer shall demonstrate the availability of spares for all the above
equipment for next 10 years from the date of supply of the product.
15.6.9 Training
The supplier shall give rigorous training to the engineers & staff (40 persons) for 2 days for
Further , the applicable equipments indicated in the MoP oder no 12/34/2020-T&R dtd
08.06.21 & CEA /PLG/R&D/MII/2021 dtd 11.6.21 and any amendment from time to time
shall be adhered to. This chapter is applicable to Group A,B,C ,U towns as per functional
requirements. If RMU/SECTIOLIZER or AUTO RECLOSER have built-in FRTU , then the
quantity shall be reduced from external FRTU . However, the FRTU shall be meet minimum
functional requirement in chapter for RTU/FRTU
Table-1: List of Tests on IED / BCPU
Test DESCRIPTION OF THE TEST Type Routine Field
Nos. test Test test
A FUNCTIONAL TESTS FOR IED / BCPU
1. Check for make, type and rating. √ √
2. Check for full model number of IED / BCPU, no. of CT, VT, DI √ √
and DO.
3. Verification of CT and VT Ratio settings in IED / BCPU. √ √
4. Verification of programmable DI and DO configuration in √ √
IED / BCPU.
Check the available protection function stages in IED / √
5. BCPU.
6. Verification of enabled protection function stages and its √
parameter settings.
7. Measurement checks via injection kit – Current and Voltage √ √
(if applicable)
8. Testing of protection function pickup and time delay though √
secondary injection. kit.
9. Check output contacts (DO) through force function of IED / √ √
BCPU.
10. Verification of configurable LEDs settings. √ √
11. Check event records, fault records and disturbance record √ √
settings.
12. Verification of communication parameter settings in IED / √ √
BCPU.
13. Check the IEC61850 communication. √
B EMI/EMC IMMUNITY TESTS FOR IED / BCPU
14. Surge Immunity Test as per IEC 61000-4-5 √
15. Electrical Fast Transient Test as per IEC 61000-4-4 √
16. Damped Oscillatory Wave Test as per IEC 61000-4-18 √
17. Electrostatic Discharge test as per IEC 61000-4-2 √
End of Chapter 15
On course completion, all participants shall be able to prepare the necessary input data to
define the system operating environment, build the system database and displays, and prepare
the database administrator to maintain and modify the database and its structures.
16.1.2 Computer System Hardware & Software Course
The computer system hardware & Software course shall be offered, at the system level only.
The training course shall be designed to give owner hardware & software personnel sufficient
knowledge of the overall design and operation of the system so that they can correct obvious
problems, configure the hardware, perform preventive maintenance, run diagnostic programs.
The following subjects shall be covered:
(a) System Hardware Overview: Configuration of the system hardware.
(b) Operating System: Including the user aspects of the operating system, such as program
loading and integrating procedures; scheduling, management service, and utility
functions; and system expansion techniques and procedures
(c) System Initialization and Fail over: Including design, theory of operation, and practice
(d) Equipment Maintenance: Basic theory of operation, maintenance techniques and
diagnostic procedures for each element of the computer system, e.g., processors,
auxiliary memories, LANs, routers and printers. Configuration of all the hardware
equipments.
(e) Diagnostics: Including the execution of diagnostic procedures and the interpretation
of diagnostic outputs,
(f) System Expansion: Techniques and procedures to expand and add equipment such as
loggers, monitors, and communication channels.
(g) System Maintenance: Theory of operation and maintenance of the hardware
configuration, fail over of redundant hardware etc.
(h) Operational Training: Practical training on preventive and corrective maintenance of
all equipment, including use of testing tools.
16.1.3 Application Software Course
The Contractor shall provide training on Application software courses covering all
applications 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 tuning
parameters (OS software, Network software, database software and Application
Software 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 system software
and Application software documentation.
(e) Hands-on Training: shall be provided with allocated computer time for trainee
performance of unstructured exercises and with the course instructor available for
assistance as necessary.
All Software modules under the SCADA-DMS System and the associated Hardware
supplied under this project.
Communication & auxiliary power supply
Contractor shall also carry out routine works like database building/ modification, report
creation/ modification, addition of analog, status points, control points and testing from field
and other such day-to-day operational activity in presence, knowledge and concurrence of
utility representatives. The information of modifications shall be documented by contractor
and utility. Further, supply of quantity of RTU/FRTUs beyond mentioned in the contract shall
be responsibility of utility. In case RTU/FRTUs and associated components are added for
further growth in the network during FMS period and are part of supply by SIA only (as per
same unit rate of the contract for implementation and 5 Years of FMS period after operational
acceptance , then SIA shall also responsible erection , commissioning of the same ). Otherwise,
the responsibility of SIA will be limited to control center activities data base population,
mimic, report generation
/modification including end to end testing
The Scope does not include management of physical security for access to the said facilities,
the following facilities will be provided at the start of contract to FMS Contractor by Utility
for carrying out the FMS responsibilities:
Sufficient Operators for dispatch control (However, SIA shall provide adequate
training to utility operators for supervision and control and handhold for at least one
initial year during FMS for the same. In any case, operations shall be made by utility
personnel or agency hired for operations by utility only).
Appropriately secured lockable storage/setup area
Sufficient Sitting/office space in neat & clean environment
PC (other communication facilities like P&T telephone & internet facility are to be
arranged by FMS Contractor)
Utility shall provide all logistic support including access, work permits / shutdowns, Air-
conditioning, raw power supply at control centers, furniture and other interface requirements
on field of components which are not in the scope of contractor. Further, supply, erection,
commissioning of quantity of SCADA enablers beyond in the contract shall be responsibility
of utility
17.1.1 Hours of cover
The Contractor’s on-site support standard hours of service the timings for Emergency Software
Support would be 24 hours a day, 7 days a week throughout the year (i . e .24x365). At least
three Engineers including Site Manager along with one on-site support personnel for Hardware
and one on-site personnel for Software shall be deployed at each control center and at least
one field engineer per district in case of Group B & C. towns and one field engineer each for
Group A /U town The support personnel so deployed shall be qualified personnel having
experience in the delivered SCADA/DMS system. The Contractorshall submit the CV’s of all
such personnel to Utility .The manpower specified is minimum, however, contractor shall
ensure sufficiency of manpower to meet SLA during FMS period
The Contractor shall be responsible for 24*7*365 management of all the systems as per scope
of work with services rendered at least as per Service Level Agreement between utility &
Contractor.
Page 250 of 333
Power Finance Corporation SCADA/DMS,
System under RDSS - Govt. of India
Model Technical specification
Requests for IMAC shall be prepared by FMS Contractor depending on customer/ system
requirements & shall be approved by utility. Utility shall formulate guidelines for IMAC &
communicate it to FMS Contractor. All procurement shall be done by utility other than
replacement of faulty items as per warranty /SLA under FMS period of the said item. Any item
consumed during warranty period from SIA supplied spares to utility, shall be replenished by
SIA
c) Contractor Management Services
As part of this activity, for efficient and effective warranty implementation, the FMS
Contractor’s team will:
1. Manage the vendors for escalations on support
2. Logging calls and co-ordination with Contractors
3. Contractor SLA tracking
4. Management of assets sent for repair
5. Maintain database of the various vendors with details like contact person, Tel. Nos.,
response time and resolution time commitments. Log calls with vendors, Coordinate
and follow up with the vendors and get the necessary items exchanged.
6. Analyze the performance of the Contractors periodically (Quarterly basis)
7. Provide MIS to utility regarding tenure of completion of warranty/AMC with outside
vendors for software, hardware & networks maintenance in order that utility may take
necessary action for renewal of warranty/AMC. FMS Contractor shall also provide
MIS regarding performance of said Contractors during existing warranty/AMC.
8. Since during initial five years, warranty is in scope of OEM vendors there will be no
AMC for SCADA/DMS system. During such period, FMS Contractor has to interact
with such vendors for maintenance services and spares. After warranty period, if
required Utility can award the suitable AMC and FMS Contractor has to interact with
Contractors as selected by utility for providing AMC for the said system on mutually
agreed terms & conditions.
9. The faulty hardware /software may be replaced from available spares of utility to
minimizing downtime time. However, in such case the same be replenished to utility
by SIA within a month.
d) FMS Contractor’s (SIA) Other Responsibilities
1. Provide a single-point-of-contact for responding to Utility’s queries or accepting its
problem management requests. FMS Contractor’s specialist will respond to utility’s
initial request within agreed service level objectives set forth.
2. Monitor availability & Escalate to service provider and Notify Utility for
communication failures.
3. Review the service levels of the service provider (as per pre-defined schedules on SLA
performance) along with utility.
4. Provide network availability incident reports severity wise to utility in a format mutually
agreed.
5. Provide SLA performance management report of the Service Provider.
6. Fault Detection and Notification: The Contractor shall diagnose problems that could
arise as part of the LAN/WAN network. These include connectivity problems due to
failures in communication transport links, routing configuration points, or from software
bugs etc.
7. Fault Isolation and Resolution: All faults that have been identified need to be isolated
and rectified appropriately. The resolution measures undertaken by the Contractor and
results produced accordingly shall be documented in the report.
8. Carrier Coordination: Carrier Coordination implies providing a single point of contact
to resolve network related problems involving carrier circuits, whether equipment or
circuit related. When a problem is diagnosed because of a WAN circuit, the Contractor
must coordinate with the corresponding carrier to test and restore the circuit. The
Contractor must take the responsibility and ensure that the problem is resolved.
9. Hardware/Software Maintenance and Monitoring: This would include problem
determination, configuration issues, and hardware and software fault reporting and
resolution. All such issues would need to be recorded and rectified.
10. 24x7 Network Monitoring and reporting: The Contractor shall monitor the network
on a continuous basis using the NMS and submit reportson a monthly basis with instances
from the NMS system. System performance is to be monitored independently by the
Contractor and a monthly report mentioning Service up time etc. is to be submitted to
Utility. The report shall include:
Network configuration changes
Network Performance Management including bandwidth availability and
Bandwidth utilization
Network uptime
Link uptime
Network equipment health check report
Resource utilization and Faults in network
Link wise Latency report (both one way and round trip) times.
11. Historical reporting for generation of on-demand and scheduled reports of Business
Service related metrics with capabilities for customization of the report presentation.
12. Generate SLA violation alarms to notify whenever an agreement is violated or is in
danger of being violated.
13. Any other reports/format other than the above mentioned reports required by utility
e) Backup/Restore management
FMS Contractor will perform backup and restore management in accordance with mutually
FMS Contractor shall ensure:
1. Backup and restore of data in accordance to defined process / procedure.
2. 24 x 7 support for database restoration requests
3. Maintenance and Upgrade of infrastructure and/or software as and when needed.
4. Performance analysis of infrastructure and rework of backup schedule for optimum
utilization.
status to be derived from trend table and failure reporting of control command
execution event , if any
Cyber security audit from CERT.IN empaneled agency on annual basis or interim
audits in case of major change
No cyber-attack or intrusion in SCADA/DMS system incident
The Contractor must adhere to well-defined processes and procedures to deliver consistent
quality services throughout its contractual period. Any hardware/software to meet the
requirements under this legacy system for integration under chapter 1 , must be provided by
the Contractor. The Contractor isexpected to have the following system management controls
in place:
i) Availability Management
The Contractor must define the processes/procedures which ensure the service delivery as per
the required SLAs or exceed it. It should cover various equipments such as all the servers,
networks, switches, routers, Modems & other site specific services, and the critical services
and their supporting hardware, and software components, as defined in scope of work. Industry
standard SLA management tools should be deployed and shall have following essentialfeatures:
Ability to create an escalation for an SLA.
Ability to workflow the SLAs.
Ability to create new action types, if needed.
Ability to define sets of actions that are grouped together in a specific sequence.
Ability to associate an escalation point with one or more actions through the action
group.
ii) Performance Management
The recording, monitoring, measuring, analyzing, reporting, and forecasting of current levels,
potential bottlenecks, and enhancements of performance characteristics for the services,
networks, applications, system software, and equipment within the scope shall be required.
System tuning and optimization is an inherent part of this contract. Where warranted, the
Contractor will utilize capacity management data in combination with performance
management data to identify ways to improve performance levels of the resources, extend their
useful life, and request utility to approve revisions/upgrades to the computing and
communications hardware, software and other equipments such that higher levels of
performance of the resources are obtained.
iii) Security Management
The protection from unauthorized usage, detection of intrusions, reporting as required
and proactive prevention actions are to be provided by the Contractor. No cyber-attack
or intrusion in SCADA/DMS system incident
Cyber security audit shall be carried out from CERT.IN empaneled agency on annual
basis or interim audit in case of major modification
No cyber-attack or intrusion in SCADA/DMS system incident
The Contractor shall submit the procedures details to meet the above along with the offer.
17.2.3 Support for System expansion
New RTUs, RMUs & FPIs etc. per year are likely to be added to match the growing Power
system. The services to be provided by the Contractor will include the Communication Front
End (CFE) port/card addition/expansion, database resizing, interface addition in CFE and
support for integration confirming to the IEC standards / existing application. This would not
include the cost of equipments/card required for expansion.
17.3 Problem Severity Levels
The problems will be categorized as follows:
Category Definition
Severity 1 – Urgent Complete system failure, severe system instability, loss or failure of
any major subsystem or system component such
as to cause a significant adverse impact to system availability,
performance, or operational capability (as described at 17.3.1).
Severity 2 – Serious Degradation of services or critical functions such as to negatively
impact system operation. Failure of any redundant system
component such that the normal redundancy is lost (as described at
17.3.1. Non-availability of Man-power at control center during
working hours
The details of the system under different severity level are as below:-
17.3.1 Severity of the system under different Severity level.
a) Severity-1 (Urgent support)
This support is required when there is a complete system failure, severe system instability, the
loss/ failure of any major sub-system / system or its components, which may significantly
impact the system availability, performance, or operational capability at Control center. For
example, loss of data to the operator due to any problem in SCADA-DMS system,
,Loss/failure of DR / Disaster recovery Centre, outages of both the CFEs attributable to any
software/hardware related problem, outage of any important software functionality (on both
the servers) which is required to disperse Distribution management /OMS functions, , Failure
of both GPS clock and time synchronization and outage of both routers, failure of both LAN
system, outage of both main and backup servers of any system, firewall would be included
under this category. The problem shall be attended by the Contractor at the earliest, within the
response/Resolution time as specified in the Agreement on occurrence of incident . The
Contractor shall take all steps to restore the SCADA functionality at the earliest to avoid data
loss.
b) Severity-2
The support services not defined under Severity-1 are included under this category. Failure of
one SCADA/DMS/FEP Server/ICCP server, failure of VPS , Stoppage of data collections for
archiving, real time calculations, failure in Acquisition of SOE at the respective Control-
Centre, outage of Real Time Network and distribution applications, and other applications are
included in this category, Coverage under this severity would be outages that do not
immediately cause on feeder data loss but subsequently could result into Severity-1 category
outage, loss of an important subsystem that may affect the day-to-day works and loss of
archived data. Failure of any redundant system component affecting the critical redundancy
like loss of any one Application Processor, Router, CFE would also be included in this category.
Non-availability of Man-power at control center during working hours will also be covered
under this category.
c) Severity-3 (Standard support)
The support services included under this category are when the outage or loss of functionality
is neither an emergency nor a priority functionality as indicated in severity level 1 or 2 above.
Problems like database reworking, failure of any one workstation, etc. would be covered under
this Severity.
d) Severity-4 (General Technical Help)
Request for information, technical configuration assistance, “how to” guidance and
enhancement requests are included under this category.
17.4 Problem/Defect Reporting Procedure
The Contractor shall propose an appropriate problem/defect reporting procedure to meet the
requirement of all severity level cases along with the offer.
17.5 Response and Resolution Time
This clause describes the target times within which the Contractor should respond to support
requests for each category of severity. The Initial Response Time is defined time as the period
between the initial receipt of the support request (through approved communications channels)
and the acknowledgment of the Contractor. The Action Resolution Time is the period between
the initial response/ incident concurrence and the Contractor delivering a solution. This period
includes investigation time and consideration of alternative courses of action to remedy the
situation. The Action is defined as a direct solution or a workaround.
Except for Severity Level 1 & RTUs/ substation equipment , all hours and days specified are working
hours only.
i) Cleaning and blowing for removal of dust from Servers , Workstations, CFE
panels and RTUs/FRTUs/ Numerical relays supplied etc.- once every 3 months.
j) Routine maintenance of electronics of RMU/ SECTIONLIZER /FPI
ii) Exclusions:
a) Maintaining dust free / AC environment and protection from rodents and vermin is
the responsibility of Utility.
b) Regular cleaning of computer furniture and surroundings is the responsibility of
Utility.
c) Equipment shutdown during preventive maintenance shall be deemed as available.
17.7 Availability and Payment charges Calculation
It is the endeavor of both the Contractor and Utility to maximize system availability to the extent
possible. The Contractor shall provide guaranteed availability for various types of Severity
levels as specified in clause 17.3 above. The non-availability hours for availability calculation
may be reckoned from the end of the allowed Action Resolution time. A standardized register/
log on system shall be maintained at each site containing full details of each outages, actions
taken by Utility to correct the problem, applicable Severity level, time of reporting to the
Contractor support engineer/support centers pursuant to the appropriate methods in the
Agreement, allowed Response time as per the Response times defined in clause 17.5, actual
Resolution time, and signature of Engineer-in-charge as well as the Contractor’s support
engineer of the site. Duration of outages over and above the Action Resolution time in each of
the Severity levels shall be counted for the non- availability computation and shall be clearly
brought out in the register. The resolution may be accomplished by a work around, and such
solution shall mark the end of non-availability. In the event of multiple failures at a site, due to a
common cause, the first FPR (Field Problem, Report) logged shall be used for the purpose of
availability calculation. However, simultaneous multiple outages duetounrelated cause would be
counted separately
17.7.1 Availability computation for SCADA-DMS-OMS System
Availability would be on per quarterly basis. The formula to be used for availability computation
would be as under:
Availability per quarter (per site) = THQ- (S1 x 0.6+S2 x0.3+S3 x 0.1) x 100%
/THQ
Where THQ is total hours in the quarter
S1 is the total non-available hours in Severity Level-1
S2 is the total non-available hours in Severity Level-2
S3 is the total non-available hours in Severity Level -3
In case of cyber-attack incident which is not neutralized by cyber security and affected the
system, the availability shall be considered nil
17.7.2 Payment of maintenance charges (based on SCADA-DMS -OMS System
availability)
In the event of availability below a certain level, the maintenance charges would be
proportionately reduced as follows. The non-availability will be considered if system is non
available beyond reporting/response + resolution time :
For overall system availability (S)
Further, Non-Availability of legacy systems shall not be considered for calculating Overall
SCADA/DMS System Availability . However , data availability from legacy to be ensured.
Further, the non-availability of following Non-Critical functions shall not be considered for
calculations of SCADA/DMS System availability, however these functions should be available for
98% of the time.
a. Database modification and generation
b. Display modification and generation
c. Report modification and creation
d. DTS
% F in Qtr = Min ( AVG Hrs FRTU up in Hrs / total Hrs), (Avg Hrs Link up in Hrs /
Total Hrs), ( Total No of points with good telemetry code captured / total number of points
end to end tested ) * 100%
Points are suggested to be taken from tabular display of 15 min for all status and
control points
The computation of Availability / Non-availability would be rounded up to single decimal places
at each Contract Co-ordination Site on quarterly basis and any deduction in the FMS charges
thereof would be calculated as stated above in Clause 17.7.2 on pro-rata basis.
b. Utility shall ensure that proper Environmental conditions are maintained for the
system.
c. Utility shall ensure that the System is kept and operated in a proper and prudent manner
and only trained Utility employees (or persons under their supervision) are allowed to
operate the system.
d. Utility shall provide access to the sites of installation for purposes of providing
Support Services.
e. Utility shall provide the Contractor with Office and storage space for their
maintenance staff and spares. However , contractor shall be responsible for security
of the items stored
17.10 Responsibility Matrix
The table in this clause provides a summary definition of the roles and responsibilities of the
Contractor and Utility.
Legend: This indicates who has primary responsibility to perform this function.
A This indicates who will provide assistance.
Utility.
5.3 Replenish local spares A
inventory
6.0 INTEGRATION AND DATABASE WORK
6.1 CFE /RTU/FRTU Card A
addition/Expansion field
equipment
6.2 Database resizing, Mimic A
creation/ editing etc ,
6.3 Annual cyber security A
audit
The contractor shall be responsible for all the maintenance of the system till the operational
acceptance. The consumables and spares wherever required for maintaining the system shall be
provided by the contractor till operational acceptance of the system. The consumable items
shall include but not be limited to (a) VPS lamps (b) printer paper (c) Printer toner, ink, ribbons
and cartridges (d) Special cleaning material
End of Chapter 17
This chapter describes the project management, schedule, quality assurance, and
documentation requirements for the project. This chapter is applicable to Group A,B,C, U
towns as per functional requirements
18.0 Project Management
The Contractor shall assign a project manager with the authority to make commitments and
decisions that are binding on the Contractor. Employer will designate a project manager to
coordinate all employer project activities. All communications between employer and the
Contractor shall be coordinated through the project managers. The project managers shall also
be responsible for all communications between other members of the project staffs.
Bidder shall submit the manpower deployment plan along with the bids, describing the key roles
of each persons.
18.1 Project Schedule
The project implementation schedule shall be not exceed 24 months from the date of award
for B,C Towns and 30 months from award for A,U Towns . Based upon this schedule the bidder
shall submit a preliminary implementation plan along with the bid. The detail project
implementation schedule shall be submitted by the contractor after award for employer’s
approval, which shall include at least the following activities:
a) Site Survey
b) Documents submission and approval schedule
c) Factory & Site Testing Schedule
d) Database development schedule
e) Hardware purchase & Manufacturing, Software development & integration schedule
f) Dispatch Schedule
g) Installation / commissioning schedule
h) Training schedule
The project schedule shall include the estimated period for completion of and its linkage with
other activities.
18.2 Progress Report:
A progress report shall be prepared by the Contractor each month against the activities listed in
the project schedule. The report shall be made available to employer on a monthly basis, e.g.,
the 10th of each month. The progress report shall include all the completed, ongoing and
scheduled activities.
18.3 Transmittals
Every document, letter, progress report, change order, and any other written transmissions
exchanged between the Contractor and employer shall be assigned a unique transmittal
number. The Contractor shall maintain a correspondence index and assign transmittal numbers
consecutively for all Contractor documents. Employer will maintain a similar correspondence
numbering scheme identifying documents and correspondence that employer initiates.
Neither the enforcement of QA/QC procedures nor the correction of work mandated by those
procedures shall be cause for an excusable delay. An effective Quality Assurance and Quality
Control organization shall be maintained by the Contractor for at least the duration of this
Contract. The personnel performing QA/QC functions shall have well-defined responsibility,
authority, and organizational freedom to identify and evaluate quality problems and to initiate,
recommend, or provide solutions during all phases of the Contract. The QA/QC organization of
the Contractor shall be an independent administrative and functional structure reporting via its
manager to the Contractor's top management. The QA/QC manager(s) shall have the authority
within the delegated areas of responsibility to resolve all matters pertaining to quality to the
satisfaction of employer when actual quality deviates from that stated in the Work Statement.
The Contractor shall be required to submit all the Quality Assurance Documents as stipulated in
the Quality Plan at the time of employer's inspection of equipment/materials.
The employer or his duly authorized representative reserves the right to carry out Quality Audit
and Quality Surveillance of the systems and procedures of the Contractor's/his vendor's Quality
Management and Control Activities.
The scope of the duties of the employer, pursuant to the Contract, will include but not be limited
to the following:
a) Review of all the Contractor's drawings, engineering data etc.
b) Witness or authorize his representative to witness tests at the manufacturer's works
or at site, or at any place where work is performed under the Contract.
c) Inspect, accept or reject any equipment, material and work under the Contract
in accordance with the specifications.
d) Issue certificate of acceptance and/or progressive payment and final payment
certificate
e) Review and suggest modification and improvement in completion schedules
from time to time; and
f) Monitor the Quality Assurance program implementation at all stages of the
works.
18.4.2 Inspection
The Contractor shall give the employer/Inspector two weeks in case of domestic supplies and
six weeks in case of foreign supplies written notice of any material being ready for testing.
Such tests shall be to the Contractor's account except for the expenses of the Inspector. The
employer/Inspector, unless witnessing of the tests is waived, will attend such tests on the
scheduled date for which employer/Inspector has been so notified or on a mutually agreed
alternative date. If employer/Inspector fails to attend the testing on the mutually agreed date,
Contractor may proceed with the test which shall be deemed to have been made in the Inspec-
tor's presence and Contractor shall forthwith forward to the Inspector, duly certified copies of
the test results in triplicate.
The employer/Inspector shall, within fourteen (14) days from the date of inspection as defined
herein, give notice in writing to the Contractor of any objection to any drawings and all or any
equipment and workmanship which in his opinion is not in accordance with the Contract. The
Contractor shall give due consideration to such objections and shall make the modifications
that may be necessary to meet said objections. When the factory tests have been completed at
the Contractor's or Sub-contractor's works, the employer/Inspector shall issue a certificate to
this effect within fourteen (14) days after completion of tests but if the tests are not witnessed
by the employer/Inspector, the certificate shall be issued within fourteen (14) days of receipt of
the Contractor's Test Certificate by the Employer/Inspector. The completion of these tests or
the issue of the certificates shall not bind the employer to accept the equipment should it, on
further tests after erection, be found not to comply with the Contract.
In cases where the Contract provides for tests, whether at the premises or works of the
Contractor or of any Sub-contractor, the Contractor except where otherwise specified shall
provide free of charge items such as labor, materials, electricity, fuel, water stores, apparatus
and instruments, as may be reasonably demanded by the employer/Inspector or his authorized
representative to carry out effectively such tests of the equipment in accordance with the
Contract and shall provide facilities to the employer/Inspector or his authorized representative
to accomplish testing.
The inspection by Employer and issue of Inspection Certificate thereon, shall in no way limit
the liabilities and responsibilities of the Contractor in respect of the agreed Quality Assurance
Program forming a part of the Contract.
The Contractor shall keep the Employer informed in advance of the time of starting of the
progress of manufacture of material in its various stages so that arrangements can be made for
inspection.
Record of routine test reports shall be maintained by the Contractor at his works for periodic
inspection by the Employer's representative.
Certificates of manufacturing tests shall be maintained by the Contractor and produced for
verification as and when desired by the Employer. No material shall be dispatched from its
point of manufacture until it has been satisfactorily inspected and tested. Testing shall always
be carried out while the inspection may be waived off by the Employer in writing only.
However, such inspection by the Employer's representative(s) shall not relieve the Contractor
from the responsibility for furnishing material, software, and equipment to conform to the
requirements of the Contract; nor invalidate any claim which the Employer may make because
of defective or unsatisfactory material, software or equipment.
Access to the Contractor's facilities while manufacturing and testing are taking place, and to
any facility where hardware/software is being produced for Employer shall be available to
Employer representatives. The Contractor shall provide to Employer representatives sufficient
facilities, equipment, and documentation necessary to complete all inspections and to verify
that the equipment is being fabricated and maintained in accordance with the Specification.
Inspection rights shall apply to the Contractor's facilities and to subcontractor facilities where
equipment is being manufactured.
Inspections will be performed by Employer, which will include visual examination of
hardware, enclosure cable dressings, and equipment and cable labeling. Contractor
documentation will also be examined to verify that it adequately identifies and describes all
wiring, hardware and spare parts. Access to inspect the Contractor's hardware quality assurance
standards, procedures, and records that are applicable to the facilities shall be provided to
Employer.
18.4.3 Inspection and Test
All materials furnished and all work performed under this Specification shall be inspected and
tested. Deliverables shall not be shipped until all required inspections and tests have been
completed, all deficiencies have been corrected to Employer’s satisfaction, and the equipment
has been approved for shipment by Employer.
Should any inspections or tests indicate that specific hardware, software or documentation does
not meet the Specification requirements, the appropriate items shall be replaced, upgraded, or
added by the Contractor as necessary to correct the noted deficiencies. After correction of a
deficiency, all necessary retests shall be performed to verify the effectiveness of the corrective
action.
The test shall be considered complete when (a) when all variances have been resolved (b) all
the test records have been submitted (c) Employer acknowledges in writing the successful
completion of the test.
18.4.3.1 Test Plans & Procedures
Test plans for both factory and field tests shall be provided by the Contractor to ensure that
each test is comprehensive and verifies all the features of the equipment are tested. The test
plans for factory and field tests shall be submitted for Employer approval before the start of
testing.
The contractor shall prepare detail testing procedure in line to specification and submit for
employer’s approval. The procedure shall be modular to the extent possible, which shall
facilitate the completion of the testing in the least possible time.
18.4.3.2 Test Records
The complete record of all factory and field acceptance tests results shall be maintained by the
Contractor. The records shall be maintained in a logical form and shall contain all the relevant
information. The test reports shall be signed by the testing engineer and the engineer witnessing
the tests.
18.4.3.3 Reporting of variances
A variance report shall be prepared by either Employer or Contractor personnel each time a
deviation from specification requirements is detected during inspection or testing. All such
variances shall be closed in mutually agreed manner.
However, at any stage if employer feels that quality of variances calls for suspension of the
testing the testing shall be halted till satisfactory resolution of variances, which may involve
retesting also.
18.4.3.4 Factory Test
The factory tests shall be conducted on all the equipments and shall include, but not be limited
to the following, appropriate to the equipment being tested:
a. Verification of all functional characteristics and requirements specified
b. Inspection and verification of all construction, wiring, labeling, documentation and
completeness of the hardware
Before the start of factory testing, the Contractor shall verify that all changes applicable to the
equipment have been implemented. As a part of the factory tests, unstructured testing shall be
performed for SCADA/DMS/OMS system to allow Employer representatives to verify proper
operation of the equipment under conditions not specifically tested in the above structured
performance test. The Contractor's test representative shall be present and the Contractor's
technical staff members shall be available for consultation with Employer personnel during
unstructured test periods. All special test facilities used during the structured performance test
shall be made available for Employer’s use during unstructured testing.
Unless otherwise specified in the relevant sections of the specification & except for
SCADA/DMS/OMS Hardware , Software, RTUs , the sampling size for FAT () is 10% and in
case any selected sample fails during the test, the failed samples shall be rejected and 20% of
the samples from the balance quantity shall be tested. If any failures are observed, the entire lot
shall be rejected.
18.4.3.5 Field Performance Test
After the equipment has been installed, the Contractor shall start up and check the performance
of the equipment of field locations. All hardware shall be aligned and adjusted, interfaces to all
inputs and outputs installed, operation verified, and all test readings recorded in accordance
with the Contractor's recommended procedures. The field performance test shall exhibit
generally all functions of the equipment and duplicate factory test. All variances must be
corrected prior to the start of the field performance test. The list of final tests to be carried out
in the field shall be listed in the site-testing document in line to the requirements specified in
the relevant sections of this volume.
18.5 Type Testing
The equipment being supplied shall conform to type tests as per technical specification and
shall be subjected to routine tests in accordance with requirements stipulated under respective
sections. The type test shall be conducted on the equipment if it is specifically mentioned in the
relevant section, for other equipment the type test report shall be submitted. Employer reserves
the right to witness any or all the type tests. The Contractor shall intimate the Employer the
detailed program about the tests at least three (3) weeks in advance in case of domestic supplies
& six (6) weeks in advance in case of foreign supplies.
The reports for all type tests as per technical specification shall be furnished by the Contractor
along with equipment / material drawings. The type tests conducted earlier should have either
been conducted in accredited laboratory (accredited based on ISO / IEC Guide 25 / 17025 or
EN 45001 by the national accreditation body viz. NABL / of the country where laboratory is
located) or witnessed by the representative(s) of Utility. However, type test reports shall not
more than 5 year old than the date of bid opening or validity of report by testing lab whichever
is lower.
In the event of any discrepancy in the test reports i.e. any test report not acceptable due to any
design / manufacturing changes or due to non-compliance with the requirement stipulated in
the Technical Specification or the type test(s) not carried out, same shall be carried out without
any additional cost implication to the Employer.
In case of failure during any type test, the Supplier at his own expenses shall modify the
equipment and repeat all type tests successfully at his own cost and within the project time
schedule.
Wherever, the make of the items is indicated in the technical specification, the type test reports
are not required to be submitted for the makes, indicated in the specification. For the new makes
(other than those indicated in the technical specification), type test reports as per relevant
standard shall be submitted for Employer’s approval.
18.6 Documentation
To ensure that the proposed systems conform to the specific provisions and general intent of
the Specification, the Contractor shall submit documentation describing the systems to
employer for review and approval. Further the contractor shall also submit the
drawings/documents for all the hardware & software required for site installation, testing and
commissioning and thereafter operation of the system. The contractor shall obtain approval of
employer for the relevant document at each stage before proceeding for manufacturing, system
development, factory testing, site testing, training etc. The schedule for submission/approval of
each document shall be finalized during the discussions before placement of the contract, this
schedule shall be in line to overall project schedule.
Each document shall be identified by a Contractor document number, the employer document
number, and the employer purchase order number. Where a document is revised for any reason,
each revision shall be indicated by a number, date, and description in a revision block along
with an indication of official approval by the Contractor's project manager. Each revision of a
document shall highlight all changes made since the previous revision.
The contractor shall submit two copies of each document/drawing for employer’s review and
approval. After approval five sets of all the documents shall be submitted as final
documentation, however, for site specific documents two sets of documents shall be provided
for each site. Any changes observed during field implementation shall be incorporated in the
as-build drawing and required sets of the same shall be submitted to employer/owner. In
addition to paper copies all the documents shall also be provided on electronic media in two
copies. In case any documentation requirement is specified in the relevant chapters , the same
shall apply for the equipment /system defined in that section. The contractor shall also supply
five sets of User manuals/guides/O&M manuals/manufacturer’s catalogues for all the hardware
& software supplied under the contract which shall be in addition to the one set each at all the
locations where the System has been installed. The user manual shall at minimum include the
principle of operation, block diagrams, troubleshooting and diagnostic and maintenance
procedures. Considering all the components of the project briefly the following
documents/drawings shall be required under the project.
a. System Description Documents (Overview)
b. Data Requirement sheets
c. Software Requirements Specification
d. Data base Documents
e. Drawings/Documents for manufacturing/Assembly of the equipment/system
f. Drawings/Documents for installation of the equipment/system at site
g. Software description/design documents for each software module
h. Testing Procedures and reports
i. Manuals for each equipment/hardware/test equipment
j. Bill of Quantities
k. Site Testing documents
l. Training documents
m. System Administrator Documents
n. User guide for Despatcher
However, all the above type of documents may not be required for each sub-system of the
project e.g. item (n) above may not be required for auxiliary power supply system, therefore,
the contractor shall submit a comprehensive list of the document as applicable for the offered
system for employer’s approval immediately after signing of the contract and the documents
shall be finalized as per the approved list. In regard to Data requirement sheets (DRS) for these
will be duly filled in by the bidder & submitted along with the bid. During detailed engineering,
contractor will be required to submit detailed DRS to include all technical parameters of the
equipment to ensure that the offered equipment meets all the technical specification
requirements
The Licensed Equipment manufacturers shall be able to manufacture, assemble, test, market
and sell the product as per OEM type tested design under technology transfer agreement. The
Licensed Equipment manufacturers should submit following documents
a) Licensed Equipment manufacturers should furnish Technology Licensee certificate or
agreement copy.
b) Licensed Equipment manufacturers should be able to furnish valid Type test certificate
from OEM.
c) Tender specific Authorization letter backed by OEM shall be submitted at the time of
tender.
Chapter 19
A ) DESIGN PARAMETERS AND PERFORMANCE TABLES
The SCADA/DMS system shall be designed as per the technical parameters defined in the
specification and the tables specified here. The SCADA/DMS/OMS system (such as databases,
network elements etc.) shall be sized to accommodate the requirement mentioned in table 7.
This chapter is applicable to Group A,B,C ,U towns as per functional requirements.
The system shall be tested with the doubled present power system size (ultimate capacity )
as defined in table 7& measure the various performance of the system as defined in the tables
and technical specification including peak and average load scenarios.
The auxiliary memory utilization , average CPU, RAM & LAN utilization parameters shall
not exceed the limits as defined in table 8. This memory utilization includes the memory used
for storage of data for the defined duration as specified in the various sections of technical
specification.
The SCADA/DMS system shall be suitable for addition of at least double the operator
workstations (in future) without requiring any up gradation of the servers.
The SCADA/DMS system design & performance parameters are defined in the following
tables:
Note ; The parameters which are not indicated in the tables & only mentioned
elsewhere in the specification shall also be considered as design parameters
2.3.6 Load priority Table Load priority table containing Monthly basis online
information such as breaker storage for 24 months
name, number of consumers
connected to each Breaker and
Load priority of each Breaker/
Feeder
2.3.7 SOE Data Table . All CBs, protection and alarm Minimum daily 4
contacts shall be considered as changes per SOE point
SOE. may be considered
Daily basis online
storage for 24 months
2.3.9 FPI fault table Table shall contain count and Minimum daily 4 faults
time of such FPI fault for O/C may be considered
and E/F Daily basis online
storage for 24 months
Action Performance
Complete database regeneration 2 hours
Complete system software build, including 6 hours
operating system, applications, and
Software build or all applications and databases 3 hours
Software build of a single applications and 10 minutes
Installation of a single, new display 60 seconds
including distribution to all consoles
Reinstallation of all displays 60 minutes
Perform an on-line update of a database parameter 60 seconds
and propagation of the change to the source data
Note Control system hardware & software shall be equipped & sized for for double
the size of the above
(b) UTILISATION
(Considering double the present power system size )
Name Average Comments
Utilization
PROCESSOR
Servers 30% Normal loading
50% Peak loading
LOCAL AREA
NETWORKS
15% Normal loading
40% Peak loading
2) PEAK LEVEL OF
ACTIVITY
The peak level of activity is an addition to the average level of activity described in (A)
NORMAL LEVEL OF ACTIVITY above. The peak level of activity shall be applied for a
five minute period. During the next ten minutes, only the normal level of system activity shall
be applied. This test shall be repeated for four consecutive fifteen minute periods, fora total
peak level test time of one hour. The five-minute peak loading period shall coincide with
SCADA/ DMS system period where all periodic software is scheduled for execution and at
least one five minute period shall span an hour boundary to consider the scheduled hourly
periodic activities. There shall be no restrictions on the period when the five-minute peak can
occur.
The software execution rates and response times defined in tables of this chapter, shall not
be degraded and the utilization defined in tables of this chapter shall not exceed during the
peak loading conditions. The following conditions shall define the additional peak level of
system activity:
(a) As per IEEE C37.1
a. 15 % of status of total status points/ 5sec measurements
b. 40% analog of total analog measurements /5sec
50% of the alarms shall be acknowledged within the five-minute period
(automatic acknowledgement is unacceptable).
The above are indicative, utility align with their Standard operating procedure
End of SCADA/DMS PERFORMANCE TABLES
Power Finance Corporation
SCADA/DMS, system under Part A –RDSS
Model Technical specification
Table 9
The BOQ shall be composite along with separate for break up for each Control center ( I.E. SCADA
/DMS & SCADA District Control center
A1) BILL OF QUANTITY
No. 2
Commnuication Server
Web/Directory server No. 2
Switches
Layer II switch (SCADA/DMS LAN) No. 2
Layer II switch ( Planning &
No. 2
Development system LAN)
Routers
Router for interfacing IT system &
No. 2
SCADA/DMS DR centre
Router at remote VDU No. 0
Security system (DMZ)
Web server with load balancing No. 2
Mail server No. 2
Router No. 2
Firewall & network IDS/IPS No. 2
Layer II switch No. 2
Other Active Devices
GPS Time synchronisation system Set 2
Time, day & date digital displays Set 1
Printers
Color inkjet printer Set 2
B/W Laser printer Set 2
Power Finance Corporation
SCADA/DMS, system under Part A –RDSS
Model Technical specification
Remarks
S.No. Equipment Unit Quantity
E1 RTUs
RTU base equipment comprising panels, racks, Per S/S
sub-racks, Power Supply modules, CPU,
interfacing equipment, required converters & all Ref
Set
other required items/accessories including remarks
complete wiring for all modules for locations
mentioned at Vol Vi
As per
Multifunctuions transducers No. Do point count
Power Finance Corporation
SCADA/DMS, system under Part A –RDSS
Model Technical specification
Do As per
Contact Multiplying Relays (CMRs) No. point count
Do As per
Heavy duty relays for Control No. point count
Dummy Breaker Latching Relays No. Do Per S/S
Remarks
S.No. Equipment Unit Quantity
Rs.
F1 FRTUs
Ref
Mini pole mounted FRTU base equipment remarks
along with enclosure suitable to work in
open environment (Adequate protection
from water & dust) , racks, sub-racks,
Power Supply modules with power backup Per
No.
, I/o modules, CPU, interfacing RMU/SECT
equipment, required converters & all other
required items/accessories including
complete wiring for all modules for
locations mentioned at Vol Vi
Ref
Contact Multiplying Relays (CMRs) No. Point count
remarks
Ref Point count
Heavy duty relays for Control No.
remarks
Ref Point count
Multifunction transducer No.
remarks
Any other hardware to meet functional
Lot -
/performance requirement of MTS
Sub-Total (Hardware) F1
F2 Test Equipments for FRTU
FRTU Database Configuration & Ref Per 100
No.
Maintenance Software tool remarks FRTU
Master Station cum FRTU Simulator & Ref Per 100
No.
Protocol analyser software tool remarks FRTU
Laptop PC for above software tools along Ref Per 100
No.
with interfacing hardware including Hub remarks FRTU
Sub-Total (Test equipment) F2
F3 MANDATORY SPARES FOR FRTU
5% of E1
Sub-Total (Spares) F3
Grand Total F
Power Finance Corporation
SCADA/DMS, system under Part A –RDSS
Model Technical specification
G1 - Communication system
Remarks
S.No Equipment Unit Quantity
MPLS
Per
Annual charges for 100MBps Links No. 0 RTU/CC/OTH
LOCATIONS
DO
MPLS Router No. 0
Sub - Total g1
GPRS/MPLS-4G
FRTU ,FPI
Modems No. 0
Remarks
S.No. Survey Type Unit Quantity
Main Equipments -
H1
Control centre
UPS with suitable rating
running in parallel Set Per CC
redundant mode*
VRLA type Battery banks
for above UPS for
minimum 30 min. backup
duration incl above Set
Power Finance Corporation
SCADA/DMS, system under Part A –RDSS
Model Technical specification
Sub- Total H1
Main Equipments - DR
H2
Centre
Main Equipments
SCADA ENABLERS
RMU No -
Sub- Total J1
J2 SECTIONLIZER /RECLOSER
Sectionlizer No -
Recloser No
Sub-Total J2
J3 FPI
Commnuicable No -
Sub-Total J3
RECONDUTORING (Specify type of
each conductor existing &
J4
reconductoring in other modernisation
WORKS if any )
Km -
Km -
Sub-Total J4
Control/power cable for RTUs from
J5 outdoor switchgear,if any at S/S and
numerical relays
control /power cable Km -
Numerical relay /BCPU Nos -
Sub-Total J5
J6 Mandatory Spares
5% of above J1 TO J5 -
Sub-Total J6
Grand Total (J)
Power Finance Corporation
SCADA/DMS, system under Part A –RDSS
Model Technical specification
Remarks
S.No. Equipment Unit Quantity
Server/ workstation
C1
Hardware
SCADA server No. 2
FEP server with interface
No. 2
switches
ISR server No. 2
NMS server No. 2
DTS server No. 1
Developmental server No. 1
Commnuication Server No. 2
Web/Directory server No. 2
SMS gaterway No. 2
*2minimum and 1 per
Ref
Workstation with dual TFT each 20s/s and maximum
Remarks
Monitors ( S/S monitoring) upto 5 workstations
Ref 1minimum *and 1 per each
Remarks per 100 FRTUs and
No.
Workstation with dual TFT maximum upto 3
Monitors (FPI monitoring) workstations
Workstation with dual TFT Ref *2minimum and 1 per
Monitors ( S/S monitoring) Remarks each 20s/s and maximum
-RTDAS upto 5 workstations
Ref 1minimum *and 1 per each
Workstation with dual TFT Remarks per 100 FRTUs and
No.
Monitors (FPI monitoring)- maximum upto 3
RTDAS workstations
Remote VDUs with one Ref 1 per Circle/ div/Sub div
No.
TFT Monitors Remarks
Developmental console
No. 2
with one TFT
DTS/Workstation Console
No. 2
with dual TFTs
DLP based Video
Projection system with 3x4
Module configuration with
No. 1
each module at least 70"
diagonal with projector
Switches
Layer II switch
No. 2
(SCADA/DMS LAN)
Layer II switch ( Planning
& Development system No. 2
LAN)
Routers
Router for interfacing IT
system & SCADA/DMS No. 2
DR centre
Router at remote VDU No. 0
Security system (DMZ)
Web server with load
No. 2
balancing
Mail server No. 2
Router No. 2
Firewall & network
No. 2
IDS/IPS
Layer II switch No. 2
Other Active Devices
GPS Time synchronisation
Set 2
system
Time, day & date digital
Set 1
displays
Printers
Color inkjet printer Set 2
B/W Laser printer Set 2
Any other items required
to meet functional
Lot 1
/Performance
requirement as per UMTS
Sub-Total C1 (Hardware)
Software for Control
C2
Centre
SCADA software Lot 1
ISR Software Lot 1
DMS software Lot 1
DTS software Lot 1
Developmental software Lot 1
Network Management
Lot 1
Software
Power Finance Corporation
SCADA/DMS, system under Part A –RDSS
Model Technical specification
DR
Remarks
S.No. Equipment Unit Quantity
Switches
Layer II switch (DR LAN) No. 2
Routers
Router for interfacing at SCADA DMS
No. 2
centre
Printers
Color inkjet printer Set 1
Sub-Total D1 Hardware
D2 Software for Control Centre
RDBMS package Lot 1
Any other items required to meet
functional /Performance requirement as Lot 1
per UMTS
Sub-Total D1 Sofware
D3 Mandatory spares Max 5% of D1
Mandatory spares L/S 1
Remarks
S.No. Equipment Unit Quantity
E1 RTUs
RTU base equipment comprising panels, racks, Per S/S
sub-racks, Power Supply modules, CPU,
interfacing equipment, required converters & all Ref
Set
other required items/accessories including remarks
complete wiring for all modules for locations
mentioned at Vol Vi
As per
Multifunctuions transducers No. Do point count
Do As per
Contact Multiplying Relays (CMRs) No. point count
Do As per
Heavy duty relays for Control No. point count
Dummy Breaker Latching Relays No. Do Per S/S
G1 - Communication system
Remarks
S.No Equipment Unit Quantity
MPLS
Per
Annual charges for 100MBps Links No. 0 RTU/CC/OTH
LOCATIONS
DO
MPLS Router No. 0
Sub - Total g1
GPRS/MPLS-4G
, FPI
Modems No. 0
Remarks
S.No. Survey Type Unit Quantity
Main Equipments -
H1
Control centre
UPS with suitable rating
running in parallel Set Per CC
redundant mode*
VRLA type Battery banks
for above UPS for
minimum 30 min. backup
duration incl above Set
Sub- Total H1
Main Equipments - DR
H2
Centre
Main Equipments
UPS with suitable rating
running in parallel Per DR
redundant mode*
VRLA type Battery banks
for above UPS for
minimum 30 min. backup
duration incl above
Sub-Total H2
II For RTU / Data
H3 Concentrator /
Communication Eqpts.
DC Power Supply
(DCPS) system based on - PER RTU
SMPS
SCADA ENABLERS
J3 FPI
Commnuicable No -
Sub-Total J3
Control/power cable for RTUs from
J5 outdoor switchgear,if any at S/S and
numerical relays
control /power cable Km -
Sub-Total J5
J6 Mandatory Spares
5% of above J1 TO J5 -
Sub-Total J6
Grand Total (J)
DO AI
Com DI modul mod
STATION SS DS DC CMR HDR MFT
module module e ule
TOTAL
RTU I/O COUNT
Note: - SS : Single status input, DS : Double status input for CBs, DC : Digital Control Output (Trip &
Close)/Raise /lower CMR : Contact Multiplying Relay, HDR : Heavy Duty Relay, METER : Energy
meter, CM: Communication Module , DI : Digital input , DO : Digital Output AI: Analog module
Power Finance Corporation
SCADA/DMS, system under Part A –RDSS
Model Technical specification
Note: 6. MFT provide data that is to be acquired by RTU on Modbus/or IEC protocol for Voltage (phase to phase and phase to neutral),Current (phase
and neutral), Active Power, Reactive Power, Apparent Power, Power Factor, Frequency, active energy (import & export), reactive energy (import
& export) etc.
7. CMRs shall be mounted in the existing C&R panels. Wherever the space is not available in the existing panels the same shall be
mounted in the RTU panels. Heavy Duty Relays shall be provided for Digital outputs for CBs and shall be mountedin the RTU panels
itself.
8. The RTU shall be equipped for the above specified I/O (analog input (meter), digital input & digital output) point points, which includes 20
% spare for future use (except for CMRs & HDRs). These 20 % spare points shall be terminated on terminal blocks in
9. All protection relay/Alarm points & CBs shall be considered for SOE.
10. Point counts include three alarms per station for auxiliary system and fire, which shall be interfaced to RTU.
Note: 1. MFT provide data that is to be acquired by RTU on Modbus/or IEC protocol for Voltage (phase to phase and phase to
neutral),Current (phase and neutral), Active Power, Reactive Power, Apparent Power, Power Factor, Frequency, active energy
2. CMRs shall be mounted in the existing C&R panels. Wherever the space is not available in the existing panels the same shall be mounted
panels. Heavy Duty Relays shall be provided for Digital outputs for CBs and shall be mounted in the RTU panels itself.
3. The RTU shall be equipped for the above specified I/O (analog input MFT), digital input & digital output) point points, which includes 20
future use . These 20 % spare points shall be terminated on terminal blocks in RTU panel.
4. All protection relay/Alarm points & CBs shall be considered for SOE.
D) BILL OF QUANTITY
FRTU
UTILTY SHALL ATTACH RTU & FRTUCONNECTIVITY DIAGRAM
TOTAL
Note: - SS : Single status input, DS : Double status input for CBs, DC : Digital Control Output (Trip & Close) CMR :
Contact Multiplying Relay, HDR : Heavy Duty Relay, METER : Energy meter, CM:Communication Module , DI :
Digital input , DO : Digital Output: AI: Analog input
Power Finance Corporation
SCADA/DMS, system under Part A –RDSS
Model Technical specification
UTILTY SHALL ATTACH COMMNUICATION NETWORK DIAGRAM FOR ALL PROPOSED MODES
B. Maintenance Training
1 Computer Hardware & System 10 2 Per Control center
Software
2. Application Software (SCADA/DMS/OMS ) 10 2 Per Control center
3. RTU & FRTU 5 2 Per Town
4. Database & display development 5 2 Per Control center
6. Auxiliary Power Supply 3 2 Per Control center
7. NMS/ Communication 5 2 Per Control center
8. SCADA enablers( 2 Per Town
RMU/SECTIONLIZER/FPIetc.)
I) FMS
The cost of shall not be less than 25 % of total contract value . The cost per year for all 5 year shall be same
The necessary spares required for maintenance of the system during FMS shall beprovided by the
contractor. However, the consumables shall be provided by the owner.
FMS shall include all the supplied hardware & software under the project.
o FMS for 2 years after operational acceptance or up to Sunset of scheme is
provisionedunder GOI sanction (whichever is earlier) and remaining period totaling
to 5 years after operational acceptance will be borne by utility. However, the cost
of all 5 years shall be same and will form part of financial evaluation .
Bidder can define quantity of servers , router, switches as per system configuration in the bid subject to
adherence to functional , performance , redundancy , cyber security and all technical & SLA
requirements
Unit price is inclusive of taxes , freight and insurance, However , GST % to be indicated by bidder for
items
Power Finance Corporation
SCADA/DMS, system under Part Revamped Reforms-Linked Results-based
Distribution Sector Scheme - Govt. of India
Model Technical specification
J) IMPLEMENTATION SCHEDULE
Page 313 of 19
Power Finance Corporation
SCADA/DMS, system under Part Revamped Reforms-Linked Results-based
Distribution Sector Scheme - Govt. of India
Model Technical specification
Page 314 of 19
Power Finance Corporation
SCADA/DMS, system under Part Revamped Reforms-Linked Results-based
Distribution Sector Scheme - Govt. of India
Model Technical specification
SNO A/U NAME OF RTU Count FRTU count FPI Count RMU Sectionlizer
TOWN Count count
Page 315 of 19
Power Finance Corporation
SCADA/DMS, system under Part Revamped Reforms-Linked Results-based
Distribution Sector Scheme - Govt. of India
Model Technical specification
Page 316 of 19
Section VII.
General Conditions of Contract
A. Contract and Interpretation
1 Definitions The following words and expressions shall have the meanings hereby
assigned to them:
(a) “Contract” means the Agreement entered into between the
Purchaser and the Supplier, together with the Contract
Documents referred to therein, including all attachments,
appendices, and all documents incorporated by reference
therein.
(b) “Contract Documents” shall mean the following documents listed,
including any amendments thereto be read and construed as part
of this Agreement, viz.:
3.11 Severability
5 Governing Law 5.1 The Contract shall be governed by and interpreted in accordance with
the laws of the India. The High Court of Judicature at Utility Head
Quarters and Courts subordinate to such High Courts shall have
exclusive jurisdiction in respect of any disputes relating to the
tendering process, award of Contract and execution of the Contract.
6 Settlement of 6.1 The Utility and the Contractor shall make every effort to resolve
Disputes amicably by direct informal negotiation any disagreement or dispute
arising between them under or in connection with the Contract.
6.2 If the parties fail to resolve such a dispute (The date of commencement
of the dispute shall be taken from the date when this clause
reference is quoted by either party in a formal communication clearly
mentioning existence of dispute or as mutually agreed) or difference
by mutual consultation within twenty-eight (28) days from the
commencement of such consultation, either party may require that
the dispute be referred for resolution to the formal mechanisms
specified in the SCC.
6.3 In the event of any dispute or difference relating to the interpretation
and application of the provisions of commercial contract (s) between
Central Public Sector Enterprises (CPSEs)/ Port Trusts inter se and also
between CPSEs and Government Departments/ Organizations
(excluding disputes concerning Railways, Income Tax, Customs &
Excise Departments), such disputes or difference shall be taken up by
either party for resolution through Administrative Mechanism for
Resolution of CPSEs Disputes (AMRCD) as mentioned in DPE Office
Memorandum No. 4(1)/2013- DPE(GM)/FTS-1835 dated 22.05.2018 or
any amendments thereof.
B Subject Matter of Contract
7 Scope of Work 7.1 The Goods and Related Services to be supplied are specified in Appendix-
C3. At the time of awarding the contract, the Utility shall specify any
change in the Scope of Work. Such changes may be due for instance,
if the quantities of goods and related services are increased or
decreased at the time of award.
7.2 Unless otherwise stipulated in the Contract, the Scope of Work shall
include all such items not specifically mentioned in the Contract but
that can be reasonably inferred from the Contract as being required for
attaining Delivery and Completion of the Goods and Related Services
as if such items were expressly mentioned in the Contract.
8 Delivery 8.1 Subject to GCC Sub-Clause 33, the Delivery of the Goods and Completion
of the Related Services shall be in accordance with the Implementation
chapter 19 Table 9 . The details of shipping and other documents to be
furnished by the Contractor are specified in the SCC.
9 Contractor’s 9.1 The Supplier shall supply all the Goods and Related Services included in
Responsibilities the Scope of Work and Appendix-C3 in accordance with GCC Clause 7,
and the Implementation Schedule, as per GCC Clause 8.
9.2 The Contractor confirms that it has entered into this Contract on the
basis of a proper examination of the data relating to the Facilities
provided by the Utility and on the basis of information that the
Contractor could have obtained from a visual inspection of the Site (if
access thereto was available) and of other data readily available to it
relating to the Facilities as at the date fifteen (15) days prior to
deadline set for price bid submission. The Contractor acknowledges
that any failure to acquaint itself with all such data and information
shall not relieve its responsibility for properly estimating the difficulty
or cost of successfully performing the Facilities.
9.3 The Contractor shall acquire in its name all permits, approvals and/or
licenses from all local, state or national government authorities or
public service undertakings in the country where the Site is located that
are necessary for the performance of the Contract, including, without
limitation, visas for the Contractor’s and Subcontractor’s personnel and
entry permits for all imported Contractor’s Equipment. The Contractor
shall acquire all other permits, approvals and/or licenses that are not
the responsibility of the Employer under GCC Sub-Clause 10 hereof and
that are necessary for the performance of the Contract.
9.4 The Contractor shall comply with all laws in force in the country where
the Facilities are installed and where the Installation Services are
carried out. The laws will include all national, provincial, municipal or
other laws that affect the performance of the Contract and bind upon
the Contractor. The Contractor shall indemnify and hold harmless the
Employer from and against any and all liabilities, damages, claims,
fines, penalties and expenses of whatever nature arising or resulting
from the violation of such laws by the Contractor or its personnel,
including the Subcontractors and their personnel,
but without prejudice to GCC Clause 9 hereof.
10 Utility’s 10.1 Whenever the supply of Goods and Related Services requires that the
Responsibilities Supplier obtain permits, approvals, and import and other licensesfrom
local public authorities, the Utility shall, if so required by the Supplier,
make its best effort to assist the Supplier in complying with such
requirements in a timely and expeditious manner.
10.2 The Purchaser shall bear all costs involved in the performance of its
responsibilities, in accordance with GCC Sub-Clause 14.1.
10.3 The Project Manager or any other person designated by the
utility, as defined in SCC, shall act as the nodal point for
implementation of the contract and for issuing necessary instructions,
approvals, commissioning, acceptance certificates, payments etc. to
the Supplier.
10.4 The Project Manager or any other person designated by the utility shall
approve all such documents within 15 working days.
10.5 Purchaser may provide on Supplier’s request, particulars/ information
/ or documentation that may be required by the Supplier for proper
planning and execution of Scope of Work under this contract.
10.6 Purchaser shall provide to the Supplier sitting space and infrastructure
and utilities, in the Purchaser’s offices at such location as may be
mutually decided by the Parties.
C. Payment
11 Contract Price 11.1 The Contract Price shall be as specified in the Agreement subject to any
additions and adjustments thereto, or deductions there from, as may
be made pursuant to the Contract as also subject to provisionsof
Clause 14.5.
11.2 Prices charged by the Supplier for the Goods delivered and the Related
Services performed under the Contract shall not vary from the prices
quoted by the Supplier in its bid, with the exception of any price
adjustments authorized in the SCC.
11.3 In the event any approval required for imports and/ or use of imported
equipment is denied in accordance with all applicable laws including
those in relation to testing issued by Ministry of Power (Order No
No.12/34/2020-T&R dated 08 June 2021, as amended and/ or modified
from time to time), the same shall neither entitle revision of Contract
Price nor shall result in revision of the Project
Implementation Plan.
12 Terms of 12.1 The Contract Price shall be paid in the manner specified in the SCC. No
Payment invoice for extra work/change order on account of change order will be
submitted by the Supplier unless the said extra work /change orderhas
been authorized/approved by the Utility in writing.
12.2 The Contractor’s request for payment shall be made to the Utility in
writing, accompanied by invoices describing, as appropriate, the Goods
delivered and Related Services performed, accompanied by the
documents submitted.
12.3 Payments shall be made promptly by the Utility, no later than forty five
(45) days after submission of an invoice or request for payment bythe
Contractor, and the Utility has accepted it.
12.4 If any excess payment has been made by the Purchaser due to
difference in quoted price in proposal and Supplier’s invoice, the
purchaser may without prejudice to its rights recover such amounts by
other means after notifying the Supplier or deduct such excess
payment from any payment subsequently falling due to the Supplier.
12.5 The currency in which payment shall be made to the supplier under
this contract is Indian Rupees (INR).
13 Securities 13.1 Issuance of Securities
The Contractor shall provide the securities specified below in favor of
the Employer at the times, and in the amount, manner and form
specified below.
13.2 Advance Payment Security
(a) The Contractor shall, within twenty-eight (28) days of the
Notification of Award of Contract, provide a security in an
amount equal to the advance payment calculated in
accordance with Terms and Procedures of Payment to the
Contract Agreement, and in the currency or currencies of the
Contract, with an initial validity of up to ninety (90) days
beyond the schedule date of Completion of the last facility
covered under the package. However, in case of delay in
completion of the facilities under the package, the validity of
this security shall be extended by the period of such delay. The
advance payment security shall also cover the amount of GST
as applicable on the advance payment to be paid to the
contractor.
(b) The security shall be in the form of an unconditional bank
guarantee as per the proforma provided as Form of Advance
Payment Security. The Advance payment Security shall be
reduced pro-rata every three (03) months after First Running
Account Bill/Stage Payment under the Contract based on the
value of the respective equipment/facilities received and
applicable GST. The cumulative amount of reduction at any
point of time shall not exceed ninety (90%) of the advance and
the amount of GST paid on the advance amount
corresponding to cumulative value of the respective
equipment/Facilities supplied and received as per certificate
issued by the Project Manager. The balance shall be released
upon release of respective milestone linked payments as
identified in Terms of payments of Contract Agreement. In
case milestone payment is not envisaged in the package, the
balance shall be released after Completion of those Facilities
on certification by the Project Manager. It should be clearly
understood that reduction in the value of security for advance
shall not in any way dilute the Contractor's responsibility and
liabilities under the Contract including in respect of the
Facilities for which the reduction in the value of security is
allowed
13.3 Performance Security
(a) The Contractor shall, within twenty-eight (28) days of the
Notification of Award, provide securities for the due
performance of the Contract for ten percent (10%) of the
Contract Price of all the Contracts, with an initial validity up to
ninety (90) days beyond the end of scheduled Defect Liability
Period of the last equipment covered under the Contract.
However, in case of delay in completion of the defect liability
period, the validity of all the contract performance securities
shall be extended by the period of such delay.
(b) The performance security shall be denominated in the
currency or currencies of the Contract, or in a freely
convertible currency acceptable to the Utility, and shall be in
the form of unconditional bank guarantee provided as Form
of Performance Security of the bidding documents.
(c) Unless otherwise stipulated in SCC, the security shall be
reduced pro rata to the Contract Price of a part of the Facilities
for which a separate time for Completion is provided, twenty
one (21) months after Completion of the Facilities or where
relevant part thereof, or fifteen (15) months after Operational
Acceptance of the Facilities (or the relevant part thereof),
whichever occurs first; provided, however, that if the Defects
Liability Period has been extended on any part of the Facilities
pursuant to GCC Sub- Clause 33 hereof, the Contractor shall
issue an additional security in an amount proportionate to the
Contract Price of that part. The security shall be returned to
the Contractor immediately after its expiration, provided,
however, that if the Contractor, pursuant to GCC Sub-Clause
33, is liable for an extended warranty obligation, the
performance security shall be extended for the period and up
to the amount agreed upon or as specified in the SCC.
(d) The Purchaser shall at its sole discretion invoke the
Performance Security and appropriate the amount secured
there under, in the event that the Supplier commits any delay
or default in Delivery of the Goods or Related Services during
the contract period (including FMS period) or commits any
other breach of the terms and conditions of the Contract.
14 Taxes and Duties 14.1 The prices quoted by the supplier shall be inclusive of all
duties/taxes/levies . Responsibility for including all applicable
taxes/duties/levies in the proposal lie with the supplierand the utility
shall not be responsible for any error/omission on the part of the
bidder. Payment of taxes/duties/levies except GST shall not be made
separately.
14.2 For goods supplied from outside the Purchaser’s country, the Supplier
shall be entirely responsible for all taxes, duties, stamp duties, license
fees, and other such levies imposed outside the Purchaser’s country.
14.3 For goods supplied from within the Purchaser’s country, the Supplier
shall be entirely responsible for all taxes, duties, entry tax, license fees,
other levies etc, incurred until delivery of the Goods and
Related service to the Purchaser.
14.4 The cost of Entry Tax as applicable will be the liability of the Supplier
i.e. the price quoted will be inclusive of Entry Tax. The amount of Entry
Tax will be deducted from the Supplier’s invoice and remittanceto tax
dept. will be made by the Purchaser under the TIN number of
Purchaser. If any liability is raised by the commercial tax department,
Govt. of <STATE> on account of Entry Tax at a later date, the same
shall be to the Supplier's account and accordingly recovery shall be
made from the supplier's pending bills/security deposit as available
with the Purchaser.
14.5 For the purpose of the Contract, it is agreed that the Contract Price
specified in (Contract Price and Terms of Payment) of the Contract
Agreement is based on the taxes, duties, levies and chargesprevailing
on seven (7) days prior to the deadline set for price bid submission in
the country where the Site is located (hereinafter called “Tax” in this
GCC Sub-Clause 14.4). If any rates of Tax are increased or decreased, a
new Tax is introduced, an existing Tax is abolished, or any change in
interpretation or application of any Tax occurs in the course of the
performance of Contract, which was or 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
into account any such change by addition to the Contract Price or
deduction therefrom, as the case may be, in accordance with GCC
Clause 30 (Change in Laws and Regulations) hereof. However, these
adjustments shall not be applicable on procurement of raw materials,
intermediary components and intermediary services etc. by the
Contractor.
D. Intellectual Property
15 Copyright 15.1 Purchaser shall own and have a right in perpetuity to use all newly
created Intellectual Property Rights which have been developed solely
during execution of this Contract, including but not limited to all
Source code, Object code, records, reports, designs, application
configurations, data and written material, products, specifications,
reports, drawings and other documents which have been newly
created and developed by the Supplier solely during the performance
of Related Services and for the purposes of inter-alia use or sub-
license of such Services under this Contract. The Supplier undertakes
to disclose all such Intellectual Property Rights arising in performance
of the Related Services to the Purchaser and execute all such
agreements/documents and file all relevant applications, effect
transfers and obtain all permits and approvals that may be necessary
in this regard to effectively transfer and conserve the Intellectual
Property Rights of the Purchaser. To the extent that Intellectual
Property Rights are unable by law to so vest, the Supplier assigns those
Intellectual Property Rights to Purchaser oncreation.
15.2 The Supplier shall be obliged to ensure that all approvals, registrations,
licenses, permits and rights etc. which are inter-alia necessary for use
of the goods supplied / installed by the Supplier,the same shall be
acquired in the name of the Purchaser, and the same may be assigned
by the Purchaser to the Supplier solely for the purpose of execution of
any of its obligations under the terms of this Contract. However,
subsequent to the term of this Contract, such approvals, registrations,
licenses, permits and rights etc. shall endure to the exclusive benefit
of the purchaser.
15.3 The Supplier shall ensure that while it uses any software, hardware,
processes, document or material in the course of performing the
Services, it does not infringe the Intellectual Property Rights of any
person and the Supplier shall keep the Purchaser indemnified against
all costs, expenses and liabilities howsoever, arising out any illegal or
unauthorized use (piracy) or in connection with any claim or
proceedings relating to any breach or violation of any
permission/license terms or infringement of any Intellectual Property
Rights by the Supplier or its personnel during the course of
performance of the Related Services. In case of any infringement by
the Supplier, the Supplier shall have sole control of the defense and all
related settlement negotiations.
15.4 Subject to sub-clauses 16.1 to 16.3, the Supplier shall retain exclusive
ownership of all methods, concepts, algorithms, trade secrets,
software documentation, other intellectual property or other
information belonging to the Supplier that existed before the effective
date of the contract.
16 Confidential 16.1 Both parties undertake to each other to keep confidential all
Information information (written as well as oral) concerning the business and
affairs of the other, which has been obtained or received as a result
of the discussions leading upto or the entering of the contract
16.2 After the entering of the contract the Purchaser and the Supplier shall
keep confidential and shall not, without the written consent of the
other party hereto, divulge to any third party any documents, data, or
other information furnished directly or indirectly by the other party
hereto in connection with the Contract, whether such information has
been furnished prior to, during or following completion or termination
of the Contract. Notwithstanding the above, the Supplier may furnish
to its Subcontractor such documents, data, and other information it
receives from the Purchaser to the extent required for the
Subcontractor to perform its work under the Contract, in which event
the Supplier shall obtain from such Subcontractor an undertaking of
confidentiality similar to that imposed on the Supplier under this
Clause.
16.3 The Purchaser shall not use such documents, data, and other
information received from the Supplier for any purposes unrelated to
the Contract. Similarly, the Supplier shall not use such documents,
data, and other information received from the Purchaser for any
purpose other than the design, procurement, or other work and
services required for the performance of the Contract.
16.4 The obligation of a party under GCC Sub-Clauses 16.1 and 16.2 above,
however, shall not apply to information that:
a. the Purchaser or Supplier need to share with the institutions
participating in the financing of the Contract;
b. now or hereafter enters the public domain through no fault of that
party;
c. can be proven to have been possessed by that party at the time of
disclosure and which was not previously obtained, directly or
indirectly, from the other party; or
d. Otherwise lawfully becomes available to that party from athird party
that has no obligation of confidentiality.
16.5 The above provisions of GCC Clause 16 shall not in any way modify
any undertaking of confidentiality given by either of the parties
hereto prior to the date of the Contract in respect of the Supply or
any part thereof.
16.6 Each of the parties to this contract, undertakes to the other to take
all such steps as shall from time to time be necessary to ensure
compliance with the provisions of the above clauses by it’s
employees, agents and sub-contractors.
16.7 The provisions of GCC Clause 17 shall survive completion or
termination, for whatever reason, of the Contract.
E. Work Execution
21 Packing and 21.1 The Supplier shall provide such packing of the Goods as is requiredto
Documents prevent their damage or deterioration during transit to their final
destination, as indicated in the Contract. During transit, the packing
shall be sufficient to withstand, without limitation, rough handling and
exposure to extreme temperatures, salt and precipitation, and open
storage. Packing case size and weights shall take into consideration,
where appropriate, the remoteness of the final destination of the
Goods and the absence of heavy handling facilities at all points in
transit. The Purchaser shall not be responsible in any manner for any
loss or damage caused to the Goods during Transit.
21.2 The packing, marking, and documentation within and outside the
packages shall comply strictly with such special requirements as shall
be expressly provided for in the Contract and in any other
instructions ordered by the Purchaser.
22 Insurance 22.1 The Goods supplied under the Contract shall be fully insured by the
Supplier, in INR, against loss or damage incidental to manufacture or
acquisition, transportation, storage, and delivery, in accordance with
the applicable Incoterms or in the manner specified in the SCC.
23 Transportation 23.1 Obligations for transportation of the Goods shall be borne by the
Supplier and shall be in accordance with the Incoterms specified in
Sections VII
24 Inspections and 24.1 The Supplier shall at its own expense and at no cost to the Purchaser
Tests carry out all such tests and/or inspections of to ensure that the Goods
and Related Services are complying with the functional parameters,
codes and standards specified in the Scope of Work at Section VI, to
the satisfaction of the Purchaser.
24.2 The inspections and tests may be conducted on the premises of the
Supplier, at point of delivery, and/or at the final destination of the
Goods, or in another place in the Purchaser’s country as per the
requirement of Section VI. Subject to GCC Sub-Clause 24.3, if
conducted on the premises of the Supplier or its Subcontractor, all
reasonable facilities and assistance, including access to drawings and
production data, shall be furnished to the inspectors at no charge to
the Purchaser.
24.3 The Purchaser or its designated representative shall be entitled to
attend the tests and/or inspections referred to in GCC Sub-Clause 24.2,
provided that the Purchaser bear all of its own costs and expenses
incurred in connection with such attendance including, but not limited
to, all traveling and board and lodging expenses.
24.4 Whenever the Supplier is ready to carry out any such test and
inspection, it shall give a reasonable advance notice, including the
place and time, to the Purchaser.
24.5 The Purchaser may require the Supplier to carry out any test and/or
inspection to verify that the characteristics and performance of the
Goods or Related Services comply with the technical specifications,
codes and standards under the Contract.
24.6 The Supplier shall provide the Purchaser with a report of the results
of any such test and/or inspection.
24.7 The Purchaser may reject any Goods / Related Services or any part
thereof that fail to pass any test and/or inspection or do not conform
to the specifications. The Supplier shall either rectify or replace such
rejected Goods/ Related Services or parts thereof or make alterations
necessary to meet the specifications at no cost to the Purchaser, and
shall repeat the test and/or inspection, at no cost to the Purchaser,
upon giving a notice pursuant to GCC Sub-Clause 24.4.
24.8 The Supplier agrees that neither the execution of a test and/or
inspection of the Goods / Related Services or any part thereof, nor
the attendance by the Purchaser or its representative, nor the issue
of any report pursuant to GCC Sub-Clause 24.6, shall release the
Supplier from any warranties or other obligations under the Contract.
30 Change in Laws 30.1 Unless otherwise specified in the Contract, if after the date of the
and Regulations Invitation for Bids, any law, regulation, ordinance, order or bylaw
having the force of law is enacted, promulgated, abrogated, or
changed in the place of the Purchaser’s country where the Site is
located (which shall be deemed to include any change in
interpretation or application by the competent authorities) that
subsequently affects the Delivery Date, then such Delivery Date shall
be correspondingly increased or decreased, to the extent that the
Supplier has thereby been affected in the performance of any of its
obligations under the Contract. Additional clause of AMISP Bid
Document creates a ambiguity w.r.t. clause Contract Prices
31 Force 31.1 The Supplier shall not be liable for forfeiture of its Performance
Majeure Security, liquidated damages, or termination for default if and to the
extent that it’s delay in performance or other failure to perform its
obligations under the Contract is the result of an event of Force
Majeure.
31.2 For purposes of this Clause, “Force Majeure” means an event or
situation beyond the control of the Supplier that is not foreseeable,
is unavoidable, and its origin is not due to negligence or lack of care
on the part of the Supplier. Such events may include, but not be
limited to wars or revolutions, earthquake, fires, floods, epidemics,
quarantine restrictions, and freight embargoes.
31.3 If a Force Majeure situation arises, the Supplier shall promptly andno
later than seven days from the first occurrence thereof, notify the
Purchaser in writing of such condition and the cause thereof. Unless
otherwise] directed by the Purchaser in writing, the Supplier shall
continue to perform its obligations under the Contract as far as is
reasonably practical, and shall seek all reasonable alternative means
for performance not prevented by the Force Majeure event.
31.4 The decision of the Purchaser with regard to the occurrence,
continuation, period or extent of Force Majeure shall be final and
binding on the Supplier.
H. Change in Contract Elements
32 Change Orders 32.1 The Purchaser may at any time order the Supplier through Notice in
and Contract accordance GCC Clause 4 ,12.1, Section VI to make changes within
Amendments the general scope of the Contract in any one or more of the following:
(a) drawings, designs, or specifications, where Goods to be
furnished under the Contract are to be specifically
manufactured for the Purchaser;
(b) Specifications for hardware, software and Related Services
(c) the method of shipment or packing;
(d) the place of delivery; and
(e) the Related Services to be provided by the Supplier.
32.2 If any such Change Order causes an increase or decrease in the cost of,
or the time required for, the Supplier’s performance of any provisions
under the Contract, an equitable adjustment shall be made in the
Contract Price or in the Delivery and Completion Schedule, or both,
and the Contract shall accordingly be amended. Any claims by the
Supplier for adjustment under this Clause must be asserted within
twenty-eight (28) days from the date of the
Supplier’s receipt of the Purchaser’s Change Order.
32.3 No variation or modification of the terms of the contract shall be
made except by written amendment signed by the parties.
33 Extensions 33.1 If at any time during performance of the Contract, the Supplier or its
of Time Subcontractors should encounter conditions impeding timelydelivery
of the Goods or completion of Related Services pursuant to GCC
Clause 10, the Supplier shall promptly notify the Purchaser in writing
of the delay, its likely duration, and its cause. As soon as practicable
after receipt of the Supplier’s notice, the Purchaser shall evaluate the
situation and may at its discretion extend the Supplier’s time for
performance, in which case the extension shall be ratified by the
parties by amendment of the Contract.
33.2 Except in case of Force Majeure, as provided under GCC Clause 31 or
where the delay in delivery of the Goods or completion of Related
Services is caused due to any delay or default of the Purchaser, any
extension granted under clause 32.1 shall not absolve the Supplier
from its liability to the pay of liquidated damages pursuant to GCC
Clause 26.
34 Termination 34.1 Termination for Default
(a) The Purchaser may, without prejudice to any other remedy for
breach of Contract, by Notice of default sent to the Supplier,
terminate the Contract in whole or in part:
i. if the Supplier fails to deliver any or all of the Goods or
Related Services within the period specified in the
Contract, or within any extension thereof granted by
the Purchaser pursuant to GCC Clause 32; or
ii. if the Supplier, in the judgment of the Purchaser has
engaged in corrupt, fraudulent, collusive, or coercive
practices, as defined in ITB Clause 4, in competing for
or in executing the Contract; or
iii. Any representation made by the bidder in the
proposal is found to be false or misleading
iv. if the Supplier commits any breach of the Contract and
fails to remedy or rectify the same within the period
of two weeks (or such longer period as the Purchaser
in its absolute discretion decide) provided in a notice
in this behalf from the Purchaser.
v. as specified in the SLA
35 Assignment 35.1 The Contractor shall not, without the express prior written consent of
the Employer, assign to any third party the Contract or any part thereof,
or any right, benefit, obligation or interest therein or thereunder,
except that the Contractor shall be entitled to assign either absolutely
or by way of charge any monies due and payable to it or that may
become due and payable to it under the Contract.
36 Disclaimer 36.1 Purchaser reserves the right to share, with any consultant of its
choosing, any resultant Proposals in order to secure expert opinion.
36.2 Purchaser reserves the right to accept any proposal deemed to be in
the best interest of the Utility.
I. Other Conditions
37 Public 37.1 All materials provided to the Purchaser by bidder are subject to Country
Disclosure and <STATE> public disclosure laws such as RTI etc.
37.2 The Supplier’s Team shall not make or permit to be made a public
announcement or media release about any aspect of this Contract
unless the Purchaser first gives the Supplier its written consent.
38 SLA Audit 38.1 A designated team / person from <UTILITY> will review the performance
of Supplier against the SLA each month. The review / audit report will
form basis of any action relating to imposing penalty
on or breach of contract of the Supplier.
Model Bid Document for Appointment of SCADA/DMS Implementation Agency by Power
Distribution Utility
39 Adherence to 39.1 Supplier shall comply with the provision of all laws including labour laws,
safety rules, regulations and notifications issued there under from time to
procedures, time. All safety and labour laws enforced by statutory agencies and by
rules Purchaser shall be applicable in the performance of this Contract and
regulations and Supplier’s Teamshall abide by these laws.
restriction 39.2 Access to the Datacenter Sites and Purchaser’s locations shall be strictly
restricted. No access to any person except the essential personnel
belonging to the Supplier who are genuinely required for execution of
work or for carrying out management/maintenance who have been
explicitly authorised by the Purchaser shall be allowed entry to the
Datacenter Sites and some Purchaser’s locations. Even if allowed,
access shall be restricted to the pertaining equipment of the Purchaser
only. The Supplier shall maintain a log of all activities carriedout by each
of its personnel.
39.3 The Supplier shall take all measures necessary or proper to protect the
personnel, work and facilities and shall observe all reasonable safety
rules and instructions. Supplier’s Team shall adhere to all security
requirement/regulations of the Purchaser during the execution of the
work. Purchaser’s employee also shall comply with safety
procedures/policy.
39.4 The Supplier shall report as soon as possible any evidence, which may
indicate or is likely to lead to an abnormal or dangerous situation and
shall take all necessary emergency control steps to avoid such
abnormal situations.
39.5 The Purchaser will be indemnified for all the situations mentioned in
this clause in the similar way as defined in GCC clause 28.
40 Non-Solicitation 40.1 For the purpose of this contract, both parties to this contract agree,not
of Staff to solicit either directly or indirectly with a view to provide or offer
employment to, offer to contract with or entice a staff member of the
other party to leave without the consent of the other during he term
of this agreement and for an additional period of 180 days after
termination.
41 Survival 41.1 The clauses of this contract, which by nature are intended to survive
termination of this contract, shall remain in effect after such
termination.
Section VIII.
Special Conditions of Contract
The following Special Conditions of Contract (SCC) shall supplement the General Conditions of Contract
(GCC). Whenever there is a conflict, the provisions herein shall prevail over those in the GCC.
GCC 6.2 The formal mechanism for the resolution of disputes shall be:
If the parties fail to resolve such a dispute or difference by mutual consultation within
twenty-eight (28) days from the commencement of such dispute and difference, either
party may require that the dispute be referred for resolution to the formal mechanisms,
described below (The date of commencement of the dispute shall be taken from the date
when this clause reference is quoted by either party in a formal communication clearly
mentioning existence of dispute or as mutually agreed) :
a. The mechanism for resolution of disputes for bidders shall be in accordance with
the Indian Arbitration and Conciliation Act of 1996. The Arbitral Tribunal shall
consist of 3 (Three) Arbitrators. Each Party shall nominate an Arbitrator and the
two nominated Arbitrators shall mutually agree and nominate a third Presiding
Arbitrator.
b. The Arbitrators shall necessarily be retired High Court Judges and the umpire shall
be a retired Chief Justice.
GCC 12.2 Details of shipping and documents to be furnished by the Supplier shall be:
(a) Copy of the Supplier’s invoice showing the description of the Goods, quantity, unit
CIF price and total amount;
(e) Copy of test certificate approval and dispatch instructions issued by the purchaser
(combined or separately).
The Purchaser shall receive the above documents at least two weeks before arrival of the
Goods at the port or place of arrival and, if not received, the Supplier will be responsible
for any consequent expenses.
For goods from within the Purchaser’s country as per INCOTERMS EXW basis
including freight and insurance charges:
Upon delivery of the Goods to the transporter, the Supplier shall notify the Purchaser and
send the following documents to the Purchaser;
a) Copy of the Supplier’s invoice showing the description of the Goods, quantity,
unit Ex-works price and total amount;
e) Insurance certificate;
f) Certificate of Origin.
The Purchaser shall receive the above documents before the arrival of the Goods and, if
not received, the Supplier will be responsible for any consequent expenses.
GCC 12.5 The currencies for payments shall be in Indian Rupees (INR).
GCC 13.3 The Supplier shall provide Performance Security of three (03) percent of the total Contract
Price.
The Performance Security shall be in the form of Bank Guarantee issued by a Scheduled
Bank as notified by Reserve Bank of India (RBI). A model format of Performance Bank
Guarantee is provided, utilities to modify the format as per there standard practices.
GCC 21.2 The packing, marking and documentation within and outside the packages if applicable
shall be: As specified (if any) in Technical Specification
GCC 22.1 The insurance coverage: Goods supplied under the contract shall be also fully insured on
all risk basis during inland transit up to destination store in the purchaser’s country. The
supplier must insure the Goods in an amount equal to 110% of CIF/EXW price of Goods.
GCC 27.3 The period of validity of the warranty shall be governed as per provisions of FMS
GCC 27.5 In case of any damage or defect is found during verification after receipt of material at
Purchaser’s stores or material develops defects within warranty period, the supplier shall
attend/replace such defects free of all charges within 30 days of being notified by the
Purchaser, of the occurrence of such defects. In case the defect is not attended or
replacement of material is not received within specified period, then apart from encashing
the performance security deposit, the Purchaser may also take suitable penal action
including debarring from all future business.
Annexure-I
Payment Schedule
10% of total value of contract as (excluding FMS and Bandwidth Charges) “Mobilization Advance”
after signing the contract. The following shall be ascertained before release of payment :-
• Opening of site office in project area
• Submission of necessary Bank Guarantee for the 110% of Initial Advance (Interest
bearing)
• Submission of the necessary Contract Performance Bank Guarantee. The same will
be released on completion of contract/assignment.
• Submission of agreed project implementation schedule
Progressive /Milestone based payment for Each Project Area excluding DR Centre
SCADA /DMS/ OMS system (Control center wise) For Group A&U towns
Software
20 % of software
1.0 Approval of Functional Design document , BOQ , DRS component of contract
20 % of Hardware
1.0Approval of Functional Design document , BOQ , DRS
component of contract
2.0Pro-rata basis on the receipt of equipment at site along with
submission of :
20 % of hardware
B component of contract
a. Detailed Packing list identifying contents of each
consignment (3 copies)
b. Manufacturer’s/contractor’s Guarantee certificate of
Quality
c. Insurance Policy/certificate (3 Copies)
d. Material Inspection Clearance or equivalent Certificate for
dispatch issued by the Utility
e. Test Certificates
3.0 Pro-rata basis on successful completion of end to end testing at 10 % of hardware component
site based on certification by the Utility( Pro rata payment based on of contract
= 0.25( FRTU E TO E tested /TOTAL FRTU) +0.7(RTU E TO E
tested /TOTAL RTU)+ 0.05 (FPI end to end tested/ Total FPI )
After successful completion of Field Performance Tests ( asdefined 25% of hardware component
in MTS) of contract
Installation, Testing and Commissioning Cost to Integrate Entire 40% after successful
SCADA & IT (relevant to SCADA) Infrastructure (Please refer completion of Field
Form:1 Project management cost) Installation Test (as
defined in MTS)
C ( Pro rata payment based on = 0.25( FRTU E TO E tested
/TOTAL FRTU) +0.7(RTU E TO E tested /TOTAL RTU)+ 0.05
35% after successful
(FPI end to end tested/ Total FPI )
completion of end to end
test (as defined in MTS)
Training: Pro-rata payment on the basis of completion of training of 75% of total value of
D required personnel as mentioned in MTS (Please refer Form F-8) Training Cost
75% of receipt of material
Spares and Test Equipment and physical verification of
E material by utility at the
site
15% software, hardware,
installation, testing and
commissioning
Final Payment after Operational Acceptance (on successful +
completion of system availability tests) and Cyber security audit by 100% of payment for
CERT.IN empanelled agency proof of submission of the required Integration with legacy
F number of reproducible, O&M Manuals, approved drawings, data applications & Data
sheets, test reports and manuals etc. of spares, maintenance & testing Migration
equipment , training etc. +
15% payment for training
+
15% of spares and test
equipment
*** Hardware also includes power supply equipment and communication equipment. SECTIONLIZER/
RMU/FPIs /Numerical relays
^ In case bidder does not opt to avail mobilization advance of 10% , the same may be released along with
FAT and Field installation in equal tranches
SCADA system ( Distt Control center wise) (B/C)