|
GRID CODE
-------------------------------
1. INTRODUCTION: 1.1. General:
The Grid Code is a document that governs the boundary between the Licensee and Users and establishes procedures for operations of facilities which will use the Transmission System. It lays down both the information requirements and the procedures governing the relationship between the Licensee and Users. It should be noted that the Grid Code is not concerned with the detailed design and operation of Generators Power Stations and Suppliers Distribution Systems, provided that their overall compatibility with the Transmission System needs is assured. The Transmission and Bulk Supply Licence requires that the Licensee in preparing, implementing and complying with the Grid Code shall neither discriminate against nor unduly prefer any one or any group of Users. The Grid Code shall cover all material technical aspects relating to Connections to and operation and use of the Transmission System including the operation of electric lines and electrical plant connected to the Transmission System in so far as is relevant to the operation and use of the Transmission System. It shall be designed so as to permit the development, maintenance and operation of an efficient, co-ordinated and economical system for the transmission of electricity in the State. 1.2. Scope: 1.3. Interpretation: Section 2 of this code has been developed on the premise that accepted engineering terms do not require additional definitions. The term "Grid Code" means any or all parts of this document. 1.4. Implementation and Operation of the Grid Code: If any User fails to comply with any provision of the Grid Code, it shall inform the Licensee without delay of the reason for its non-compliance and shall remedy its non-compliance promptly. Consistent failure to comply with the Grid Code may lead to Disconnection of the Users plant and/or facilities. The operation of the Grid Code will be reviewed regularly by the Grid Code Review Panel in accordance with the provisions of the relevant Section of the Grid Code. 1.5 General Requirements: Users must therefore understand and accept that the Licensee in such unforeseen circumstances may be required to act decisively to discharge its obligations under its Licence. Users shall provide such reasonable co-operation and assistance as the Licensee may request in such circumstances. 1.6. Code Responsibilities: 1.7. Confidentiality: 1.8. Procedures to settle dispute: In the event of any conflict between any provision of the Grid Code and any contract or agreement between the Licensee and a User, the provision of the Grid Code will prevail. 1.9. Communication between Licensee and Users: Unless otherwise specifically required by the Grid Code, all communications shall be in writing, save that where operation timescales require oral communication, these communications shall be confirmed in writing as soon as practicable. 1.10. Partial Invalidity: 1.11 Directive: 1[1.12
2. DEFINITIONS
|
3. MANAGEMENT OF THE GRID CODE 3.1 Introduction: Subject to the conditions in the next paragraph of this Section, a specific and important feature of the Grid Code is that no revision or modification of the Code, however large or small, may be made without being discussed at the Grid Code Review Panel meeting and approved by the OERC. The OERC may issue directions requiring the Licensee to revise the Grid Code in such a manner as may be specified in those directions and the Licensee shall promptly comply with any such directions. This document defines the procedure to be followed by the Licensee in maintaining the Grid Code and also in pursuing any change. 3.2 Objective: 3.3 Responsibilities: The Licensee shall establish and service the requirements of the Grid Code Review Panel in accordance with provisions of Section 3.4 of the Code. 3.4 Grid Code Review Panel: Each User shall inform the Panel Member Secretary of the name and designation of their Panel Representative not less than 3 days before the first Panel meeting and shall inform the Panel Member Secretary, in writing, of any subsequent change. The Panel shall be chaired by Gridco in its capacity as the transmission Licensee and consist of the following members:
A single representative from each of the following:
The Rules to be followed by the Panel in conducting their business shall be formulated by the Panel themselves and shall be approved by the OERC. The Panel will meet at least once in 5[six] months. The functions of the Panel are as follows:
Sub-meetings may be held by the Licensee with a User to discuss individual requirements and with groups of Users to prepare proposals for the Panel meeting. The Panel may set up sub-committees for detail studies of related problems. 3.5 Grid Code Review and Revisions: The Licensee shall send to the Commission following reports at the conclusion of each review meeting of the Panel.
All revisions to the Grid Code shall require approval of 1[the] Commission. The Licensee shall publish revisions to the Grid Code once approved by the OERC. The Licensee shall present proposals to the OERC to allow relaxation, where Users have difficulties in meeting the Grid Code requirements. The revision number and date of issue shall appear on Every change from the previous version shall be clearly marked in the
margin. In addition, a revision sheet shall be placed at the front of the revised version
that lists the number of every changed sub-Section. 1[-------------]
The Licensee shall keep an up-to-date list of the recipients and locations of all
serviced copies of the Grid Code.
4.1 Introduction: A requirement for reinforcement or extension of the Transmission System may arise for a number of reasons, including but not limited to the following.
Accordingly, the reinforcement or extension of the Transmission System may involve work at an entry or exit point (Connection point) of a Generator or Distribution Company to the Transmission System. Since development of all Users systems must be planned well in advance to permit consents and wayleaves to be obtained and detailed engineering design/construction work to be completed, the Licensee will rquire information from Users and vice versa. To this effect the Planning Code imposes a time scale, for exchange of necessary information between the Licensee and Users having regard, where appropriate, to the confidentiality of such information. 4.2 Objective: 4.3 Perspective Plan: 4.3.2 For fulfilment of the above requirement the Licensee shall:
4.4 Planning Standards and Procedures: The generation expansion planning shall be carried out in accordance with the power supply planning and security standards under condition 20 of the Licence. 4.5 Planning Responsibility: 4.5.2 The Licensee is responsible for integrating the load forecasts submitted by each of the Distribution Companies and determining the long term (10 years) load forecasts for the State 1[within 90 days of the date on which the Distribution Companies furnished all the required information consistent to provisions of this Code]. In doing so the Licensee may apply appropriate diversity factors, and satisfy itself regarding probability of materialisation of bulk loads of consumers with demands above 5 MW in consultation with that Distribution Company concerned. 4.5.3 The Licensee may also review the methodology and assumptions used by the Distribution Company in making the load forecast, in consultation with the Distribution Company. The resulting overall load forecast will form the basis of planing for expansion of generation and the Transmission System. 2[4.5.4 In the event, Distribution Companies failed to provide all the requisite information within the time frame and in accordance with the form provided by the Licensee, the Licensee shall approch to the Commission for a directive.] 4.6 Planning Data Requirement: 4.6.2 To enable Users to co-ordinate planning, design
and operation of their plants and systems with the Transmission System they
may seek certain salient data of Transmission system as applicable to them, which
the Licensee shall supply from time to time as detailed under Data Registration Section and categorised as Detailed
System Data (Transmission).
5.1. Introduction: 5.2. Objective:
5.3 Site Responsibility Schedule:
An illustrative Site Responsibility Schedule is provided at Appendix A. 5.3.1. The Users owning the connection site shall provide reasonable access and other required facilities to another user whose equipment is installed at the connection site for installation, operation and maintenance etc. 5.4 System Performance: Installation of all electrical equipment shall comply with IE Rules. For every new Connection sought, the Licensee shall specify the Connection Point and the voltage to be used, along with the metering and protection requirements as specified in the Metering and Protection Sections. 3[The Transmission System rated frequency shall be 50.00Hz and shall normally be controlled within the limits as per Indian Electricity Rules, 1956 as amended from time to time. The Users shall however be subject to Grid discipline imposed by SLDC as per guidelines mutually agreed in EREB forum.] 4[The variation of voltages on the Transmission System may not be more than the voltage range specified in the Indian Electricity Rules, 1956 as amended form time to time.] Insulation co-ordination of the Users equipment shall conform to applicable Indian Standards/Codes. Rupturing capacity of switchgear shall not be less than that notified by the Licensee from time to time. Protection schemes and Metering schemes shall be as detailed in the Protection & Metering Sections of the Code. For existing Power Stations, the equipment for data transmission and communications shall be owned and maintained by the Licensee, unless alternative arrangements are mutually agreed. For new Power Stations the equipment for data transmission and communications shall be owned and maintained by the respective Generator. 5.5. Connection Point: Voltage may be 400/220/132 kV or as agreed with the Licensee. Unless specifically agreed with the Licensee the Connection point shall be the outgoing feeder gantry of Power Station switchyard. Metering point shall be at the outgoing feeder. All the terminal communication, protection and metering equipment owned by the Generator within the perimeter of the Generators site shall be maintained by the Generator. Other Users equipment shall be maintained by the respective Users. From the outgoing feeder gantry onwards, all electrical equipment shall be maintained by the Licensee. 5.5.2 Distribution Company The Connection point shall be the outgoing feeder gantry of the Licensees sub-station. The metering point shall be at the outgoing feeder. All the terminal, communication, protection and metering equipment within the premises of the Licensee shall be maintained by the Licensee. From the outgoing feeder gantry onwards, all electrical equipment shall be maintained by the respective Distribution Company. 5.5.3 Eastern Regional Transmission System 5.5.4. CPPs & Bulk Power Consumers: Sub-stations are owned by CPPs and Bulk Power Consumers. The Connection point shall be the feeder gantry on their premises. The metering point shall be at the Licensees sub-station or as agreed with the Licensee. 5.6. Data Requirements: 5.7. Procedure for Applications for Connection to and Use of
Transmission:
5.7.2 The Licensee shall normally make a formal offer to the User within 2 months of receipt of the application complete with all information as may reasonably be required, subject to provision in paragraph 5.7.5. 5.7.3 The offer shall specify and take into account any works required for the extension or reinforcement of the Transmission System to satisfy the requirements of the Connection application and for obtaining statutory clearances, wayleaves as necessary. 5.7.4 In respect of offers for modification of existing Connection, the terms shall take into account, the existing Connection Agreement. 5.7.5
5.7.6 All offers (other than preliminary offers) including revised offers shall remain valid for 60 days of issue of offer. 5.7.7 The Licensee shall make a revised offer, upon request by a User, if necessitated by changes in data earlier furnished by the User. 5.7.8 In the event of the offer becoming invalid or not being accepted by any User within the validity period, no further action shall be taken by the Licensee on the Connection applications. 5.7.9 The Licensee may reject any application for Connection to and/or use of Transmission System:
5.8 Connection Agreements:
2[v. general philosophy, guidelines etc. on protection] 5. 9. Appendix: |
|
SITE RESPONSIBILITY SCHEDULE Name of Power Station/Sub-Station Site Owner:
6.1. Introduction: 6.2. Objective: 6.3. Demand Estimation: Distribution Companies and other agencies involved in bilateral exchanges shall provide to the Licensee their estimates of demand / export for Active Power(MW), Reactive Power(MVAr) and Energy Consumption(MU) at each connection / External Interconnection point for the next financial year by 31st December of each year on daily / weekly / monthly basis. The Distribution Companies shall intimate to Licensee the methodology used in producing their forecasts. The Licensee shall use this data
The daily / weekly / monthly data shall be in the form of 24 hourly averaged demand figures for each day / each day of week / each day of month. The demand / export estimates provided by the Distribution Companies and other agencies involved in bilateral exchanges shall be updated as necessary and sent each month to the Licensee 15 days ahead on same daily / weekly / monthly basis. The demand estimates shall be further updated and sent to SLDC in accordance with the provision of Section 7, Scheduling and Despatch. The Licensee shall make its own demand forecast using hourly generation summation figures and CPP import / export figures provided under Section 9 or by using suitable computer program, to compare with demand estimates provided by Users. SLDC shall notify a Contact Person who shall be responsible for day ahead demand forecast. The official and residential telephone numbers of the Contact Person shall be intimated to all the Distribution Companies. Similarly all the Distribution Companies shall notify the Contact Person with telephone numbers and intimate SLDC. In case of change of Contact Person, it should be intimated to SLDC and vice versa. Distribution Companies shall provide to SLDC estimates of load that may be shed, when required, in discrete blocks with the details of the arrangements of such load sheddings. All data shall be collected in accordance with procedures agreed between the Licensee and each User. SLDC shall maintain a database of State demand on an hourly basis. 6.4. Transmission Outage Planning Process: SLDC shall produce a yearly transmission Outage programme for the next financial year. All Generators shall provide SLDC with their proposed Outage programmes in writing for the next financial year by 1st August each year. All Distribution Companies shall provide SLDC with their proposed Outage programmes in writing for the next financial year by 1st August each year. Outage programmes shall contain identification of unit, Outage start date and duration of Outage. SLDC shall produce a draft Outage programme based on the information received from Generators and Distribution Companies, taking into account demand estimation and shall carry out studies as required. SLDC shall inform EREB 6[Secretariat of its proposed Outages in writing by 30th November for each financial year.] 7[EREB secretariat will then come out with a draft outage programme for the next financial year by 31st December of each year for the Regional Grid.] EREB shall inform SLDC of its proposed Outages that would affect the Transmission System by 1st November each year. SLDC shall interact with all Users as necessary to review and optimise the draft plan, agree to any changes and produce an acceptable co-ordinated generation and transmission Outage plan by 1st February each year. SLDC shall release the finally agreed transmission Outage plan, which takes account of Regional and User requirements, to all Users by 1st March each year. SLDC shall review the final Outage plan quarterly in consultation with ERLDC and Users, who shall be informed by SLDC of any proposed changes. Users requests for additional Outages will be considered by SLDC and accommodated to the extent possible. SLDC shall inform Users promptly of any changes that affect them. 6.5. Release of Circuits and Generator Units Included in Outage
Plan: Once an Outage has commenced, if any delay in restoration is apprehended, SLDC or User concerned shall inform the other party promptly together with revised estimation of restoration time. 6.6 Data Requirements:
7.1. Introduction: It further sets down the procedures to be followed by Users so that the Licensee can meet its daily Drawal Schedule whilst ensuring that Reactive Power drawals/ returns are minimised. 7.2. Objective: This Section details the responsibilities of Users to ensure that SLDC can meet its obligations to follow the daily Drawal Schedule. 7.3. Generation Scheduling: All Generators shall provide the hourly MW/MVAr availability (00.00 - 24.00 hours) of all Generating Units, to SLDC on the day ahead basis by 10.00 hours. CPPs 1[.......] shall provide the hourly import/export figures on the day ahead basis by 10.00 hours. In working out the MW/MVAr availability, Hydro Power Stations shall take into account their respective reservoir levels and any other restrictions and shall report the same to SLDC. SLDC shall obtain from ERLDC, capabilities and hourly MW entitlements from ISGS and hourly MW and MWH in the case of Chukha Hydro Power Station, by 11.00 hours on a day ahead basis. SLDC will review it after looking at availability data provided by Generators, export figures from CPPs, the hourly demand estimates from Distribution Companies and any bilateral exchanges. SLDC will advise ERLDC by 15.00 hours of its Drawal Schedule for each ISGS and Chukha Hydro Power Station, in which the Licensee has shares. In preparation of the schedule, SLDC shall take into account of the relative commercial costs to the Licensee of the operation of Generation units. SLDC will receive hourly "net Drawal Schedule" in MW from ERLDC by 17.00 hours for the next day (00.00 hours to 24.00 hours) as summation of the station-wise ex-power plant drawal schedules for all ISGS and Chukha, after deduction of apportioned transmission losses (estimated). SLDC shall intimate the generation schedule/import schedule for the following day to all Generators / CPPs by 18.00 hours. Generators shall promptly report to SLDC, changes of Generating Unit availability or capability, or any unexpected situation which could affect its operation. All CPPs shall similarly report regarding their export to the Licensee. SLDC shall advise Users as soon as possible of any necessary rescheduling. If Generators
or CPPs need to change
availability, SLDC to inform ERLDC
by 22.00 hours. SLDC shall receive final Drawal Schedule from ERLDC by 23.00 hours. SLDC shall prepare the day ahead generation schedule keeping in view the followings:
SLDC shall instruct Generators to hold capacity reserves (spinning and/or standby) to the agreed EREB guidelines or as determined for local conditions. SLDC may also require the Generators/CPPs to generate MVAr within their respective capability limits to hold station bus bar voltages at specified levels. 7.4. Generation Despatch: All Generating Units, above 5 MW, other than those in a CPP, will be subject to central despatch instructions. CPPs will be subject to these instructions as applicable to their respective exports to the Licensee. SLDC will despatch by instruction all generation and imports from CPPs according to the hourly day ahead generation schedule, unless rescheduling is required due to unforeseen circumstances. In absence of any despatch instructions by SLDC, Generators and CPPs shall generate/export according to the day ahead generation schedule. Despatch instructions shall be in standard format. These instructions will recognise declared availability and other parameters which have been made available by the Generator to SLDC. These instructions shall include time, Power Station, Generating Units (total export in the case of CPP), name of operators sending and receiving the same. Despatch instructions may include:
7.5. Communication with Generators: 7.6. Action required by Generators: All Generators and CPPs shall comply promptly with a despatch instruction issued by SLDC unless this action would compromise the safety of plant or personnel. The Generator and CPPs shall promptly inform SLDC in the event of any unforeseen difficulties in carrying out an instruction. All Generating Units shall have Automatic Voltage Regulator (AVR) in service. All Generating Units shall have the governor available and in service and must be capable of automatic increase or decrease in output within the normal declared frequency range and within their respective capability limit. Generators shall immediately inform SLDC by telephone of any loss or change (temporary or otherwise) to the operational capability of any Generating Unit which is synchronised to the system or which is being used to maintain system reserve. Generators shall inform SLDC any removal of AVR and/or governor from service with reasons. CPPs shall similarly inform any change in status affecting their ability in complying with despatch instructions. Generators shall not de-synchronise Generating Units, other than in respect of CPPs, without instruction from SLDC except on the grounds of safety to plant or personnel which shall be promptly reported to SLDC. 1 [Generators and CPPs shall report any abnormal voltage and frequency related operation of Generating Units / feeders promptly to SLDC].Generators shall not synchronise Generating Units, other than in respect of CPPs, without instruction from SLDC. 2[In emergency situations, the Generator may synchronise Units with the grid without prior intimation in the interest of the operation of the grid following standing institutions developed for such purpose under "contingency planning"] Should a Generator fail to comply with any of the above provisions, it shall inform SLDC promptly of this failure. 7.7. Enhancement of Schedule and Dispatch Procedure: 7.8. Data Requirements:
8. FREQUENCY AND VOLTAGE MANAGEMENT 8.1. Introduction: The Licensees System normally operates in synchronism with the Eastern Region grid and ERLDC has the overall responsibility of enforcing grid discipline and managing the frequency in the Region. The constituents of the Region are required to follow the instructions of ERLDC for the backing down generation, regulating load, etc. to meet the objective. SLDC shall accordingly instruct Generating Units and CPPs to regulate generation/export and hold reserves of active and reactive power, within their respective declared parameters. SLDC shall also regulate load and bilateral exchange as may be necessary to meet this objective. Transmission System voltage levels can be affected by Regional operation. High voltages generally occur during high frequency and vice versa, therefore system frequency regulation must be recognised as an important method of voltage control. The Licensee shall optimise voltage management by adjusting transformer taps to the extent available and switching of circuits/reactors and other operational steps. SLDC will instruct Generating Units and CPPs to regulate MVAr generation within their declared parameters. SLDC shall also instruct Distribution Companies to regulate demand if necessary. 8.2. Objective:
8.3. Frequency Management: SLDC shall always endeavour to restrict net drawal to within the Drawal Schedule whenever system frequency is below 49.5 Hz. When frequency falls below 49.0 Hz, SLDC shall explore and utilize internal generation capacity and then requisite load shedding as agreed with Distribution Companies, shall be carried out in the State by SLDC to curtail the over-drawal. 8.4. Responsibilities: SLDC shall monitor actual Drawal against scheduled Drawal and regulate internal generation/demand to maintain this schedule. Generators and CPPs shall follow the despatch instructions issued by SLDC. Distribution Companies shall co-operate with SLDC in managing load on instruction from SLDC as required. 8.4.1. Falling frequency |