Full Grid Code - NTDC Draft

The Pakistan Grid Code
February/March 2021
Introduction 1
INTRODUCTION
Pursuant to Section 35 of NEPRA Act and Article 16 of the NTDC licence, based on Article 23G the
National Transmission and Dispatch Company as System Operator is required, among other duties, to
ensure that there is in force at all times a Grid Code updating for the needs of its functions stated in
Article 18. It states “The national grid company shall be responsible to operate and provide safe, reliable
transmission and inter-connection services on a non-discriminatory basis, including to a bulk-power
consumer who proposes to become directly connected to its facilities.
Consequently, NTDC is required to submit a comprehensive Grid Code for approval of the Authority in
accordance with the requirement of Article 16, 18 and 23G of NEPRA Act. The Grid Code provides for
the smooth and effective functioning of NTDC and other NEPRA licensees that are or will be connected to
the NTDC's Bulk Transmission System.
The Grid Code is an essential requirement of the regulation of electric network supply and delivery system.
In accordance with 'Regulation of Generation, Transmission and Distribution of Electric Power Act (XL of
1997)', all existing and future Users of the electric network supply and delivery system need a relevant
Licence from NEPRA; and register as Code Participants with NTDC as per the provisions of Grid Code. One
of the NTDC Licence's requirements is that Users of the NTDC's system must comply with the provisions of
Grid Code at all times. Failure to do so may result in their licence being suspended or revoked.
The Grid Code sets out the guidelines. rules and procedures to be adopted by all Code Users. The sub-
codes of the Grid Code relate to technical and commercial relationships between NTDC and its Users.
The purpose of Grid Code is to provide unambiguous guidelines, rules and procedures, which ensure that
all Users of Grid Code understand and abide by the obligations and responsibilities placed upon them
under this Grid Code. The Code covers day-to-day and long-term principles. standards, procedures and
guidelines for Planning, Operation, Dispatch, and Connection purposes for normal and abnormal NTDC
transmission system conditions.
The Grid Code sets out the operating procedures and principles between the National Transmission and
Dispatch Company; and all authorised Electricity Operators as defined in NTDC transmission licence
collectively referred to as "Users" in the context of this document.
The Grid Code is structured so as to ensure that the NTDC’s transmission system can be developed,
operated, and maintained in an efficient, safe. reliable and co ordinated manner from technical and
commercial aspects both. The Grid Code is expected to encourage competition between Generators,
Distribution Companies, and BPCs (Bulk Power Consumers) as the Market Structure develops.
It seeks to avoid any undue discrimination between various Users themselves; between the entities within
a particular User Group type; and in day-to-day working relationship of NTDC with its Users.
In implementing and complying with the Grid Code, neither the NTDC nor its affiliates shall unduly
discriminate in any manner between any purchasers, procurers, providers or recipients of electric power or
ancillary service providing similar services.
Introduction 2
Main Objectives of the Grid Code are:
a) To achieve the Performance Standards (Transmission) to be prescribed under the Act;
b) To facilitate the development, operation, and maintenance of an efficient, co-ordinated, safe,

reliable and economical system for the transmission of electric power;
c) To facilitate competition in the provision of electric power; and
d) To cover all material technical aspects relating to Connection, the Operation and Use of the
NTDC's transmission system including the operation of electric lines and electric plants
connected to the NTDC's transmission system in so far as relevant to the Operation and Use
of NTDC's transmission system.
This Grid Code includes the following sub-codes:
a. Code Management
Code Management, which sets out procedures to be adopted by all parties in the NTDC
process of administering, updating, and amending of the Grid Code.
b. Planning Code
The Planning Code, which deals with Principles, Standards, Processes, and Procedures along
with data information exchange requirements between parties to ensure an efficient,
economic, and timely development of the NTDC bulk transmission system to meet the
forecasted Total System Demand and Margin of Operating Reserve requirements. It also
describes in detail the data needs which the Users must fulfill in a timely manner to meet the
planning responsibilities of NTDC in an effective manner.
c. Connection Code
A Connection Code, which sets out the principles and procedures to be applied to new
connections to the NTDC bulk transmission system. New connections may include new or
existing Generators; Distribution Companies, Consumers requiring a direct connection to the
NTDC transmission system known as transmission-connected Consumers; and Externally-
connected Parties, and Externally-connected Consumers.
d. Data Registration Code
Data Registration Code, which sets out a unified listing of all data required by NTDC from
Users; and by Users from NTDC, from time to time under the Grid Code.
e. Operation Code
The Operation Code, which sets out the principles, standards, procedures, and guidelines to
be followed by NTDC and its Users to ensure safe and an efficient operation of the NTDC
transmission system, for real-time, and for short-term planning of system operations, and for
normal and abnormal circumstances.
f. Protection and Metering Code
The Protection and Metering Code, which places the Protection and Metering requirements
upon the Users and NTDC (particularly with reference to the Inter-connection Sites) in terms
of Principles, Standards, Design, and Procedures to ensure safe, reliable and effective
functioning of NTDC's bulk transmission system.
g. Scheduling and Dispatch Code
A Scheduling and Dispatch Code, which sets Out Principles, Processes and Procedures to
ensure minimum-cost generation dispatch, the relationship between NTDC and Generators,
including the dispatch process and requirements for ancillary services and 'provisions for
Introduction 3
frequency control. It also places an obligation upon Users to supply certain data information
to the NTDC in a timely manner.
h. Code Glossary & Definitions
The Code Definitions, which provides an explanation of the terms used in this Grid Code.
The relationship aong Codes, the Grid Code, the Distribution Code, Other Codes and the Commercial
Code, is shown on Figure 1 .
The Grid Code specifies all the material, technical design, and operational aspects of the interface
requirements between NTDC, Distribution Licensees, BPCs, Externally-connected Parties and
Consumers, Provincial and Special Purpose Transmission Licensees (SPTLs).
The Distribution Code shall be consistent in material particulars with the Grid Code; and it shall
ensure strict compliance by the distribution companies and other Users with the provisions of
Grid Code including, without limitation, the instructions from time to time of NTDC and/or the System
Operator in respect of the Use and Operation of their distribution systems.
Other Codes may influence or need to be taken into account from Grid Code, these are code which
regulates entities which are external to NTDC battery limits.
The Interconnectors are regulated by a Technical Code.. This need to be taken into consideration in
the Grid Code in terms minimum technical requirements and obligations, which may depend on the
Interconnector technology itself.
The institution of the CTCBM bi-lateral Market determine a Commercial Code to be set up among
Pakistan Energy Market stakeholders, and the Market Design interacts with parts of the Grid Code
sections, i.e. the Scheduling & Dispatching and The Demand Forecast.
Finally, via Interconnectors Technical Code and contractual Agreements between interconnected
parties, Grid Codes of other jurisdictions shall be accounted for, in order to consider possible system
limitations of other stakeholders and manage interconnectors without put external parties at risk.
Introduction 4
Commercial Code/ Other Grid Codes
External
Technical I nterconnected
Parties
Code 1
Technical
Code k
Technical
Code 1
Figure 1. Relationship between the Grid Code, the Distribution Code and Other Codes
Technical Grid Code Transmission Connected Customers

Codes/ Other
Codes Provincial Companies Provincial
& SPTLs
Special Purpose Transmission
Companies
System Generators Connected to
Operator Transmission I nterc.
Operators
I nterconnectors
Generator Aggregators
Demand
Demand Customers Side
Operators
Load Demand Side Units
Dispatch
Centre Distribution Companies
DI SCOs
Embedded Generators
Dist. Code Small Scale Power producers
Figure 2. Stakeholders and the Codes
Introduction 5
CODE MANAGEMENT
CONTENTS
CM 1 INTRODUCTION & SCOPE.................................................................................. 2
CM 2 UNFORESEEN CIRCUMSTANCES......................................................................... 2
CM 3 THE GRID CODE REVIEW PANEL......................................................................... 3
CM 4 COMMUNICATIONS BETWEEN NTDC AND USERS.............Error! Bookmark not defined.
CM 5 MISCELLANEOUS.......................................................... Error! Bookmark not defined.
CM 6 OWNERSHIP OF FACILITIES, PLANT AND/OR APPARATUS Error! Bookmark not defined.
CM 7 SYSTEM CONTROL........................................................ Error! Bookmark not defined.
CM 8 FORCE MAJEURE.......................................................... Error! Bookmark not defined.
CM 9 MATTERS TO BE AGREED.................................................................................. 6
CM 10 INFORMATION DISSEMINATION....................................................................... 21
CM 11 INDEMNITY TO THE NTDC............................................. Error! Bookmark not defined.
CM 12 PRESERVATION OF CONTRACTS PRIOR TO ENACTMENT OF NEPRA ACT..........Error!

Bookmark not defined.
CM 13 CODE ADMINISTRATION............................................... Error! Bookmark not defined.
CM 14 NON-COMPLIANCE....................................................... Error! Bookmark not defined.
CM i
CODE MANAGEMENT
CM 1 INTRODUCTION & SCOPE

CM 1.1 While each individual section of the Grid Code contains the rules and provisions relating
specifically to that section of the Grid Code the Code Management section contains
provisions of general application to all provisions of the grid code. Their objective is
to ensure that the various sections of the grid code work in conjunction with each
other for the benefit of all users. This code management section applies to all users
including NTDC.
CM 2 OBJECTIVE
CM 2.1 The objectives of the General Conditions are as follows:
(a) to ensure, insofar as it is possible, that the various sections of the Grid Code work
together, and work in practice, for the benefit of the operation of the Power
System and for the benefit of the SO and Users;
(b) to provide a set of principles governing the status and development of the Grid
Code and related issues, as approved by the NEPRA;
(c) to provide an outline of how the SO, the Other SO and the Regulatory
Authorities will cooperate with regard to Grid Code revisions and derogations to
both Sections Under Common Governance and other Grid Code sections which
may be considered to be relevant to the operation of the CTBCM.
CM 3 SCOPE
The Code Management apply to the SO, the NEPRA, and to all Users
(which expression in these Code Management means all persons (other
than the SO) to whom any individual section of the Grid Code applies).For
avoidance of doubt, in addition to NTDC, Users are the followings:
a) All Generators connected at the Transmission system
b) Generators with capacity greater than 10 MW;
c) DISCOs;
d) Transmission-connected Consumers; and
e) Externally Connected Consumers/Parties, like
1. Special Licensee Transmission Company
2. Provincial Companies
3. Interconnector Operators
4. Aggregators
5. Independent Power Producers (IPP)
6. Demand Customers
CM 2
CM 4 PURPOSE
CM 4.1 This Grid Code is designed to cover all material technical aspects relating to the
operation and use of the Transmission System, and (insofar as relevant to the planning,
operation and use of the Transmission System) all material technical aspects relating to
the use of Plant and or Apparatus connected to the Transmission System or to the
Distribution, Provincial and SPTLs Systems.
CM 5 THE GRID CODE REVIEW PANEL

CM 5.1 NTDC shall establish and maintain the Review Panel, which shall be a standing body and
shall undertake the functions detailed in CM 5.3.
CM 5.2 The Panel shall consist of:
(a) a Chairman and up to 3 Members appointed by NTDC;
(b) a person appointed by the Authority;
(c) the following Members;
i. 2 Persons representing Generators/Generator Aggregators with a total

registered capacity in excess of 1000 MW;
ii. 3 Persons representing Generators/Generator Aggregators with a total

registered capacity of less than 1000 MW but greater than 500 MW;
iii. 4 Persons representing Generators/Generators Aggregators with a total

registered capacity of less than 500 MW but greater than 10 MW;
iv. Max 4 Persons representing Demand Side Aggregators wit a total

registered capacity less than 500 MW but greater than 10 MW.
v. one representative from each Distribution Company Licensed with

NEPRA;
vi. one representative from each Provincial Company Licensed with NEPRA;
vii. a one representative from each Special Purpose Transmission Company

Licensed with NEPRA;
viii. a Person representing Transmission-connected consumers;
ix. a Person representing Small Power Producers (SPP);
x. a Person representing Externally-connected Consumers
xi. one representative from Externally-connected Parties and
xii. one Member from the Industry or an Academic Institution or PEC.
The representation within each category shall be based on rotation and mutual
agreement.
CM 5.3 The panel shall:
(a) keep the Grid Code and its workings under review;
(b) review all suggestions for amendments to the Grid Code which the Authority
or any User may wish to submit to NTDC for consideration by the Panel;
(c) publish recommendations as to amendments to the Grid Code that NTDC or

the Panel believes are desirable and the reasons for such recommendations;
(d) submit all the agreed recommendations to NEPRA for approval;

CM 3
(e) issue guidance on the Grid Code and its implementation, performance and
interpretation, when asked to do so by any User;
(f) resolve any matters of dispute between NTDC and its Users/Code Participants;
(g) study and evaluate the suggestions received from different parts of the power
market participant; and
(h) consider the modification which are necessary to the Grid Code arising out of
any unforeseen circumstances and Force Majeure referred to it by NTDC
under CM 2 & CN 8 of this sub-code.
CM 5.4 The Panel shall establish and comply with at all times with its own rules and
procedures relating to the "Conduct of its Business", which shall be approved by the
Authority.
CM 5.5 NTDC shall consult in writing all Users which are liable to be affected by any
proposed amendments to the Grid Code and shall submit all such proposed
amendments to the Grid Code to the Panel for discussion prior to such consultation.
CM 6 JOINT GRID CODE REVIEW PANEL
CM 6.1 SO shall, in conjunction with the Other SOs, establish and maintain the Joint Grid Code
Review Panel. This Joint panel comprises all members of the Grid Code Review Panel and
nominated representatives of Other Grid Code Review Panels and it has the following functions:
(a) generally review and discuss the Sections Under Common Governance
and their workings;
(b) review and discuss suggestions for amendments to the Sections Under
Common Governance of the Grid Code, which the SO, either
Regulatory Authority, or any User may wish to submit to the SO for
consideration by the Joint Grid Code Review Panel from time to time;
(c) discuss what changes are necessary to the Sections Under
Common Governance of the Grid Code arising out of any
unforeseen circumstances referred to it by the SO under GC.12 .
CM 4
CM 6.2 The SO shall publish recommendations and ensure that User consultation upon such
recommendations has occurred
CM 6.3 The Joint Grid Code Review Panel shall be governed by its own constitution, which defines its
scope, membership, duties, and rules of conduct and operation as approved by all Regulatory
Authorities.
CM 7 GRID CODE REVISIONS
CM 7.1 All revisions to the Grid Code must be reviewed by the Grid Code Review Panel or the
Joint Grid Code Review Panel (where relevant) prior to application to the NEPRA by the SO.
Where the SO identifies or receives a proposed revision that affects a Section Under Common
Governance, it shall bring it to the attention of the Other SO. All proposed revisions from Users,
the NEPRA, or the SO will be brought before the Grid Code Review Panel or the Joint Grid
Code Review Panel (where relevant) by the SO for consideration. In the event that the SO,
acting reasonably, considers that proposed revisions are frivolous or repeated, the SO may propose
to the Grid Code Review Panel or the Joint Grid Code Review Panel (where relevant) that these
proposed revisions are not to be considered. However, in the event that any member of the Grid
Code Review Panel or the Joint Grid Code Review Panel (where relevant) decides that the revision is
worthwhile, it shall be reviewed. The SO shall then inform the proposer of the decision, with an
accompanying explanation if required. If the proposing User is not satisfied with the response from
the SO, they can bring it to the attention of the NEPRA.
CM 7.2 The SO will advise the Grid Code Review Panel or the Joint Grid Code Review Panel (where
relevant), all Users, and the NEPRA of all proposed revisions to the Grid Code with notice of no less
than xx days in advance of the next scheduled meeting of the Grid Code Review Panel or the Joint
Grid Code Review Panel (where relevant).
CM 7.3 Following review of a proposed revision by the Grid Code Review Panel or the Joint Grid Code
Review Panel (where relevant), the SO will apply to the NEPRA for revision of the Grid Code based
on the SO recommendation and shall make representation of all other views or considerations
including those of the Grid Code Review Panel or the Joint Grid Code Review Panel (where relevant).
The SO, in applying to the NEPRA, shall also notify each User of the proposed revision and other
views expressed by the Grid Code Review Panel or the Joint Grid Code Review Panel (where
relevant) and Users so that each User may consider making representations directly to the NEPRA
regarding the proposed revision.
CM 7.4 The NEPRA shall consider the proposed revision, other views, and any further representations
and shall determine whether the proposed revision should be made and, if so, whether in the form
proposed or in an amended form. Where amendments to the revision are contemplated by the
NEPRA, the NEPRA shall consult the Grid Code Review Panel or the Joint Grid Code Review Panel
(where relevant), the SO, and Users as appropriate. Determination on a modification to a Section
Under Common Governance shall be made by the NEPRA in accordance with its procedure that is
in place to approve modifications to Sections Under Common Governance.
CM 7.5 Having been so directed by the NEPRA that the applied for revision or amended revision shall
be made, the SO shall notify each User of the revision at least xx Business Days prior to the revision
taking effect, and the revision shall take effect (and this Grid Code shall be deemed to be amended
accordingly) from (and including) the date specified in such notification or other such date as
directed by the NEPRA. The date may be modified to ensure that the revision is implemented
simultaneously in both jurisdictions on the Republic of Pakistan.
CM 5
CM 8 MATTERS TO BE AGREED
CM 8.1 Grid Code Interpretation
CM 8.1.1 In the event that any User requires additional interpretation of the intention and application of
any provision of the Grid Code, it may apply to the SO for such interpretation. Provided that the
request is reasonable, the SO shall provide the User with an interpretation of the relevant
provision. If the request refers to a Section Under Common Governance then the SO shall liaise
with the Other SO prior to the provision of the interpretation to the User.
CM 8.1.2 In the event that the User, acting reasonably, considers that an interpretation provided by the
SO pursuant to GC.8.1 is incomplete, the User may request additional clarification from the SO.
CM 8.1.3 In the event that the User, acting reasonably, considers that an interpretation provided by the
SO pursuant to GC.8.1 is unreasonable or incorrect, the User may require the SO to refer the
matter for consideration, at the next scheduled meeting of the Grid Code Review Panel or the Joint
Grid Code Review Panel (where relevant) (or in the event that there is insufficient time before the
next scheduled meeting, then at the meeting immediately following the next scheduled meeting).
CM 8.2 DEROGATIONS (NEPRA to elaborate adequate forms, see examples XXX1,,2,3 and 4)
CM 8.2.1 If a User finds that it is, or will be, unable to comply with any provision of the Grid Code, then
it shall without delay report such non-compliance to the SO and shall, subject to the provisions of
GC.9.2.1 make such reasonable efforts as are required to remedy such non-compliance as soon as
reasonably practicable. Where the SO is aware or should reasonably be aware that a non-
compliance may have an impact on the Other Transmission System or on the operation of the
CTBCM, the SO shall provide details of the non-compliance to the Other SO.
CM 8.2.2 Where the non-compliance is:
(a) with reference to Plant and/or Apparatus connected to the Transmission

System and is caused solely or mainly as a result of a revision to the Grid
Code; or
(b) with reference to Plant and/or Apparatus which is connected, approved to
connect, or for which approval to connect to the Transmission System is
being sought, and the User believes either that it would be unreasonable
(including cost and technical considerations) to require it to remedy such non-
compliance or that it should be granted an extended period to remedy such
non-compliance, it shall promptly submit to the SO a request for a derogation
from such provision in accordance with the requirements of CM 16.2.3 and
shall provide the NEPRA with a copy of such a request. In consideration of a
derogation request by a User, the SO may contact the relevant User to
obtain clarification of the derogation request, or to obtain further information
regarding the request, or to discuss changes to the request. Once the
derogation request has been validated by the SO, the reference number is
assigned
(c) Where the derogation request may have an impact on the Other
Transmission System or the operation of the CTBCM, the SO shall liaise
with the Other SOs prior to providing an assessment to the NEPRA.
(d) The SO will assess the derogation request and provide to the NEPRA an
assessment and a recommendation.
(e) On receipt of a derogation assessment from the SO, the NEPRA will consider
the derogation request, the SO’s assessment and the SO’s recommendation.
CM 6
(f) In its consideration of a derogation request by a User, the NEPRA may
contact the relevant User and/or the SO to obtain clarification of the request,
or to obtain further information regarding the request, or to discuss changes to
the request.
(g) Where the NEPRA identifies that a derogation request may impact on the
Other Transmission System or the operation of the CTBCM, the NEPRA
shall keep the Regulatory Authorities inof Other SOs’ jurisdictions informed
in its consideration of the request.
(h) Provided that the NEPRA considers that the grounds for the derogation are
reasonable, then the NEPRA shall grant such derogation unless the
derogation would, or it is likely that it would, have a materially adverse impact
on the security and stability of the Transmission System or the Other
Transmission Systems or impose unreasonable costs on the operation of
the Transmission System or on other Users.
CM 8.2.3 A request for derogation from any provision of the Grid Code shall contain:
(a) the version number of the Grid Code;

(b) identification of the Plant and/or Apparatus in respect of which a derogation is
sought;
(c) identification of the provision with which the User is, or will be, unable to
comply;
(d) the extent of the non-compliance;
(e) the reason for the non-compliance; and
(f) the date by which compliance will be achieved (if remedy of the non-
compliance is possible) subject to GC.XXX.
CM 8.2.4 If the SO finds that it is, or will be, unable to comply with any provision of the Grid Code, then
it shall, subject to the remaining provisions of GC.9.1 make such reasonable efforts as are
required to remedy such non-compliance as soon as reasonably practicable.
CM 8.2.5 In the case where the SO requests a derogation, the SO shall submit the information set out in
GC.XXX to the NEPRA.
CM 8.2.6 To the extent of any derogation granted in accordance with this GC.9.1, the SO and/or the
User (as the case may be) shall be relieved from its obligation to comply with the applicable
provision of the Grid Code and shall not be liable for failure to so comply but shall comply with any
alternate provisions as set forth in the derogation.
CM 8.2.7 The SO shall:
(a) keep a register of all derogations which have been granted, identifying
the company and Plant in respect of whom the derogation has been
granted, the relevant provision of the Grid Code and the Grid Code
version number, the period of the derogation and the extent of
compliance to the provision;
(b) on request from any User or User of the Other Grid Code, provide
a copy of such register of derogations to such User; and
(c) publish this register on the SO’s website.
CM 7
CM 8.2.8 Where a material change in circumstance has occurred a review of any existing derogations,
and any derogations under consideration, may be initiated by the NEPRA at the request of the
NEPRA, the SO, or Users.
CM 8.3 Generating Unit Derogation Procedure
CM 8.3.1 Power to Grant Derogations

NEPRA may, at the request of a Generator, or the SO, grant a Generator or
the SO derogations from one or more Generating Unit clauses in the Grid
Code for Generating Units in accordance with GC.9.3.2, GC.9.3.3 and
GC.9.3.4. Derogations may be granted and revoked in accordance with GC.9.3.2,
GC.9.3.3 and GC.9.3.4 by other authorities than the NEPRA.
CM 8.3.2 General Provisions
8.3.2.1 The criteria specified by NEPRA to assess derogations pursuant to GC.9.3.3 and GC.9.3.4 are
specified in form xxxx1 and xxxx2 respectively.
8.3.2.2 If NEPRA deems that it is necessary due to a change in circumstances relating to the evolution of
system requirements, it may review and amend at most once every year the criteria for granting
derogations as referenced in GC.9.3.2.1. Any changes to the criteria shall not apply to
derogations for which a request has already been made.
CM 8.3.3 Request for a Derogation by a Generator
8.3.3.1 Generators and Generator Aggregators may request a derogation to one or several Generating
Units clauses in the Grid Code for Generating Units within their Facility.
8.3.3.2 A request for a derogation shall be filed with the SO using form XXX1 and include:
(a) an identification of the Generator, Generator Aggregator, and a

contact person for any communications;
(b) a description of the Generating Unit(s) for which a derogation is

requested;
(c) a reference to the Generating Unit(s) clauses in the Grid Code from
which a derogation is requested and a detailed description of the
requested derogation;
(d) detailed reasoning, with relevant supporting documents and cost-

benefit analysis;
(e) demonstration that the requested derogation would have no

adverse effect on cross-border trade.
CM 8
8.3.3.3 Within xxxx of receipt of a request for a derogation, the SO shall confirm to the Generator
whether the request is complete. If the SO considers that the request is incomplete Generator,
Generator Aggregator shall submit the additional required information within one month from
the receipt of the request for additional information. If the Generator, Generator Aggregator
does not supply the requested information within that time limit, the request for derogation shall
be deemed withdrawn.
8.3.3.4 The SO shall assess the request for derogation and the provided cost-benefit analysis, taking
into account the criteria determined by the NEPRA pursuant to GC.9.3.2.
8.3.3.5 Within XXXXX of receipt of a request for derogation, the SO shall forward the request to the
NEPRA and submit the assessment(s) prepared in accordance with GC.9.3.3.4. That period may
be extended by one month where the SO seeks further information from the Generator.
8.3.3.6 The NEPRA shall adopt a decision concerning any request for derogation within xxxxxx from the
day after it receives the request. That time limit may be extended by xxxxx before its expiry
where the CRU requires further information from the Generator, Generator Aggregator, or
from any other interested parties. The additional period shall begin when the complete
information has been received.
8.3.3.7 The Generator, Generator Aggregator shall submit any additional information requested by
the NEPRA within two months of such a request. If the Generator, Generator Aggregator
does not supply the requested information within that time limit, the request for derogation shall
be deemed withdrawn unless, before its expiry:
(a) the NEPRA decides to provide an extension; or
(b) the Generator, Generator Aggregator informs the NEPRA by means

of a reasoned submission that the request for a derogation is
complete.
8.3.3.8 The NEPRA shall issue a reasoned decision concerning a request for derogation. Where the
NEPRA grants a derogation, it shall specify its duration.
8.3.3.9 The NEPRA shall notify its decision to the relevant Generator, Generator Aggregator and
the SO.
8.3.3.10 The NEPRA may revoke a decision granting a derogation if the circumstances and underlying
reasons no longer apply.
CM 8.3.4 Request for a Derogation by the SO
8.3.4.1 The SO may request derogations for classes of Generating Units connected or to be connected
to their Network.
8.3.4.2 he SO shall submit their requests for derogations, using form XXX2, to the NEPRA. Each request
for a derogation shall include:
(a) identification of the SO, and a contact person for any

communications;
(b) a description of the Generating Units for which a derogation is

requested and the total installed capacity and number of Generating
Units;
(c) the Generating Unit clauses in the Grid Code for which a derogation
is requested, with a detailed description of the requested
CM 9
derogation;
(d) detailed reasoning, with all relevant supporting documents;

adverse effect on cross-border trade;
(f) a cost-benefit analysis.
8.3.4.3 The NEPRA shall adopt a decision concerning a request for derogation within xxxx from the day
after it receives the request.
8.3.4.4 The xxxxx time limit referred to in GC.9.3.4.3 may, before its expiry, be extended by an
additional xxxx where the NEPRA requests further information from the SO requesting the
derogation or from any other interested parties. That additional period shall run from the day
following the date of receipt of the complete information.
The SO shall provide any additional information requested by the NEPRA within xxxxx from the date
of the request. If the SO does not provide the requested additional information within that time limit,
the request for derogation shall be deemed withdrawn unless, before expiry of the time limit:
(b) the SO informs the NEPRA by means of a reasoned submission that

the request for derogation is complete.
8.3.4.6 The NEPRA shall notify its decision to the SO.
8.3.4.7 The NEPRA may lay down further requirements concerning the preparation of requests for
derogation by the SO, Other SOs and Regulators. In doing so, the NEPRA shall take into
account the delineation between the transmission system and the distribution, provincial and
SPTLs systems at the national level and shall consult with system operators, Generators,
Generators Aggregators, Interconnector Operators, Demand Customers, Demand Side
Operators and stakeholders, including manufacturers.
CM 8.3.5 Register of Derogations
8.3.5.1 The NEPRA shall maintain a register of all derogations they have granted or refused
8.3.5.2 The register shall contain, in particular:
(a) the requirement or requirements for which the derogation is granted

or refused;
(b) the content of the derogation;
(c) the reasons for granting or refusing the derogation;
(d) the consequences resulting from granting the derogation.
CM 10
CM 8.4 Demand Consumers, Demand Side Units, Discos, Provincial & SPTLs
Companies Derogation Procedure
CM 8.4.1 Power to Grant Derogations
NEPRA may, at the request of a Demand Facility Owner, Demand Side Units, Distribution, Provincial &
SPTLs System Operator, or the SO, grant a Demand Facility, , Distribution, Provincial & SPTLs or the
SO, derogations from one or more Demand Facility Units Demand Side Units, clauses in the Grid Code
in accordance with GC.9.4.2, GC.9.4.3 and GC.9.4.4. Derogations may be granted and revoked in
accordance with GC.9.4.2, GC.9.4.3 and GC.9.4.4 by other authorities than the NEPRA. GC.9.4.2
CM 8.4.2 General Provision
8.4.2.1 The criteria specified by NEPRA to assess derogations pursuant to GC.9.4.3 and GC.9.4.4 are
specified in form XXXX1, XXXX2 and XXXX3 respectively.
8.4.2.2 If NEPRA deems that it is necessary due to a change in circumstances relating to the evolution of
system requirements, it may review and amend at most once every year the criteria for granting
derogations as referenced in GC.9.4.2.1. Any changes to the criteria shall not apply to
derogations for which a request has already been made.
8.4.2.3 The NEPRA may decide that Demand Facilities, Demand Side Units, Distribution, Provincial &
SPTLs, for which a request for a derogation has been filed pursuant to GC.9.4.3 or GC.9.4.4 do
not need to comply with clauses in the Grid Code from which a derogation has been sought from
the day of filing the request until the NEPRA's decision is issued.
CM 8.4.3 Request for a Derogation by a Demand Facility Owner, Demand Side Units, Distribution,
Provincial & SPTLs Companies
CM 8.4.4 Demand Facility Owners, Demand Side Operators, Distribution, Provincial & SPTLs Systems
Operators may request a derogation to one or several DCC Unit clauses in the Grid Code for
Demand Facility, or Distribution, Provincial & SPTLs System.
CM 8.4.5 A request for a derogation shall be filed with the SO using form XXX1 or XXX2 and include:
(a) an identification of the Demand Facility Owner, or Demand Side

Operators, Distribution, Provincial & SPTLs Systems Operators and a
contact person for any communications;
(b) a description of the Demand Facility, Demand Side Unit, Distribution,

Provincial & SPTLs Systems Operators System for which a derogation is
requested;
(c) a reference to the Unit clauses in the Grid Code from which a derogation is
requested and a detailed description of the requested derogation;
(d) detailed reasoning, with relevant supporting documents and cost-benefit

analysis;
(e) demonstration that the requested derogation would have no adverse

effect on cross-border trade.
CM 11
8.4.5.1 Within xxxxx of receipt of a request for a derogation, the SO shall confirm to the Demand Facility
Owner, or Demand Side Operators, Distribution, Provincial & SPTLs Systems Operators whether
the request is complete. If the SO considers that the request is incomplete, the Demand Facility
Owner, or Demand Side Operators, Distribution, Provincial & SPTLs Systems Operators shall
submit the additional required information within one month from the receipt of the request for
additional information. If the Demand Facility Owner, Demand Side Operators, Distribution,
Provincial & SPTLs Systems Operators, does not supply the requested information within that
time limit, the request for derogation shall be deemed withdrawn.
8.4.5.2 The SO shall assess the request for derogation and the provided cost-benefit analysis, taking
into account the criteria determined by the NEPRA pursuant to GC.9.4.2
8.4.5.3 Within xxxxx of receipt of a request for derogation, the SO shall forward the request to the
NEPRA and submit the assessment(s) prepared in accordance with GC.9.4.3.4. That period may
be extended by xxxxx where the SO seeks further information from the Demand Facility Owner,
Demand Side Operators, Distribution, Provincial & SPTLs Systems Operators.
8.4.5.4 The NEPRA shall adopt a decision concerning any request for derogation within six months from
the day after it receives the request. That time limit may be extended by three months before its
expiry where the NEPRA requires further information from the Demand Facility Owner, Demand
Side Operators, Distribution, Provincial & SPTLs Systems Operators, or from any other
interested parties. The additional period shall begin when the complete information has been
received.
8.4.5.5 The Demand Facility Owner, Demand Side Operators, Distribution, Provincial & SPTLs
Systems Operators shall submit any additional information requested by the NEPRA within
xxxxx of such a request. If the Demand Facility Owner, Demand Side Operators,
Distribution, Provincial & SPTLs Systems Operators does not supply the requested
information within that time limit, the request for derogation shall be deemed withdrawn unless,
before its expiry:
(b) the Demand Facility Owner, Demand Side Operators, Distribution,

Provincial & SPTLs Systems Operators informs the NEPRA by means
of a reasoned submission that the request for a derogation is
complete.
8.4.5.6 The NEPRA shall issue a reasoned decision concerning a request for
derogation. Where the NEPRA grants a derogation, it shall specify its
duration.
8.4.5.7 The NEPRA shall notify its decision to the relevant Demand Facility
Owner, Demand Side Operators, Distribution, Provincial & SPTLs
Systems Operators and the SO, Other SOs and Regulators.
8.4.5.8 The NEPRA may revoke a decision granting a derogation if the

circumstances and underlying reasons no longer apply.
8.4.5.9 Request for a Derogation by the SO.
8.4.5.10 The SO may request derogations for classes of Demand Facilities,

Demand Side Operators, Distribution, Provincial & SPTLs Systems
Operators connected or to be connected to their Network.
CM 12
8.4.5.11 The SO shall submit their requests for derogations, using form XXXXX3, to the NEPRA. Each
request for a derogation shall include:
(a) identification of the SO, and a contact person for any

communications;
(b) a description of the Demand Facilities, Demand Side Operators,

Distribution, Provincial & SPTLs Systems for which a derogation is
requested and the total installed capacity and number of Demand
Facilities, Demand Side Operators, Distribution, Provincial & SPTLs
Systems;
(c) the Unit clauses in the Grid Code for which a derogation is
requested, with a detailed description of the requested derogation;
(d) detailed reasoning, with all relevant supporting documents;

adverse effect on cross-border trade;
(f) a cost-benefit analysis.
8.4.5.12 NEPRA shall adopt a decision concerning a request for derogation within six months from the
day after it receives the request.
8.4.5.13 The xxxxx time limit referred to in GC.9.4.4.3 may, before its expiry, be extended by an
additional xxxxx where the NEPRA requests further information from the SO requesting the
derogation or from any other interested parties. That additional period shall run from the day
following the date of receipt of the complete information.
8.4.5.14 The SO shall provide any additional information requested by the NEPRA within xxxx from the
date of the request. If the SO does not provide the requested additional information within that
time limit, the request for derogation shall be deemed withdrawn unless, before expiry of the
time limit:
(b) the SO informs the NEPRA by means of a reasoned submission that

the request for derogation is complete.
CM 13
8.4.5.16 The NEPRA shall notify its decision to the SO, Other SOs and Regulators.
8.4.5.17 The NEPRA may lay down further requirements concerning the preparation of requests for
derogation by the SO. In doing so, the NEPRA shall take into account the delineation between
the transmission system and the distribution system at the national level and shall consult with
the Demand Side Operators, Distribution, Provincial & SPTLs Systems Operators,
Demand Facilities Owners and stakeholders, including manufacturers.
CM 8.4.6 Register of Derogations
8.4.6.1 The NEPRA shall maintain a register of all derogations they have granted or refused.
8.4.6.2 The register shall contain, in particular:
(a) the requirement or requirements for which the derogation is granted

or refused;
(b) the content of the derogation;
(c) the reasons for granting or refusing the derogation;
(d) the consequences resulting from granting the derogation.
CM 8.5 Unresolved matters between NTDC and Users after a Review Panel shall be referred to
NEPRA for resolution whose decision shall be final and binding on all parties. The Grid
Review Panel or the Joint Grid Review Panel, as the case may be, shall need to refer to
the Authority and/or Authorities any matters requiring interpretation of the Grid Code
provisions.
CM 14
CM 9 PLANT FAILURES
CM 9.1 When partial breakage or partial failure of a Plant and/or Apparatus occurs which causes
a non-compliance but does not necessarily prevent the Plant and/or Apparatus being
operated safely or securely then the User shall promptly notify the SO of the non-
compliance and the User's proposed programme for remedying the non-compliance.
CM 9.2 Where time permits and if the SO reasonably considers that a non-compliance of a User
as described in GC.10.1 may have a materially adverse impact on another User or
Users, the SO will consult the affected User or Users as to the impact of the intended
non-compliance on the User or Users. If the SO considers that non- compliance may
have an impact on the CTBCM, it shall inform the Other SOs of the non-compliance.
CM 9.3 If the SO, acting reasonably, and taking into account the operation of the Transmission
System and the consultation with any affected Users in GC.10.2, is satisfied as to the
User's programme for remedying the non-compliance, and the breakage or failure is not
causing or is not likely to cause the Plant and/or Apparatus to materially affect the
security and stability of the Transmission System or other Users and is not likely to
impose unreasonable and unforeseen costs on the operation of the Transmission System
or other Users, then the SO may, for so long as the SO is so satisfied, treat the User as
being in compliance with the relevant provision of the Grid Code, and the User will be
deemed to be so compliant.
CM 9.4 If the SO, at its discretion, taking into account the operation of the Transmission System
and the consultation with any affected Users in GC.10.2, is not satisfied as to the User's
programme for remedying the non-compliance, the User shall apply for a derogation
under the terms of GC.9.
CM 9.5 When breakage or failure of a Plant and/or Apparatus occurs which causes a non-
compliance which prevents the Plant and/or Apparatus being operated safely or securely
then the User shall promptly notify the SO of the non-compliance and reflect such non-
compliance in Availability Notices and Technical Parameters.
CM 9.6 Notices and other data submitted under SDC1 until such time as the non-compliance
has been remedied.
CM 9.7 Failing agreement between the User and the SO, the User shall immediately apply for
derogation in accordance with GC.9.
CM 10 ASSISTANCE IN IMPLEMENTATION
CM 10.1 The SO has a duty to implement, and comply with, the Grid Code as approved by the
NEPRA.
CM 10.2 In order to fulfil its duty to implement the Grid Code the SO may, in certain cases, need
access across boundaries, or may need services and/or facilities from Users. This could,
for example, include De-Energising and/or disconnecting Plant and/or Apparatus. It is
hoped that these cases would be exceptional and it is not, therefore, possible to
envisage precisely or comprehensively what the SO might reasonably require in order to
put it in a position to be able to carry out its duty to implement the Grid Code in these
circumstances.
CM 10.3 Accordingly, all Users are required not only to abide by the letter and spirit of the Grid
Code, which shall include providing the SO with such rights of access, services and
facilities as provided for in appropriate agreements, and complying with such
instructions as the SO may reasonably require in implementing the Grid Code.
CM 15
CM 11 INFORMATION DISSEMINATION
The System Operator (SO) shall establish, operate and maintain a Web Site, providing necessary
information about the transmission system status, pricing, congestion, operating procedures,
technical and operational Committee meetings, and other relevant information and data.
CM 12 INDEMNITY TO THE NTDC

Each Code Participant shall keep NTDC and the System Operator indemnified at all
times against any claim, action, damage, loss, liability, expenses or outstanding liability
which NTDC or the System Operator pays, suffers, incurs or is liable for in respect of any
breach by such person or any of its officer, agent or employee.
CM 13 PRESERVATION OF CONTRACTS PRIOR TO ENACTMENT OF NEPRA ACT

During the implementation of agreements executed by the Participants of this Code, prior
to the enactment of NEPRA Act and carrying a sovereign guarantee for their
performance, nothing contained in this Code shall be applicable to such Participants
which is inconsistent with the terms and conditions of their agreements or impairs the
rights of these participants thereunder.
CM 14 CODE ADMINISTRATION
The NTDC shall be responsible for the enforcement and administration of the Grid Code.
CM 15 NON-COMPLIANCE
Non-compliance of any of the provisions of this Grid Code by any of the Code participants
shall be treated as a violation of the Grid Code and shall be subject to penalties as per
NEPRA Fees & Fines Rules (2002)-The First Schedule (Part-I, Sr. No. 5). Non-compliance
by NTDC of the Grid Code provisions applicable to NTDC shall be treated as a violation of
NTDC licence, and shall be subject to penalties as per NEPRA Fees & Fines Rules (2002).
CM 16
CM 16 UNFORESEEN CIRCUMSTANCES
CM 16.1 If unforeseen circumstances arise which are not included in the Grid Code, NTDC shall
promptly consult with all affected Users in an effort to reach an agreement on what
should and needs to be done under such circumstances.
CM 16.2 If agreement between the SO and those Users as to what should be done cannot be
reached in the time available, the SO shall determine what should be done. If the
unforeseen circumstance may have an impact on the CTBCM, the SO shall, where
possible, consult with the Other SO, with a view to jointly determining what should be
done. Whenever the SO makes such a determination it shall have regard wherever
practicable in accordance with this GC.12.2 to the views expressed by Users and, in any
event, the SO will act reasonably and in accordance with Prudent Utility Practice in all
circumstances. In addition the SO will, following such a determination and upon request,
make available to any affected User its reasons for the determination.
CM 16.3 Each User shall comply with all instructions given to it by the SO following such a
determination provided the instructions are consistent with the then current technical
parameters of the User System as notified under the Grid Code. The SO shall promptly
refer all such unforeseen circumstances, and any such determination, to the Grid Code
Review Panel or the Joint Grid Code Review Panel as appropriate for consideration in
accordance with GC.5.1(c).
CM 17 COMMUNICATIONS BETWEEN NTDC AND USERS

CM 17.1 All operational instructions issued by NTDC between NTDC and Users shall be
between the NTDC Control Engineer based at the NPCC, as advised to Users before
connection to the Transmission System, and the Users Responsible Engineer based
at a Regional Control Centre notified to NTDC before connection to the Transmission
System.
CM 17.2 Unless otherwise specified in the Grid Code, all operational communications detailed
in CM 4.1 shall be through Control Telephony (dedicated telephone network).
CM 17.3 All non-operational communications (data information and notices) between NTDC
and Users shall be inwriting and issued to the appropriate Officers of NTDC, the
System Operator, and each User.
CM 17.4 If for any reason NTDC or a User re-locates its Control Centre, NTDC or the User
must inform the other Party in writing of the move and advise the other party of any
changes to their Control Telephony.
CM 17.5 All instructions and communications given by Control Telephony are to be recorded
by whatever means available, and shall be acceptable by NTDC and Users as
evidence of those instructions or communications.
CM 18 OWNERSHIP OF FACILITIES, PLANT AND/OR APPARATUS

The Facilities, Plant and Apparatus of a User shall include Facilities, Plant and Apparatus
used by a User under an agreement with a third party.
CM 17
CM 19 SYSTEM CONTROL
Where a User System (or part thereof) is, by agreement, under the SO control, then for the purposes
of communication and the co-ordination of operational time scales the SO can (for these purposes
only) treat that User System (or part thereof) as part of the Transmission System, but as between
the SO and other Users it will continue to be treated as the User System.
CM 20 FORCE MAJEURE
CM 20.1 The Force Majeure has been defined in the Section on "Definitions". Code Participants
(as defined in the Section on “Definitions") should note that certain provisions of the
Grid Code may be suspended in whole or in part pursuant to any directive given by the
Authority under Force Majeure. NTDC shall inform NEPRA within Seven days of the
initiation of Force Majeure to be claimed by NTDC for the suspension of some or all
provisions of the Grid Code.
CM 21 HIERARCHY
In the event of any conflict between the provisions of the Grid Code and any contract,
agreement, or arrangement between the SO and a User, the provisions of the Grid Code
shall prevail unless the Grid Code expressly provides otherwise.
CM 22 ILLEGALITY AND PARTIAL INVALIDITY

CM 22.1 If any provision of the Grid Code should be found to be illegal or partially invalid for any
reason, the legality and validity of all remaining provisions of the Grid Code shall not be
affected.
CM 22.2 If part of a provision of the Grid Code is found to be unlawful or invalid but the rest of
such provision would remain valid if part of the wording were deleted, the provision
shall apply with such modification as may be necessary to make it valid and effective,
but without affecting the meaning or validity of any other provision of the Grid Code.
CM 23 MISCELLANEOUS
CM 23.1 Data and Notices
CM 23.2 References in the grid code to 'in writing’, shall include typewriting, printing,
lithography and other modes of reproducing words in a legible and non-transitory
form such as electronic communications.
CM 23.3 Where applicable all data items shall refer to Nominal Voltage and Frequency.
End of CM
CM 18
Appendixes: DEROGATIONS FORMS
EXA_1, 2, 3 and 4. Derogation forms
Example1: DSO, Provincial, SPTLs CONNECTION NETWORK

CODE DEROGATION APPLICATION FORM
APPLICANT
APPLICANT
CONTACT NAME
DATE
APPLICANT TELEPHONE
NUMBER
APPLICANT APPLICANT E-
POSTAL ADDRESS MAIL ADDRESS
DEROGATION
APPLICATION NUMBER
GRID CODE VERSION AND CLAUSE

FOR WHICH DEROGATION IS
SOUGHT
UNIT FOR WHICH A DEROGATION IS

REQUESTED
DEMAND CAPACITY (MW/MVA)
DESCRIPTION OF UNIT
DETAILS OF UPS OR ON
SITE GENERATION
DESCRIPTION OF DEROGATION
IMPACT ON THE ELECTRICITY SYSTEM

OF NON-COMPLIANCE
REASON FOR NON-COMPLIANCE

LEVEL OF NON-COMPLIANCE AND
CM 19
EFFORTS MADE TO
IMPROVE/ACHIEVE/MAXIMISE COMPLIANCE
COSTS INVOLVED TO ACHIEVE
COMPLIANCE
IMPACT ON THE INTERESTS OF
CONSUMERS/OTHER PARTIES
POTENTIAL FOR DISCRIMINATING
TREATMENT OF COMPARABLE UNITS
EFFECT OF DEROGATION ON CROSS-
BORDER TRADE
COST BENEFIT ANALYSIS Document:
THE END DATE OF THE REQUESTED
DEROGATION APPLICATION
PROPOSAL FOR REMEDYING

NON- COMPLIANCE.
PLEASE INCLUDE MILESTONES AND

DATES FOR REMEDYING NON-
COMPLIANCE, COSTS, AND RISK

FACTORS THAT MAY DELAY
COMPLIANCE.
(THIS SECTION MUST BE FILLED OUT FOR

ALL APPLICATIONS)
DETAILS OF SUPPORTING
DOCUMENTATION FOR APPLICATION (IF
ANY) ATTACHED
Please submit the completed EXA1_DEROGATION form and any supporting information to NTDC web-site
CM 20
SO CONNECTION NETWORK CODE DEROGATION APPLICATION FORM
APPLICANT
APPLICANT
CONTACT NAME
DATE
APPLICANT TELEPHONE
NUMBER
POSTAL ADDRESS MAIL ADDRESS
DEROGATION
APPLICATION NUMBER
GRID CODE VERSION AND

GENERATION//HVDC UNIT CLAUSE
FOR WHICH DEROGATION IS SOUGHT:
GENERATION/Demand Consumers/HVDC
UNIT(S)
FOR WHICH A DEROGATION IS
REQUESTED
TOTAL
INSTALLED
CAPACITY (MW)
MEC (MW)
NUMBER OF POWER
GENERATING
MODULES (PGMS)
Solar, Wind & ESGU GENERATION
UNITS ONLY SIZE (MW) OF EACH PGM
MAKE(S) AND MODEL(S)

OF PGMS
ENERGISATION DATE
DATE OPERATIONAL
CERTIFICATION
ACHIEVED
CM 21
Demand Users UNITS ONLY DEMAND
CAPACITY
(MW/MVA)
DESCRIPTION OF
Demand User UNIT
DETAILS OF UPS OR
ON SITE GENERATION
HVDC UNITS ONLY REGISTERED
EXPORT CAPACITY
(MW)
REGISTERED
IMPORT CAPACITY
(MW)
DESCRIPTION OF
HVDC UNIT

OF NON-COMPLIANCE

EFFORTS MADE TO
IMPROVE/ACHIEVE/MAXIMISE
COMPLIANCE
COSTS INVOLVED TO
ACHIEVE COMPLIANCE
IMPACT ON THE INTERESTS

OF CONSUMERS/OTHER
PARTIES
TREATMENT OF COMPARABLE
UNITS
EFFECT OF DEROGATION ON
CROSS- BORDER TRADE
CM 22
CONFIDENTIA
L
COST BENEFIT ANALYSIS FOR RFG

Generating Unit DEROGATIONS;
for Demand Units DEROGATIONS; AND
FOR HVDC DEROGATIONS.
(Methodology to be addressed as reference)
HVDC UNITS ONLY:
FOR DC-CONNECTED Solar, Wind &

ESU MODULES CONNECTED TO ONE OR
MORE
REMOTE-END HVDC
CONVERTER STATIONS:
PROVIDE EVIDENCE THAT THE

CONVERTER STATION WILL NOT BE
AFFECTED BY THE
DEROGATION; OR
PROVIDE EVIDENCE OF AN
AGREEMENT FROM THE CONVERTER
STATION OWNER TO THE PROPOSED
DEROGATION
THE END DATE OF THE

REQUESTED DEROGATION
APPLICATION

NON- COMPLIANCE.

COMPLIANCE.

ALL APPLICATIONS)
DOCUMENTATION FOR APPLICATION
(IF ANY) ATTACHED
CM 23
CONFIDENTIA
L
SO CONNECTION NETWORK CODE CLASS DEROGATION APPLICATION FORM
APPLICANT NTDC
APPLICANT CONTACT X Y NTDC department

NAME
DATE DD/MM/YYYY
APPLICANT TELEPHONE +353-1-XXX YYY
NUMBER
APPLICANT POSTAL APPLICANT E- X.Y@NTDC.com
ADDRESS NTDC Address MAIL ADDRESS
DEROGATION
APPLICATION NUMBER
NEPRA ….. establishing a Grid code on ……, which is also known

GRID CODE VERSION AND as the ….. Article XX(Y)(z), …..
GENERATION/Demand/HVDC UNIT
CLAUSE FOR WHICH DEROGATION IS
SOUGHT
DETAILS OF CLASS OF UNIT FOR WHICH A DEROGATION IS REQUESTED
Generating UNITS ONLY MAKE(S) AND MODEL(S)

OF UNIT
DESCRIPTION OF UNIT
TOTAL INSTALLED
CAPACITY
AFFECTED (MW)
NUMBER OF
AFFECTED SOLAR,
WIND & ESUSS &
PGMS CURRENTLY
INSTALLED
Demand User UNITS ONLY DEMAND
CAPACITY
(MW/MVA)
DESCRIPTION OF Demand
User
DETAILS OF UPS OR
ON SITE GENERATION
CM 24
CONFIDENTIA
L
HVDC UNITS ONLY REGISTERED EXPORT

CAPACITY
REGISTERED IMPORT
CAPACITY
DESCRIPTION OF HVDC
UNIT
DESCRIPTION OF NON-
COMPLIANCE/DEROGATION

OF NON-COMPLIANCE

EFFORTS MADE TO
IMPROVE/ACHIEVE/MAXIMISE
COMPLIANCE
COSTS INVOLVED TO
ACHIEVE COMPLIANCE
IMPACT ON THE INTERESTS

OF CONSUMERS/OTHER
PARTIES
TREATMENT OF COMPARABLE
UNITS
EFFECT OF DEROGATION ON
CROSS- BORDER TRADE
COST BENEFIT ANALYSIS:

FOR Generating Units
DEROGATIONS;
FOR Demand User Unit DEROGATIONS
FOR HVDC DEROGATIONS
CM 25
HVDC UNITS ONLY:
FOR DC-CONNECTED Solar, Wind & ESU

MODULES CONNECTED TO ONE OR
MORE REMOTE-END HVDC
CONVERTER
STATIONS:
PROVIDE EVIDENCE THAT THE CONVERTER
STATION WILL NOT BE AFFECTED BY

THE DEROGATION;
THE END DATE OF THE

REQUESTED DEROGATION
APPLICATION

NON- COMPLIANCE.

COMPLIANCE.

ALL APPLICATIONS)
(IF ANY) ATTACHED
CM 26
DSU CONNECTION NETWORK CODE DEROGATION APPLICATION FORM
APPLICANT
APPLICANT
CONTACT NAME
DATE
APPLICANT TELEPHONE
NUMBER
POSTAL MAIL
ADDRESS ADDRESS
DEROGATION
APPLICATION NUMBER
GRID CODE VERSION AND DSU CLAUSE FOR

WHICH DEROGATION IS SOUGHT
DEMAND SIDE UNIT FOR WHICH A

DEROGATION IS REQUESTED
DSU CAPACITY (MW) TOTAL
AVOIDED
CONSUMPTION
ON SITE GENERATION
TOTAL NUMBER TOTAL

OF INDIVIDUAL
DEMAND SITES AVOIDED
(IDS) IN DSU CONSUMPTION
ON SITE GENERATION
DESCRIPTION OF DSU
CM 27
Connection Name/Description Capacity Reduction
Code
IMPACT ON THE ELECTRICITY SYSTEM OF NON-COMPLIANCE
LEVEL OF NON-COMPLIANCE AND EFFORTS MADE TO IMPROVE/ACHIEVE/MAXIMISE COMPLIANCE
COSTS INVOLVED TO ACHIEVE COMPLIANCE
IMPACT ON THE INTERESTS OF CONSUMERS/OTHER PARTIES
POTENTIAL FOR DISCRIMINATING TREATMENT OF COMPARABLE UNITS
EFFECT OF DEROGATION ON CROSS- BORDER TRADE
COST BENEFIT ANALYSIS
THE END DATE OF THE REQUESTED DEROGATION APPLICATION
CM 28
CM 29
NON- COMPLIANCE.

COMPLIANCE.

ALL APPLICATIONS)
(IF ANY) ATTACHED
Please submit the completed EXA4 form and any supporting information to NTDC
30
PLANNING CODE
CONTENTS
PC1 INTRODUCTION, OBJECTIVE & SCOPE............................................... 31
PC2 PLANNING...................................................................................... 35
PC3 PLANNING DATA............................................................................. 37
PC4 PLANNING STANDARDS................................................................... 40
PC5 DATA VALIDATION & VERIFICATION.................................................. 41
Appendix A - STANDARD PLANNING DATA.................................................... 42
PART-1- GENERAL INFORMATION & USER'S SYSTEM DATA............................ 42
PART-2- GENERATED UNIT DATA.................................................................. 47
PART-3- DEMAND AND ACTIVE ENERGY DATA............................................... 70
Appendix B................................................................................................ 70
31
PLANNING CODE
PC1 INTRODUCTION, OBJECTIVE & SCOPE

The Planning Code provides requirements for the planning process by which the
objectives of system security, adequacy, reliability, and performance shall be
satisfied. Some of the objectives are:
(a) To specify the responsibilities of NTDC and other Users in the planning
and development of the national transmission grid/NTDC Transmission
System;
(b) To specify the planning procedures and technical studies that shall
ensure the safety, security, reliability, and stability of the national
transmission grid;
(c) To specify the planning data required from Users seeking new Connection
or a modification in their existing Connection to the NTDC Network;
(d) To specify the data requirements to be used by NTDC in planning the

development of the NTDC's Transmission System.
The Planning Code provides the basis for system reliability goals that are to be
achieved and maintained by NTDC and the System Operator. The reliability
goals need to be coordinated with policy objectives for the electric power sector
as well as with short-term and long-term system planning objectives.
The planning process is based on a philosophy that conforms to the regulatory

process, allows for competition, and is coordinated with operational
considerations. Requisite information inputs to the planning process from Code
Participants shall be provided.
The objective of the Code is to promote:
a) NTDC/User interaction for any proposed development on the User Systems

that may impact on the performance of the Transmission System or the
direct connection of the Transmission system
b) for an exchange of planning information between NTDC and Users and
specifies the Licence Standards that the NTDC shall adopt in planning and
developing its Transmission System.
c) For provision of information required by the TSO from Users in order for the
TSO to participate in the co-ordinated planning and development of both the
Transmission System and the Other Transmission System; and
d) For provision of information required by the TSO for the purposes of the
Transmission Forecast Statement
The Planning Code (PC) specifies the technical and design criteria, processes
and procedures, which NTDC shall apply to ensure that the NTDC Transmission
System is able to accommodate User System developments in a timely and
cost-effective manner. This code specifies the information to be exchanged
between NTDC and the Users. The reinforcement and/or extension of the NTDC
Transmission System may be necessary for several reasons, but not be limited
to the following:
a) development on a User System already connected to the NTDC

Transmission System;
32
b) the construction of a new Transmission Connection Point or the
modification of an existing Transmission Connection Point between a
User and the Transmission system;
c) changing requirements for electricity transmission facilities due to changes

in factors such as Demand, Generation, technology reliability
requirements, and/or environmental requirements
d) the cumulative effects of developments referred to in (a), (b) and (c).
To accommodate User System developments, reinforcements or extensions of

the NTDC Transmission System may involve the following activities:
(a) At new or existing Connection site where User’s plant and/or Apparatus is
connected to Transmission Connection;
(b) At a new or existing transmission circuit or other facilities which which

join that Connection site to the Transmission System;
(c) On remote transmission lines, which may not be directly connected to

that Connection site at the Transmission System.
The time required for the planning and subsequent development of the
Transmission System will depend on the type and extent of the necessary work,
the time required for obtaining planning permission and wayleaves, including
any associated hearings, and the degree of complexity in undertaking the new
work while maintaining satisfactory security and quality of supply on the
existing Transmission System.
PC 1.1 The scope of this Code applies to all NTDC Transmission System Users, i.e.
f) NTDC;
g) All Generators connected at the Transmission system
h) Generators with capacity greater than 10 MW;
i) DISCOs;
j) Transmission-connected Consumers; and
k) Externally Connected Consumers/Parties, like
10. Aggregators
12. Demand Customers
PC 1.2 Procedures for Transmission System Expansion

NTDC shall establish a planning process that leads to the recommendation of specific
transmission system reinforcements, upgrading, and expansion projects. Specific
projects shall be defined according to established planning criteria contained in this
Grid Code, and in response to load growth, and the NTDC Plan.
The TSEP shall be presented to NEPRA each year as part of the "Annual System
Reliability Assessment and Improvement Report", and shall be in terms of specific
projects. The projects shall be identified in terms of: new transmission lines, new
transmission circuits, new grid stations, new transformer installations, substation bus
33
expansions, voltage control projects, circuit breaker upgrading projects, elimination
of congestion bottlenecks, and system stability improvement projects.
NTDC shall participate in and coordinate its system planning efforts with the 132 kV
planning efforts to be carried out by the distribution companies and Provincial
Companies. In this regard, it is to be expected that there will be some joint projects
until the planning and development of the HV and EHV NTDC System makes the
NTDC System independent of the distribution company 132 kV system planning
process.
NTDC shall submit to NEPRA for information its proposed plan for its planning process
on or before the year of enforcement of the Grid Code. The Plan shall as a minimum
address the following points:
Load Forecasting
Three levels of load forecasts should be employed for a time horizon of at least next
twenty years for the long-term. The three levels are (1) High Growth; (2) Medium
Growth and (3) Low Growth projections. Factors that are to be taken into account
when preparing the load forecasts are: economic activity, population trends,
industrialization, weather, distribution companies forecasts, demand side
management, load shedding etc.
Project Identification
A Detailed "Transmission Investment Plan" shall be prepared that is based on the

"NTDC Twenty-Year Load Forecast", 'Indicative Generation Capacity Expansion Plan
(IGCEP or MT/STRATEGIC NTDC Plan )", and the Transmission System Expansion Plan
(TSEP) or Strategic Grid Development Plan (SGDP)" based on ASRAI. The Plans shall
be broken into several time periods. The Transmission Plan may be prepared for next
one, three, five and ten years into the future. The strategic Plan shall extend beyond
10 years up to 30 years.
Scenario Planning approach:
The SGDP shall capture the uncertainties in the Long Term. A scenario Planning
approach is suggested, where scenarios are prepared by a dedicated Scenario
Planning Group (SPG); its function shall be to track and identify potential new
industrial, commercial and government projects that can result in the need to
construct new generation, substations and transmission facilities or technology,
policies that can be deployed into Pakistan within the time frame of the study. The
present and future interconnectors and import/export programs shall also be
incorporated into the analysis. Through a consultation process with Stakeholders of the
Transmission Grid, SPG shall identified a number of developing scenarios .
The scenario planning approach is aiming at capturing robustness and volatility of Grid. It
is expected that more scenarios/developing trajectories shall be considered compare to
the MT analysis.
PC 1.3 Planning Procedure for Connection
PC.1.3.1 Information
Users and prospective Users of the Transmission System are able to assess opportunities for
connecting to, and using, the Transmission System, through:
(a) The statement, prepared by the TSO, enabling prospective Users to assess
for each of the 10 succeeding years, the opportunities available for connecting
to and using the Transmission System and to assess those parts of the
Transmission System most suited to new connections and transport of
further quantities of electricity;
34
(b) A Connection Offer by the TSO to enter into or amend a Connection
Agreement; and
(c) Published Use of System Tariffs.
PC.1.3.2 Application for Connection
PC.1.3.2.1 Users proposing a new Connection Site or Modification of an existing

Connection Site shall send an application form to the TSO.
PC.1.3.2.2 The application form to be submitted by a User when making an application for
a Connection Offer shall include:
(a) A description of the Plant and/or Apparatus to be connected to the

Transmission System or, as the case may be, of the Modification relating to
the User's Plant and/or Apparatus already connected to the Transmission
System, each of which shall be termed a "User Development" in the
Planning Code;
(b) The relevant data as listed in the Planning Code Appendix; and
(c) The desired Connection Date and Operational Date of the proposed User
Development.
PC.1.3.2.3 The application form for a Connection Offer shall be sent to the TSO as more
particularly provided in the connection offer process documentation.
PC.1.3.2.4 Data supplied in the application form or data submitted along with the
application form which is directly relevant to the application and has been
submitted in support of it will be treated as Preliminary Project Planning Data
until such time as the Connection Offer has been made and accepted.
PC.1.3.3 Connection Offer
PC.1.3.3.1 A Connection Offer shall include, but shall not be limited to, the following:
(a) details of how the connection is to be made, including details of the Plant
and Apparatus that will be required to implement the connection;
(b) a description of any Modification that the applicant User is required to

pay for;
(c) an indication of the Connection Date and the Operational Date; and
(d) an estimate of the charges for connection.
PC.1.3.3.2 Any Connection Offer will provide that it must be accepted by the applicant
User within the period stated in the Connection Offer. Acceptance of the
Connection Offer shall be effected by execution of the Connection
Agreement by both parties which renders the connection works relating to that
User Development committed and binds both parties in accordance with its
terms. The User shall supply the data pertaining to the User Development as
listed in the Appendix to this Planning Code in accordance with the terms of the
Connection Agreement.
PC.1.3.3.3 Once a Connection Offer has been accepted then all data supplied in the
application form and any data submitted along with the application form will be
treated as Committed Project Planning Data.
PC.1.3.4 Complex Connections
35
PC.1.3.4.1 The magnitude and complexity of any Transmission System development will
vary according to the nature, location and timing of the proposed User
Development which is the subject of the application and it may, in certain
circumstances, be necessary for the TSO to carry out additional or more
extensive system studies to evaluate more fully the impact of the proposed
User Development on the Transmission System. A proposed User
Development may also require system studies to be carried out to evaluate the
impact of the proposed User Development on the External System.
Where the TSO judges that such additional or more extensive studies are necessary, the TSO
shall advise the User the areas that require more detailed analysis and before
such additional studies are carried out, the User shall indicate whether it wishes
the TSO to undertake the work necessary to proceed to make a Connection
Offer within the period allowed or such extended time as the TSO, acting
reasonably considers is necessary.
PC.1.3.4.2 To enable the above detailed system studies to be carried out, the TSO may require
the User to supply some or all of the data items listed in the Appendix to this
Planning Code as Committed Project Planning Data in advance of the normal time-
scale, provided that the TSO considers that it is relevant and necessary. In the event
that such data items are supplied they will be treated as Preliminary Project Planning
Data submitted in support of the application as outlined in PC.4.3.2.4.
PC.1.3.5 Notice Required
Any User proposing to de-rate, close, retire, withdraw from service or otherwise
cease to maintain and keep available for Dispatch in accordance with Good
Industry Practice any Generation Unit or Generation Units or Controllable
Wind, Solar, ESPP with Registered Capacity greater than 50 MW in aggregate
shall give the TSO at least 36 calendar months’ notice of such action and any
Generation Unit or Generation Units or Controllable Wind, Solar, ESPP with
Registered Capacity less than or equal to 50 MW in aggregate shall give the TSO
at least 24 calendar months’ notice of such action.
PC2 SYSTEM PLANNING

PC 2.1 In order for the TSO to undertake the planning and development of the
Transmission System, in accordance with the relevant standards as provided for
in PC. 4, and, where appropriate, to participate in the co-ordinated planning and
development of both the Transmission System and the Other Transmission
System, the TSO will require Users to provide data and information on a regular
basis. Information received for this purpose will be treated as System Planning
Data.
Data requirements for planning of future works, which would include the development of new
facilities, reinforcements, up-ratings, extensions and augmentation of the
existing facilities, and planning for the new Connection Points shall be provided
to NTDC each year by all the Users/Code Participants on 1 st of January each
year.
PC 2.2 The TSO may also require additional data or information from a User. Where the
TSO considers that this information is required then the User where reasonable
shall submit the information to the TSO without delay so that it can execute
adequate system planning studies. Data can be the followings but not limited to:
a. any other data i.e. specific daily or hourly Load Curves, energy
consumption from the Users/Code Participants. The Users shall
supply all such data individually through quickest means of
communication; and
36
b. details of any individual loads which have characteristics
significantly different from the typical categories of domestic,
commercial, industrial, and agricultural loads supplied;
c. The sensitivity of the Load Demand (Active and Reactive Power)

to variations in voltage and Frequency on the NTDC
Transmission System at the time of the peak Load Demand
(Active Power); and
d. Details of any traction loads, arc furnace, welder etc.
Such information may be required so that the TSO can:
(a) plan and develop the Transmission System in accordance with the
relevant standards;
(b) undertake co-ordinated planning and development of both the
Transmission System and the Other Transmission System;
(c) monitor Power System adequacy and Power System performance and
project future Power System adequacy and Power System performance;
and
(d) fulfil its statutory and regulatory licensee obligations.
PC.2.3 In the planning and development of the Transmission System and, where
appropriate, in the co-ordinated planning and development of both the
Transmission System and the Other Transmission System, the TSO may
require an individual User, or group of Users, to modify or install new Plant or
Apparatus, where the TSO can reasonably show that it is prudent or necessary
to do so. A User may object on grounds that to modify or install new Plant or
Apparatus as required, in accordance with Good Industry Practice, would be
technically infeasible. This may include, but shall not be limited to, for example,
the installation of Power System Stabilisers.
PC.2.4 Technical parameters of User Apparatus and Plant connected to the NTDC
Transmission System, including the submission of updated technical
parameters whenever there is a change of User Apparatus or Plant shall be
submitted as and when required according to PC.Appendix as the case may
be.
PC.2.5 NTDC Technical and Network Operator's Data
NTDC must provide data to the User of the network and receive data from the
User of the network according to PC.A.8.
NTDC shall have network data relevant to short circuit current contributions.
NTDC is required to make available to Users the network Operator's Data

relevant to short circuit current contributions listed in Part 3 of Appendix A
(PC.A.2.4.7) and Part 2 of Appendix A. NTDC is required to make this
technical data available in week 45 of each year to cover for the following
NTDC's Calendar Year.
Information to be provided to NTDC by the Users and Network Operators or

Vice Versa for planning purposes is covered in Appendix A and B of this sub-
code.
37
PC3 PLANNING DATA
PC.3.1 As far as the Planning Code is concerned, there are three relevant types of
data:
1. Preliminary Project Planning Data,

2. Committed Project Planning Data and
3. System Planning Data.
PC.3.1.1 These types of data are submitted to different levels of confidentiality,
commitment and validation, as described below.
PC.3.1.2 Preliminary Project Planning Data and Committed Project Planning

Data relate to the data required from a User at various stages during the
process for introduction of a new Connection Site or Modification of an
existing Connection Site as outlined in PC.4.2, and more specifically in the
application form for a Connection or Modification.
System Planning Data relates to the data that must be submitted at regular periods by all
Users, or other such data or information as requested by the TSO under
PC.5.
PC.3.2 An existing User proposing a new Connection Site will need to supply data
both in an application for a Connection Offer and under the Planning Code
in relation to that proposed new Connection Site and such information will
be treated as Preliminary Project Planning Data or Committed Project
Planning Data (as the case may be), but the data an existing User supplies
under the Planning Code relating to its existing Connection Sites will be
treated as System Planning Data.
PC 3.3 Preliminary Project Planning Data

PC.3.3.1 At the time the User applies for a Connection Offer but before such an offer
is made by the TSO, the data relating to the proposed User Development
will be considered as Preliminary Project Planning Data. This data will be
treated as confidential within the scope of the provisions relating to
confidentiality in the TSO policy on confidentiality. The TSO may disclose
Preliminary Project Planning Data to the Other TSO.
The following information shall be published on the TSO website:
(i) User’s name (legal and project name);
(ii) User’s contact details;
(iii) User’s date of completed application;

(iv) Status of application, for example in progress or issued;
(v) Specific location, including grid co-ordinates;
(vi) The Registered Capacity applied for; and
(vii) Interacting group where applicable.
PC.3.3 Preliminary Project Planning Data contains such data as may be

reasonably required by the TSO or Other TSO to evaluate the connection
application/ as outlined in PC.4.2 and, if applicable, any other data directly
relevant to, and submitted in support of, the application.
PC 3.4 Committed Project Planning Data

PC.3.4.1 Once the Connection Offer has been formally accepted by the prospective
User, the data relating to the User Development, already submitted as
38
Preliminary Project Planning Data, and any subsequent data required by
the TSO under this Planning Code, will become Committed Project
Planning Data. This data, together with other data held by the TSO and the
Other TSO relating to the Transmission System and the Other
Transmission System, will form the basis from which new applications by
any User will be considered and from which planning of the Transmission
System or Other Transmission System and power system analysis will be
undertaken. Accordingly, Committed Project Planning Data will not be
treated as confidential to the extent that the TSO is obliged:
(a) to use it in the preparation of the Forecast Statement and in any
further information given pursuant to the Forecast Statement;
(b) to use it when considering and/or advising on applications (or
possible applications) of other Users (including making use of it by
giving data from it, both orally and in writing, to other Users making
an application (or considering or discussing a possible application)
which is, in the TSO's view, relevant to that other application or
possible application);
(c) to use it for the TSO planning purposes and to use it when
participating in co-ordinated planning and development of both the
Transmission System and the External Systems;
(d) the TSO may disclose it to the Other TSO for the purposes of
consideration of developments on the Other Transmission System;
and
(e) the TSO may disclose it to the External TSO for the purposes of
consideration of Interconnector developments with the External

System.
PC.3.5 To reflect different types of data, Preliminary Project Planning Data and
Committed Project Planning Data are themselves divided into those
items of Data which:
(a) will always be forecast, known as Forecast Data;
(b) upon connection become fixed (subject to any subsequent changes),

known as Registered Data; and
(c) relate to Plant and/or Apparatus which upon connection will
become Registered Data, but which prior to connection will be an
estimate of what is expected, known as Estimated Registered
Data.
PC.3.6 System Planning Data

PC.3.6.1 The Planning Code requires that, as soon as is practical, and not later than a
date which is the earlier of 18 months prior to the scheduled Operational
Date or six months after the signing of the Connection Agreement, unless
otherwise directed by NEPRA, all data requirements as stated in the
Appendix to the Planning Code, not previously requested by the TSO and
supplied by the User, will be submitted by the User to the TSO. This will
include confirming any estimated values assumed for planning purposes or,
where practical, replacing them by validated actual values and by updated
estimates for the future and by updating forecasts for Forecast Data items
such as Demand. As more accurate data becomes available, due to
completion of detailed design, test measurements/results or any other
sources, this information will be submitted by the User to the TSO as soon as
practicable and not later than the Operational Date.
39
PC.3.6.2 The Planning Code requires that Users submit to the TSO, each year, the
System Planning Data as listed in section PC.A3.3 of the Appendix to the
Planning Code. This data should be submitted by calendar week 9 of each
year and should cover each of the ten succeeding years (and in certain
instances the current year). Where from the date of one submission to the/a
subsequent date submission there is no change in the data to be submitted
for any given year, instead of resubmitting the data, a User may submit a
written statement that there has been no change from the data submitted the
previous time, pertaining to the particular year specified.
PC.3.7 System Planning Data, together with other data held by the TSO and the
Other TSO relating to the Transmission System and the Other
Transmission System, will form the basis from which new applications by
any User will be considered and from which planning of the Transmission
System will be undertaken. Accordingly, System Planning Data will not be
treated as confidential to the extent that the TSO is obliged:
(a) to use it in the preparation of the Forecast Statement and in any

further information given pursuant to the Forecast Statement;
(b) to use it when considering and/or advising on applications (or
possible applications) of other Users (including making use of it by
giving data from it, both orally and in writing, to other Users making
an application (or considering or discussing a possible application)
which is, in the TSO's view, relevant to that other application or
possible application);
(c) to use it when participating in co-ordinated planning and
development of both the Transmission System and the External
Systems;
(d) to use it for the TSO planning purposes;
(e) to disclose it to the External TSO as the case may be, so that it can
meet its statutory and legal requirements for the External System.
To reflect the different types of data referred to above System Planning Data is
itself divided into those terms of data:
1) which will always be forecast, known as Forecast Data;
2) which upon connection become fixed (subject to any subsequent

changes), known as Registered Data; and
3) which relate to Plant and/or Apparatus which for the purposes of
the Plant
and/or Apparatus concerned as at the date of submission are

Registered.
Demand, Active and Reactive Energy Data
Each Code Participant/User directly connected to the NTDC Transmission

System shall provide to NTDC its Load Demand data, historic, current and
projected. The required data shall be provided for each substation in each
User/Code Participant's System as applicable.
Each User/Code Participant shall provide forecast data for power demand,
Active and Reactive energy and demand requirements on its System. The
User/Code Participant shall separately indicate its nonBPC Load Demand on
40
sector-wise basis. BPC's Demand, and the Load Demand of the Second-tier
Users of their network, if any.
The Code Participants shall provide Demand Data according to PC A.4.
PC4 PLANNING STANDARDS
PC.4.1 The TSO shall apply the Transmission System Security Planning
Standards (TSSPS) and relevant standards in the planning and
development of the Transmission System and where appropriate when
participating in the co-ordinated planning and development of both the
Transmission System and the Other Transmission System.
PC.4.2 In assessing the technical requirements of a User's connection, the TSO
shall not discriminate between Users of a similar category, location or size
although it will not be technically or economically practicable to achieve
uniformity of method of connection at all times.
PC.4.3 The Transmission System Voltage level at which a User's System will be
connected and the busbar configuration which a User's System uses will
depend upon but shall not be limited to the following:
(a) the size of the Generation Units and the number of

Generation Units comprising the User's System;
(b) the size and rating of the Interconnector;
(c) proximity to the existing Transmission System; and
(d) the cost of the proposed connection.
PC.4.4 The Transmission System Voltage level at which a Demand Customer

will be connected to the Transmission System will depend upon but shall
not be limited to the following:
(a) the size of the MW Demand at the Connection Point;
(b) consistency with future development of the Transmission System or

the Other Transmission System;
(c) proximity to the existing Transmission System.; and
(d) the cost of the proposed connection.
PC.4.5 The Transmission System Voltage level at which the Distribution System
Operator
will be connected to the Transmission System will depend upon but shall
not be limited to the following:
(a) the size of the MW Demand at the Connection Point;
(b) consistency with future development of the Transmission System or

the Other Transmission System;
(c) consistency with co-ordinated planning of the Transmission System

and of the Distribution System;
(d) proximity to the existing Transmission System; and
41
(e) the cost of the proposed connection.
PC.4.6 The method of connection used may exceed the relevant standards where
this is required by the User and is acceptable to the TSO.
PC5 DATA VALIDATION & VERIFICATION

PC.5.1 Where a User submits data, which in the opinion of the TSO (or in its opinion
following referral with the Other TSO) is incorrect then the TSO may request
that that User supply such additional information as the TSO deems
necessary to verify the accuracy of the data.
PC.5.2 Where, following consideration of such information submitted under PC.5.1,

the TSO maintains (or maintains following referral with the Other TSO),
acting reasonably, that the additional information is insufficient to verify the
accuracy of the original data then the TSO may request that the User carry
out specific Tests to verify the data. Where such a Test or Tests are
requested, they will be subject to the provisions of the relevant operational
codes.
PC.5.3 In the event that the data as submitted by the User is verified by the Test or
Tests to be correct then all costs reasonably incurred as a result of such Test
or Tests as agreed will be borne in full by the TSO.
PC.5.4 In the event that any of the data items submitted are shown to be incorrect or
inaccurate then the User will bear the cost of the Test in full and the data
values as ascertained by the Tests will be the values used in the data. If, as a
result of the changes to the data arising from the Test or Tests, the TSO
have to redo or perform additional system studies then the User will also
bear the cost reasonably incurred as a result of this additional work.
Data but which for the ten succeeding years will be an estimate of what is
expected, known as Estimated Registered Data.
42
Appendix A
This appendix specifies data to be submitted to the TSO by Users or prospective Users of the
Transmission System. The requirement to provide data is governed by the Planning Code
(PC.4.2, PC.4.3, PC.4.4).
The specific data requirements depend on whether the User is a Customer or a Generator or
Interconnector or an Aggregator or an External Party in general or more than one combined.
PC.A1 and PC.A2 apply to all Users.
PC.A3 applies to Generators.
PC.A4 applies to demand Users.
PC.A5 applies to Controllable Solar, Wind and ESPP.
PC.A6 applies to Interconnectors.
PC.A7 applies to Aggregators.
PC.A8 refers to the dynamic Model requirements for Users. For the avoidance of doubt,
PC.A8 may apply to the DSO, where the need for such Models is identified.
Any material changes to the data specified in PC.A3, PC.A4, PC.A5, PC.A6 or PC.A7 must be notified
to the TSO as soon as practicable.
PART-1- STANDARD PLANNING DATA
PC.A.1 GENERAL INFORMATION
All Users connected directly through existing Connection Points to the NTDC
Transmission System or seeking a direct Connection shall provide NTDC data
on their Systems which relates to the Connection Site which may have an
effect on the performance of NTDC Transmission System.
PC.A1.1 Full name of the User(s)

PC.A1.2 Address of the User(s)
PC.A1.3 Contact Person
PC.A1.4 Telephone Number
PC.A1.5 Telefax Number
PC.A1.6 Email Address
PC.A.2 USER'S SYSTEM DATA
PC.A2.1 Map and Diagrams
Provide a 1:50,000 Survey map, with the location of the facility clearly marked with an "X". In
addition, please specify the Survey Grid Co-ordinates of the electrical connection
point which is assumed to be at the HV bushings of the Grid Connected
Transformer.
PC.A2.2. Provide a plan of the site (1:200 or 1:500) of the proposed facility, indicating
the proposed location for a transmission station compound, location of the
connection point, generators, transformers, converter stations, site buildings
etc. The plan is to be submitted in hard copy format. A digitised format may be
required and should also be provided if available.
PC.A2.3 Licensing and Authorisation (For Generation, Interconnector and other applications
requested by the TSO)
PC.A2.3.1 Licence
43
Details of any Generation or Interconnector or Supply Licence held by the
applicant, or of any application for a Generation or Interconnector or Supply
Licence.
PC.A2.3.2 Authorisation
Details of any authorisation or application for authorisation to construct or reconstruct the Generation
station, Interconnector or other applications requested by the TSO for which the
connection is being sought.
PC.A.2.4 User's System Layout
PC.A.2.4.1 Each User shall provide a Single Line Diagram, depicting both its existing and
proposed arrangement(s) of load current carrying apparatus relating to both
existing and proposed Connection Points.
PC.A.2.4.2 The Single Line Diagram must include all parts of the User System operating at EHV
and those parts of its sub-transmission system at any NTDC Site. In addition, the
Single Line Diagram must include all parts of the User's sub-transmission system
operating at a voltage 66kV & above.
At the User's discretion, the Single Line Diagram can also contain additional details
of the User's sub-transmission System not already included above, and also details
of the transformers connecting the User's sub-transmission system to a lower
voltage. With NTDC's agreement, the Single Line Diagram can also contain
information about the User's System at a voltage below the voltage of the sub
transmission system.
PC.A 2.4.3 The Single Line Diagram shall also include:
(a) Electrical circuitry identifying overhead lines, underground cables, power

transformers reactive compensation equipment and similar equipment etc.
(b) Name of the sub-station with operating voltages
(c) Circuit breakers isolators, current transformers, potential transformers,

protection data.
PC.A.2.4.4 For each circuit shown on the Single Line Diagram, the User shall provide the
following circuit parameters details relating to that part of its system:
Circuit Parameters
(a) Rated voltage (kV)
(b) Operating voltage (kV)
(c) Line Length (km)
(d) Conductor Name
(e) Type of Tower
(f) Positive phase sequence reactance
(g) Positive phase sequence resistance
(h) Positive phase sequence susceptance
(i) Zero phase sequence reactance
(j) Zero phase sequence resistance
(k) Zero phase sequence susceptance
PC.A.2.4.5 For each transformer shown on the Single Line Diagram, the User shall provide the
following details:
44
(a) Rated MVA
(b) Voltage Ratio
(c) Winding arrangement
(d) Positive sequence reactance for all windings
(e) Positive sequence resistance for all windings
(f) Zero sequence reactance for all windings
PC.A.2.4.6 In addition, for all interconnecting transformers between the User's EHV Voltage
System and the User's Sub-transmission System the User shall supply the following
information:
(a) Earthing system details i.e. direct, resistance or reactance impedance (if not
directly earthed).
(b) Tap changer range
(c) Tap change step size
(d) Tap changer type
PC.A.2.4.7 User shall supply the following information about the User's equipment installed at a
Connection Site which is owned, operated or managed by NTDC:
(a) Switchgear: User shall provide the following parameters for the circuit
breakers.
(i) Rated Voltage (kV)
(ii) Operating Voltage (kV)
(iii) Rated 3-phase rms short-circuit breaking current, (kA)
(iv) Rated 1-phase rms short-circuit breaking current, (kA)
(v) Rated 3-phase peak short-circuit making current, (kA)
(vi) Rated 1-phase peak short-circuit making current, (kA)
(vii) Rated rms continuous current (A)
(viii) DC time constant applied at testing of asymmetrical breaking abilities

(Secs.)
(b) Substation Infrastructure: User shall provide the following parameters for the
installed electrical equipment.
(i) Rated 3-phase rms short-circuit withstand current, (kA)
(ii) Rated 1-phase rms short circuit withstand current, (kA)
(iii) Rated 3-phase short-circuit peak withstand current, (kA)
(iv) Rated 1-phase short-circuit peak withstand current, (kA)
(v) Rated duration of short circuit withstand (Secs)
(vi) Rated rms continuous current (A)
(c) Detailed short circuit data for single-point or multi-point connection sites.
PC.A.2.4.8 Lumped System Susceptance
45
For all parts of the User's Sub-transmission System which are not included in the
Single Line Diagram provided under PC.A.2.1.1, each User shall provide the
equivalent lumped shunt susceptance at Nom·1nal frequency.
PC.A.2.4.9 Reactive Compensation Equipment
For all independently switched reactive compensation equipment, including that

shown on the Single Line Diagram, not owned by NTDC and connected to the User's
System at 132kV and above, other than power factor correction equipment
associated directly with User's Plant and Apparatus, the User shall supply the
following information is required.
(a) Type of equipment (e.g. fixed or variable);
(b) Capacitance and/or inductive rating or its operating range in Mvar;
(c) Details of any automatic control logic to enable operating characteristics to be

determined;
(d) The Point of Connection to the User's system in terms of electrical location
and system voltage; and
(e) Voltage assessment studies of the User system.
PC.A.2.4.10 Short Circuit Contribution to NTDC Transmission System
General
(a) To allow NTDC .to calculate fault currents, each User is required to provide
data and short circuit analysis of its system; calculated in accordance with
good industry practice, as set out in the following paragraphs.
(b) The data should be provided for the User's system with all Generating Units
synchronized to the User's System. The User must ensure that the pre-fault
network conditions reflect a credible system operating arrangement.
(c) The list of data items required, in whole or part, under the following
provisions. Each of the relevant following provisions identifies which data
items in the list are required for the situation with which that provision deals.
The fault current in sub-paragraphs (a) and (b) of the data list should be based on
an ac load flow that takes into account any pre-fault current flow across the Point of
Connection being considered. Measurements made under appropriate system.
conditions may be used by the User to obtain the relevant data.
(d) NTDC may at any time, in writing, specifically request for data to be provided
for any alternative system condition, for example minimum plant, and the
User will insofar as such request is reasonable, provide the information as
soon as reasonably practicable following the request.
PC.A.2.2.11 GENERATOR DATA
For each Generating Unit with one or more associated Station Transformers, the
Generator is required to provide values for the contribution of the power plant
auxiliaries (including auxiliary gas turbines or auxiliary diesel engines) to the fault
current flowing through the Station Transformer(s).
(a) Root mean square of the symmetrical three-phase short circuit current in feed
at the instant of fault:
(b) Root means square of the symmetrical three-phase short circuit after the sub-
transient fault current contribution has substantially decayed;
46
(c) If the associated generating unit step-up-transformer can supply zero phase
sequence current from the generating unit side to the NTDC Transmission
System;
(d) If the value is not 1.0 p.u;
(e) Root mean square of the pre-fault voltage at which the maximum fault
currents were calculated.
PC.A.2.2.12 If the Power Plant has separate Station Transformers, data should be provided for
the fault current contribution from each transformer at its high voltage terminals,
assuming a fault at that location, as follows: -
Data for the fault in feeds through both Step-up Transformers and Stations
Transformers shall be provided for the normal running arrangement when the
maximum number of Generating Units in the Power Station are synchronized to the
System.
Data Items
(a) The following is the list of data utilized in this part of the Planning Code.
(i) Root mean square of the symmetrical three-phase short circuit current
in feed at the instant of fault;
(ii) Root mean square of the symmetrical three-phase short circuit after the
sub-transient fault current contribution has substantially decayed;
(iii) The zero sequence source resistance and reactance values of the User's
System as seen from the node on the Single Line Diagram provided;
(iv) Root mean square of the pre-fault voltage at which the maximum fault
currents were calculated;
(v) The positive sequence X/R ratio at the instant of fault; and
(vi) The negative sequence resistance and reactance values of the User's
System seen from the node on the Single Line Diagram
47
PART-2- STANDARD PLANNING DATA
PC.A.3 GENERATED UNIT DATA
PC.A.3.1 General Details
Each Generator shall submit to the TSO detailed information as required to plan,
design, construct and operate the Transmission System.
Station Name
Number of Generating Units
Primary Fuel Type / Prime Mover (e.g. gas, hydro etc.)
Secondary Fuel Type (e.g. oil)
PC.A.3.2 Treatment of Generator Data
i. data item which must be provided by the applicant and which shall be
treated as Preliminary Project Data as discussed in PC.6.3.
ii. data item which, if not provided by the applicant as Preliminary Project
Data, will be estimated by the TSO at the applicant's sole risk. The TSO
puts the applicant on notice that this data estimate shall be treated as
Preliminary Project Data as discussed in PC.6.3.
Once the Connection Offer has been formally accepted by the prospective User all
data shall be provided by the User and treated as Committed Project Planning
Data as discussed in PC.6.4.
Following the Operational Date or Modification Date as appropriate, all data
requirements as listed in this appendix shall be submitted by the User to the TSO
and shall be treated as System Planning Data as discussed in PC.6.6. This will
include confirming any estimated values assumed for planning purposes and
replacing them by validated actual values and by updated estimates for future
Forecast Data.
PC.A.3.3 Directly Connected Generators
Each Generator shall provide the following data to NTDC.
PC.A.3.3.1 Generator Operating Characteristics and Registered Data
Minimum requirements for generator operating conditions are specified in the

Connection Conditions.
For thermal plant, provide a functional block diagram of the main plant components,
showing boilers, alternators, any heat or steam supplies to other processes etc.
indicate whether single shaft or separate shaft.
For each individual unit, on Primary Fuel and on Secondary Fuel where
applicable, fill in the following:
1. Unit Number
2. Registered Capacity (MW)
3. Fuel
48
Symbol Units
* Normal Maximum Continuous Generation Capacity: MW
* Normal Maximum Continuous Export Capacity M

W
Primary Fuel Switchover Output M
Secondary Fuel Switchover Output W
MW
* Power Station Auxiliary Load MW
Power Station Auxiliary Load Mvar
* Maximum (Peaking) Generating Capacity MW
* Maximum (Peaking) Export Capacity MW
* Normal Minimum Continuous Generating Capacity MW
* Normal Minimum Continuous Export Capacity MW
* Generator Rating:
Mbase MVA
* Normal Maximum Lagging Power Factor

Mvar
* Normal Maximum Leading Power Factor Mvar
Governor Droop R
Forbidden Zones MW
Terminal Voltage adjustment range kV
Short Circuit Ratio
Rated Stator Current Amps

* Number of available hours of running at Registered Capacity from on-site fuel storage stocked to its full
capacity.
Description
Capability Chart showing full range of operating capability of the generator Diagram
including thermal and excitation limits.
Open Circuit Magnetisation Curves Graph
Short Circuit characteristic Graph
Zero power factor curve Graph
§ V curves Diagram
Symbol Units
Time to synchronise from warm Hour
Time to synchronise from cold Hour
Minimum Up Time Hour
Minimum Down Time Hour
Normal loading rate MW / min
49
§ Normal deloading rate MW / min
§ Can the Generator start on each fuel
§ Ability to change fuels on-load
§ Available modes (lean burn, etc.)
§ Time to change modes on-load
§ Control range for AGC operation MW
Other relevant operating characteristics not otherwise provided....
Reserve Capability
 Primary Spinning Reserve
 Secondary Spinning Reserve
 Tertiary Reserve
Give details of reserve capability of the Generator in different operating modes: Unit co-
ordinating, turbine follow, recirculation, base load, etc.
What reserve, if any, is available when the unit is off load?
CCGT Installation Matrix

This matrix is a look up table determining which CCGT Unit will be operating at any given
MW Dispatch level. This information will be applied for planning purposes and for
scheduling, Dispatch and control purposes as covered in the SDCs unless by prior
agreement with the TSO.
As an example of how the matrix might be filled out, consider a sample unit with a total
capacity of 400 MW made up of two 150 MW combustion turbines and one 100 MW
steam turbine. In this case, the following ranges might be specified:
0 MW to 50 MW GT1
50 MW to 170 MW GT1 and ST
170 MW to 400 MW GT1 and GT2 and ST
Please insert MW ranges and tick the boxes to indicate which units are synchronised to
deliver each MW range at the following atmospheric conditions: Temperature 10°C,
Pressure 1.01 bar and 70% Humidity.
CCGT INSTALLATION CCGT UNIT AVAILABLE
OUTPUT USABLE 1s 2nd 3rd 1s 2n 3r

t t d d
GT GT
GT ST ST ST
OUTPUT USABLE
Unit MW Capacity → e.g. 150 150 - 100 - -
Total MW Output Range ↓
PC.A.3.4 Generator Parameters
50
Symbol Units
* direct axis Synchronous reactance Xd % on rating
* direct axis Transient reactance saturated ' % on rating

X
d sat
* direct axis Transient reactance unsaturated ' % on rating

X
d unsat
* Sub-transient reactance unsaturated '' '' % on rating

X X
d q
Quad axis Synchronous reactance Xq % on rating
Quad axis Transient reactance unsaturated ' % on rating

X
q unsat
Negative Phase Sequence Synchronous X2 % on rating

reactance
Zero phase sequence reactance X0 % on rating
* Turbine generator Inertia constant for entire H MW s/MVA

rotating mass
§ Stator resistance Ra % on rating
§ Stator Leakage reactance XL % on rating
§ Poiter reactance XP % on rating
PC.A.3.4.1 Generator Time Constants

Symbol Units
Direct axis open Circuit Transient Tdo’ sec
Direct axis open Circuit sub-Transient Tdo’’ sec
Quad axis open Circuit Transient Tqo’ sec
Quad axis open Circuit sub-Transient Tqo’’ sec
Direct axis short Circuit Transient Td’ sec
Direct axis short Circuit sub-Transient Td’’ sec
Quad axis short Circuit Transient Tq’ sec
Quad axis short Circuit sub-Transient Tq’’ sec
PC.A.3.5 Mechanical Parameters
Provide mechanical parameters of the Generator that affect the dynamic

performance of the Generator. This may include the stiffness of the shaft, a multi-
mass model of the Plant components, torsional modes, mechanical damping or
parameters as specified by the TSO.
PC.A.3.6 Excitation System
51
Provide parameters and supply a Laplace-domain control block diagram (or as
otherwise agreed with the TSO) completely specifying all time constants and gains to
fully explain the transfer function from the compensator or generator terminal voltage
and field current to generator field voltage. These parameters may include but are not
limited to:
Description Symbol Units

Excitation system type (AC or DC) Text
Excitation feeding arrangement (solid or shunt) Text
Excitation system Filter time constant Tr sec
Excitation system Lead time constant Tc sec
Excitation system Lag time constant Tb sec
Excitation system Controller gain Ka
Excitation system controller lag time constant Ta sec
Excitation system Maximum controller output Vmax p.u.
Excitation system minimum controller output Vmin p.u.
Excitation system regulation factor Kc
Excitation system rate feedback gain Kf
Excitation system rate feedback time constant Tf sec
PC.A.3.7 Speed Governor System
Supply a Laplace-domain control block diagram and associated parameters of

prime mover models for thermal and hydro units (or as otherwise agreed with the
TSO) completely specifying all time constants and gains to fully explain the transfer
function for the Governor Control System in relation to Frequency deviations
and setpoint operation.
PC.A.3.8 Control Devices (including Power System Stabilisers) and Protection

Relays Supply any additional Laplace domain control diagrams and associated
parameters for any outstanding control devices including Power System
Stabiliser or special protection relays in the generating unit, which automatically
impinge on its operating characteristics within 30 seconds following a system
disturbance and which have a minimum time constant of at least 0.02 seconds.
PC.A.3.9 Environmental Impact
CO2 tonne CO2 / tonne fuel
Unit CO2 removal efficiency
SO2 tonne SO2 / tonne fuel
Unit SO2 removal efficiency
NOX tonne NOX / exported MWh curve
PC.A.3.10 Pumped Storage
Reservoir Capacity MWh pumping
52
Max Pumping Capacity MW
Min Pumping Capacity MW
Efficiency (generating / pumping ratio) %
PC.A.3.11 Generator Transformer
Symbol Units
Number of windings
Vector Group
Rated current of each winding Amps
Transformer Rating MVATrans
Transformer nominal LV voltage kV
Transformer nominal HV voltage kV
Tapped winding
Transformer Ratio at all transformer taps
Transformer Impedance at all taps1 % on rating

MVATrans
Transformer zero sequence impedance at nominal tap Z0 Ohm
Earthing Arrangement including neutral earthing resistance & reactance
Core construction (number of limbs, shell or core type)
Open circuit characteristic Graph
PC.A.3.12 Generator Forecast Data
PC.A 3.12.1 Expected Maintenance Requirements

Expected Maintenance Requirements weeks/year
PC.A 3.12.2 Forecast Availability of Registered Capacity
Apart from the expected scheduled maintenance requirements
Availability of Registered Reason Available Exported MW Time %
Capacity
Registered Capacity
Restricted Rating
Forced Outage Probability

Total 100%
Reasons for restricted rating might include poor fuel, loss of mill, loss of burners, hydro flow restrictions,
etc.
PC.A 3.12.3 Energy Limitations
1
For Three Winding Transformers the HV/LV1, HV/LV2 and LV1/LV2 impedances together with associated bases shall be provided.
53
Daily GWh
Weekly GWh
Monthly GWh
Annual GWh
PC.A 3.12.4 Hydro Expected Monthly GWh
January GWh
February GWh
March GWh
April GWh
May GWh
June GWh
July GWh
August GWh
September GWh
October GWh
November GWh
December GWh
PC.A.4 DEMAND AND ACTIVE ENERGY DATA
PC.A4.1 Treatment of Demand Data
At the time the User applies for a connection offer but before an offer is made by the TSO
and accepted by the applicant User the above data will be considered as Preliminary
Project Planning Data as described in PC.6.3.
Once the Connection Offer has been formally accepted by the prospective User all data
shall be provided by the User and treated as Committed Project Planning Data as
discussed in PC.6.4.
Following the Operational Date or Modification Date as appropriate, all data
requirements as listed in this appendix shall be submitted by the User to the TSO and shall
be treated as System Planning Data as discussed in PC.6.6. This will include confirming
any estimated values assumed for planning purposes and replacing them by validated
actual values and by updated estimates for future Forecast Data.
PC.A4.2 Registered Connection Capacity

The registered connection capacity is required in MW and Mvar, corresponding to the
maximum MVA. It should be stated whether the User is producing or absorbing Mvar.
PC.A4.3 Measured and Forecast Data

This section details the measurements of demand and 10-year demand forecasts that are
required from each User of the Transmission System who is a Demand Customer in
respect of each infeed from the Transmission System to the Customer’s network(s).
This section applies equally to the Distribution System Operator (DSO).
54
The TSO shall notify each User who is a Demand Customer in advance of each load
reading day. These load reading days are winter peak, summer and summer minimum as
specified in sections PC.A3.3.2, PC.A3.3.3 and PC.A3.3.4 respectively.
The measurements of demand and 10-year demand forecasts should be submitted by the
end of calendar week 9 of each year.
PC.A4.3.1 Measurement Point

Demand measurements and forecasts for each infeed from the Transmission
System shall relate to the appropriate Measurement Point.
Network Operator's Demand (MW) and Active Energy Requirements (MWHs)
shall be calculated and forecasted based on Demand data History. The
following forecasted Daily Demand Profiles (Active Power) shall be estimated.
(a) Time of Peak, and Maximum Load Demand (Winter peak) (Active Power
and Active Energy Data);
(b) Time of NTDC's System Peak Demand as Notified by NTDC (Active

Power);
(c) Time of Minimum NTDC Demand (Active Power) as Notified by NTDC;

and
(d) Preceding Year's Total NTDC Demand (Active Power) With Time of
System Peak with Respect to Each User's System Peak Demand (Active
Power)
PC.A4.3.2 Winter Peak- Load Readings and Forecast

A coincident set of measurements of MW and Mvar values both at 12.30 and
18.00 hours on the [day of the expected peak]
The readings should be taken with both the transmission and distribution
networks intact, and with normal sectionalising of the Distribution System, i.e.
under normal feeding conditions. The load reading shall take account of
embedded generation as detailed in section PC.A4.3.6.
NTDC's Load Forecast (System Peak Demand and Active Energy

Requirements)
(a) NTDC's Notification of its Forecasted Annual System Peak Demand

(Active Power)
(b) The Total Active Energy of the NTDC in the preceding NTDC Financial
Year along with a Forecasted Active Energy Requirements for the
Current Financial Year.
As follows:
A forecast of the expected MW and Mvar winter peak demand at the

Measurement Point at [xxxxxxx] for the next ten (10) years is required. For
example, the forecasts to be received by calendar week 9 of 2003 should
cover years 2003 through 2012. The load forecast shall take account of
sections PC.A4.3.6 through PC.A4.3.9 dealing with embedded generation,
description of forecast methodology, transformer reinforcements and
permanent load transfer.
The DSO, in preparing the forecast for winter peak load, shall bear in mind
that the coincident load readings taken on the second Thursday in December
may be lower than at system peak.
PC.A4.3.4 Minimum Demand - Load Reading and Forecast

A coincident set of measurements of MW and Mvar values at 06.00 hours on
the Sunday preceding the early August Monday Public Holiday is required.
55
The load readings shall take account of embedded generation as detailed in
section PC.A4.3.6.
NTDC's Load Forecast (System minimum Demand and Active

Energy Requirements)
a) NTDC's Notification of its Forecasted Annual System and Annual

Minimum Demand (Active Power);
As follows:
A corresponding 10-year forecast of the MW and Mvar minimum demand at
the Measurement Point in August at 06.00 hours for the next ten (10) years
is also required. For example, the forecasts to be received by calendar week
9 of 2003 should cover years 2003 through 2012. The load forecast shall take
account of sections PC.A3.3.6 through PC.A3.3.9 dealing with embedded
generation, description of forecast method, transformer reinforcements and
permanent load transfer.
PC.A4.3.5 Non Coincident Peak Demand - Load Reading and Forecast

Each User of the Transmission System who is a Demand Customer,
including the DSO, is required to specify by calendar week 9 of each year,
the MW and Mvar values corresponding to the maximum MVA demand which
occurred at the Measurement Point during the previous year. The date and
time of the occurrence of this maximum demand should be stated by the
User.
PC.A4.3.6 Embedded Generation
All load readings shall specify, separately, the MW and Mvar contribution from
significant embedded generation. The User should indicate whether the
generator is producing or absorbing Mvar from the system. The type or types
of significant embedded generation should be specified – hydro, wind, CHP,
biomass, diesel or other.
All load forecasts shall specify, separately, the installed capacity of existing
and projected significant embedded generation. Both MW and Mvar capability
should be given, indicating the Mvar limits both for production and
absorption. The type or types of embedded generation should be specified –
hydro, wind, CHP, biomass, diesel or other.
Load Forecast - Methodology

The User shall provide, with the forecast data, a brief description of the basis
for the forecast.
PC.A4.3.7 Load Forecast - Transformer Reinforcements

The User shall provide, with the forecast data, details of planned changes in
transformer capacity between the Measurement Point and the Connection
Point.
PC.A4.3.8 Load Forecast - Permanent Load Transfer

There are two separate characteristics of Distribution System load
forecasts; expected load growth and expected permanent load transfer
between infeeds from the Transmission System. In order to identify
separately the load growth, the DSO demand forecasts shall be prepared for
the load at each Measurement Point without taking account of any
proposed load transfers.
Then, in order to identify separately the proposed load transfer, the DSO shall
provide, with the forecast data, details of each planned load transfer as
follows:
56
(a) Date of transfer
(b) Reason for transfer e.g. proposed 110kV station, transformer

capacity, etc.
(c) MW and Mvar at each of the measurement points expected to be

transferred
(d) Existing source of supply for the load to be transferred.
Only proposed permanent load transfers for which there is a firm commitment
should be included. For example, proposed 110kV stations should be included
only where there is a connection agreement between the TSO and the DSO.
For a proposed new 110kV station which will supply new load and for which
there is a connection agreement between the TSO and the DSO, a load
forecast is required
PC.A4.3.9 Special Load Reading

The DSO shall continue to provide the TSO with the DSO special load
readings.
PC.A4.3.10 Data Templates

For uniformity of data capture, and to facilitate Users of the Transmission
System who are Demand Customers, the TSO will provide to each such
User prepared templates with data validation to facilitate entry of the
required data.
Users shall provide data to the TSO using these data templates or in such
other form as may be agreed by the TSO.
PC.A4.4 User Network Data

Single-line diagram of user network to a level of detail to be agreed with the TSO.
Electrical characteristics of all 132 kV circuits and equipment (R, X, B, R 0, X0, B0,)
continuous and overload ratings.
Contribution from User network to a three-phase short circuit at connection point.

Connection details of all 132 kV-connected transformers, shunt capacitors, shunt reactors
etc. (star, delta, zigzag, etc.)
Electrical characteristics of all 132kV circuits and equipment at a voltage lower than
132 kV that may form a closed tie between two connection points on the
Transmission System.
PC.A4.5 Standby Supply Data

For each User who is a Demand Customer, that can take supply from more than one
supply point, the following information is required:
Source of the standby supply (alternative supply point(s)) Standby capacity required (MW
and Mvar)
PC.A4.6 Fluctuating Loads

For each demand that can fluctuate by more than 5 MVA at the point of connection to the
Transmission System, the following information is required:
PC.A4.6.1 Rate of change of Active Power and Reactive Power, both increasing and
decreasing (kW/s. kvar/s).
PC.A4.6.2 The shortest repetitive time interval between fluctuations in Active Power
and Reactive Power Demand (Seconds).
57
PC.A4.6.3 The magnitude of the largest step changes in Active Power and Reactive
Power Demand (kW, Kvar).
PC.A4.7 Disturbing Loads

Description of any Disturbing Load to be connected to the Transmission System.
PC.A4.8 Grid Connected Transformer

Symbol Units
Number of windings
Vector Group
Rated current of each winding A
Transformer Rating MVATrans
Tapped winding
Transformer Ratio at all transformer taps
Transformer Impedance (resistance R and reactance X) at R+jX % on rating

all taps MVATrans
% on rating
For 3 winding transformers, where there are external Z HV:LV1
MVATrans
connections to all 3 windings, the impedance (resistance R ZHV:LV2
and reactance X) between each pair of windings is ZLV1:LV2
% on rating
required, measured with the third set of terminals open
circuit. MVATrans
% on rating
MVATrans
58
Transformer zero sequence impedances at nominal tap
Zero Phase Sequence impedance measured between the ZHT Ohm

HV terminals (shorted) and the neutral terminal, with 0
the LV terminals open circuit.
Zero Phase Sequence impedance measured between the ZHL Ohm

HV terminals (shorted) and the neutral terminal, with 0
the LV terminals short-circuited to the neutral.
Zero Phase Sequence impedance measured between the ZLT Ohm

LV terminals (shorted) and the neutral terminal, with 0
the HV terminals open circuit.
Zero Phase Sequence impedance measured between the ZLH Ohm

LV terminals (shorted) and the neutral terminal, with 0
the HV terminals short-circuited to the neutral.
Zero Phase Sequence leakage impedance measured ZL 0 Ohm

between the HV terminals (shorted) and the LV
terminals (shorted), with the Delta winding closed.
Earthing Arrangement including LV neutral earthing resistance & reactance
Open circuit characteristic Graph
59
PC.A4.9 Shunt Capacitor / Reactor Data
For each shunt capacitor or reactor with a rating in excess of 1 Mvar

connected to or capable of being connected to a user network, the following
information shall be provided.
PC.A4.9.1 Rating (Mvar).
PC.A4.9.2 Resistance / Reactance / Susceptance of all components of the

capacitor or reactor bank.
PC.A4.9.3 Fixed or switched.
PC.A4.9.4 If switched, control details (manual, time, load, voltage, etc.).
PC.A4.9.5 If automatic control, details of settings.
PC.A.5. Controllable Solar, Wind and ESPP (SWE) Data Requirements
All information for Controllable SWE connection applications shall include details of
the Transmission System Connection Point. This shall include details listed in
PC.A2.1, PC.A2.2 for the Connection Point. The minimum technical, design and
operational criteria to be met by Controllable SWE are specified in the Connection
Conditions.
PC.A 5.1 Wind Turbine Generators and Mains Excited Asynchronous Generators
State whether turbines are Fixed Speed or Variable Speed:
Provide manufacturer details on electrical characteristics and operating

performance with particular reference to Flicker and Harmonic performance.
For Mains Excited Asynchronous Generators, state:

Units
How the generator is run up to synchronous speed
Magnitude of inrush / starting current Amps
Duration of inrush / starting current ms
Starting / paralleling frequency Hz
Power factor on starting
Reactive power demand at zero output ('no load') kvar
Give details of reactive power compensation to be installed
PC.A 5.2 Wind Turbine Generators Parameters
Provide electrical parameters relative to the performance of the Wind Turbine

Generator. This may include but is not limited to parameters of electrical generator,
power electronic converters, electrical control and/or protection systems. Laplace
diagrams and associated parameters shall be provided to the TSO where appropriate.
PC. A 5.3 Mechanical parameters of the WTG
Provide mechanical parameters relative to the performance of the Wind Turbine

Generator. This may include but is not limited to the drive train characteristics of the
WTG, the stiffness of the shaft of the WTG and/or a multi-mass model of the WTG
60
components. Laplace diagrams and associated parameters shall be provided to the
TSO where appropriate.
PC.A 5.4 Aerodynamic performance of WTG
Provide details on the aerodynamic performance of the Wind Turbine Generator.

This may include but is not limited to variation of power co-efficient with tip speed
ratio and WTG blade pitch angle, aerodynamic disturbance from WTG tower, WTG
blade pitch control and high and low wind speed performance of the WTG. Laplace
diagrams and associated parameters shall be provided to the TSO where appropriate.
PC.A 5.5 Wind Turbine Generator transformer
Provide details of the transformer that connects the WTG with the internal
Controllable SWE network. This may include but is not limited to the rating of WTG
transformer (MVA or kVA), the WTG transformer voltage ratio (kV) or the WTG
transformer impedance (%).
PC.A 5.6 Reactive Compensation
Provide details of any additional reactive compensation devices and control systems
employed by the Controllable SWE. This shall include Mvar capability, the number
of stages in the device and the Mvar capability switched in each stage and any
control or protection systems that influence the performance of the Controllable
SWE at the Connection Point. Laplace diagrams and associated parameters shall be
provided to the TSO where appropriate.
PC.A 5.7 Controllable SWE control and protection systems
Provide details of any control or protection systems that affect the performance of the
Controllable SWE at the Connection Point. This shall include any systems or
modes of operation that activate during system Voltage or Frequency excursions
including Low Voltage Ride Through (FRT), High Voltage Ride Through, Low
Frequency Response and High Frequency Response. The transition between
Controllable SWE control modes shall also be specified. Laplace diagrams and
associated parameters shall be provided to the TSO where appropriate.
PC. A 5.8 Grid connection transformer of Controllable SWE

Provide details of the transformer that connects the Controllable SWE site with the
Distribution/Transmission System (equivalent to the Generator Transformer
of a conventional power station). This shall include but is not limited to rating of
grid transformer (MVA or kVA), transformer Voltage ratio (kV), transformer
impedance (%), transformer tap changing control and no-load losses.
PC. A 5.9 Internal network of Controllable SWE

Provide details of the Controllable SWE’s internal network structure (Collector
Network) and lay out (by means of a single-line diagram or other description of
connections). This shall include but is not limited to a breakdown of how the individual
WTGs are connected together as well as how they are connected back to the
Controllable SWE substation. Please specify different cable or overhead line types
and the individual length of each section of circuit.
Type1 Type2 Type3 Extend
Total length (m) Table as

appropriate
Conductor cross section area
per core (mm)
Conductor type (Al,

Cu, etc)
61
Type of insulation
Charging capacitance
(µF/km)
Charging current
(Ampere/km)
Positive sequence resistance
(R1 Ohm/km)
Positive sequence reactance (X1 Ohm/km)
PC. A 5.10 Flicker and harmonics
Provide details of harmonic or flicker contribution from the Controllable SWE that
may affect the performance of the Controllable SWE at the Connection Point. This
may include harmonic current injections and phase angles associated with the
Controllable SWE. Details of any additional AC filter devices shall also be provided
by the Controllable SWE to the TSO.
PC. A 5.11 Short Circuit Contribution
Provide details of the single-phase to ground, phase-phase and three-phase to ground

short circuit contribution from the Controllable SWE at the Connection Point. The
Controllable SWE shall provide the TSO with the single-phase and three- phase
short circuit contribution for rated conditions, i.e. maximum output from the
Controllable SWE with all WTGs and any additional devices in the Controllable
SWE contributing to the short circuit current. The Controllable SWE shall also
provide the single-phase to ground, phase-phase and three-phase to ground short
circuit contribution from an individual WTG. Signature plots of the short circuit
contribution from an individual WTG shall also be supplied by the Controllable SWE.
PC.A.6. Interconnector Data Requirements
Notwithstanding the Interconnectors Technical Code [], all information for

Interconnector connection applications shall include details of the Transmission
System Connection Point and external Transmission System Connection Point.
This shall include details listed in PC.A2.1, PC.A2.2 for each Connection Point. The
minimum technical, design and operational criteria to be met by Interconnectors
are specified in the Connection Conditions.
PC. A.6.1 Interconnector Operating Characteristics and Registered Data

(i) Interconnector Registered Capacity
(a) Interconnector Registered Import Capacity for import to the

Transmission System (MW);
(b) Interconnector Registered Export Capacity for export from the

Transmission System (MW).
Interconnector Registered Capacity figures (a) and (b) above shall

include transmission power losses for the Interconnector and be
considered Registered Data.
(ii) General Details
62
(a) single line diagram for each converter station;
(b) proposed Transmission connection point;
(c) Control Facility location;
(d) Interconnector Operator details.
(iii) Technology details where applicable
(a) Interconnector technology type (i.e. if AC or DC and, if

applicable, current or voltage source technology);
(b) AC/DC network cable or overhead line type & characteristics i.e.
length, resistance (R), reactance (X), susceptance (B);
(c) AC/DC rated DC Network Voltage/pole (kV);
(d) number of poles and pole arrangement;
(e) Earthing / return path arrangement;
(f) short circuit contribution (three phase to ground, single line to

ground, phase to phase);
(g) Interconnector losses (MW/Mvar);
• converter station;
• line circuits;
• house load demand;
• losses on de-block at minimum transfer;
• total losses at max import / export.
(h) overload capability including details of any limitations i.e. time,
temperature;
(iv) AC filter reactive compensation equipment parameters
(a) total number of AC filter banks;
(b) type of equipment (e.g. fixed or variable);
(c) single line diagram of filter arrangement and connections;
(d) Reactive Power rating for each AC filter bank, capacitor bank, or
operating range of each item or reactive compensation
equipment, at rated voltage;
(e) performance chart (PQ), showing Reactive Power capability of

the Interconnector, as a function of Interconnector Registered
Capacity transfer.
(f) harmonic and/or flicker contribution from the Interconnector

that may affect the performance of the Interconnector at the
Connection Point.
(v) Interconnector power electronic converter and control systems
(a) parameters related to the power electronic converters.
Interconnector converter characteristics to be represented
may include but is not limited by the following; converter firing
angle, modulation index, Valve winding voltage, DC Voltage, DC
Current as the output variables;
63
(b) transfer function block diagram representation including
parameters of the Interconnector transformer tap changer
control systems, including time delays;
(c) transfer function block diagram representation including
parameters of AC filter and reactive compensation equipment
control systems, including any time delays;
(d) transfer function block diagram representation including
parameters of any Frequency and/or load control systems;
(e) transfer function block diagram representation including
parameters of any small signal modulation controls such as
power oscillation damping controls or sub-synchronous
oscillation damping controls, which have not been submitted as
part of the above control system data;
(f) transfer block diagram representation including parameters of
the Active Power control, DC Voltage control, AC Voltage
control and Reactive Power control at converter ends for a
voltage source converter for both the rectifier and inverter
modes.
(g) transfer block diagram representation including parameters of
any control modes that affect the performance of the
Interconnector at the Connection Point which have not been
submitted as part of the above control system data. Features to
be represented shall include but are not limited to the following;
start-up sequence, shutdown sequence, Normal operating
mode, VSC control mode, Island mode and Emergency Power
control.
(vi) Interconnector Transformer;
Symbol Units
Number of windings
Vector Group
Rated current of each winding A
Transformer rating MVATrans
Tapped winding
Transformer ratio at all transformer taps

% on rating
Transformer impedance at all taps
MVATrans
Z0 Ohm
Transformer zero sequence impedance at nominal tap
Earthing arrangement including neutral Earthing resistance &

reactance

Graph
Open circuit characteristic
PC.A.7. Aggregators Data
64
For each Generator Aggregator, the following information shall be provided:
(i) Name of Generator Aggregator group;
(ii) Total Generation Capacity at their Connection Points of all Generation Units
being aggregated (MW) (Aggregated Maximum Export Capacity);
For each Generator Site within the Generator Aggregator group, the following
information shall be provided:
(i) Location;
(ii) Registered Capacity; and
(iii) Name of the Transmission Station to which the Generation Site is normally
connected.
For each Demand Side Unit Operator, the following information shall be provided:
(a) General Details
(i) name of Demand Side Unit;
(ii) address of the Demand Side Unit Control Facility;
(iii) address of each Individual Demand Site(s) comprising the

Demand Side Unit;
(iv) Irish Grid Co-ordinates of the Connection Point of each
Individual Demand Site comprising the Demand Side Unit;
(v) Meter Point Reference Number for each Individual Demand
Site
comprising the Demand Side Unit;
(vi) classification of operation of each Individual Demand Site
comprising the Demand Side Unit as one of:
 avoided Demand consumption only,
 combination of avoided Demand consumption and

Shaving Mode operation of Generation Units,
Continuous Parallel Mode operation of Generation
Units,
Lopping Mode operation of Generation Units,
1 For Three Winding Transformers the HV/LV1, HV/LV2 and LV1/LV2 impedances together with associated bases
shall be provided.
65
Standby Mode operation of Generation Units,
Automatic Mains Failure Mode operation of Generation
Units,
 Shaving Mode operation of Generation Units only,
 Continuous Parallel Mode operation of Generation Units

only,
 Lopping Mode operation of Generation Units only,
 Standby Mode operation of Generation Units only,
 Automatic Mains Failure Mode operation of Generation

Units
only;
(vii) current classification of operation of each Individual Demand Site
comprising the Demand Side Unit if different to above;
(viii) details of all Generation Units used as part of the Demand

Side Unit operated in Continuous Parallel Mode, Shaving
Mode or Lopping Mode, including the make, model,
Capacity, MVA rating, fuel type, and protection settings;
(ix) whether a change is required to the current Maximum Export
Capacity or Maximum Import Capacity of Individual
Demand Sites comprising the Demand Side Unit;
(x) whether the operation of Embedded Generator Interface
Protection trips a DSO-operated interface circuit breaker, DSO
Demand Customer main incomer, Generation Unit LV circuit
breaker, Generation Unit HV transformer circuit breaker or
other on a Distribution System-connected Individual
Demand Site comprising a Demand Side Unit containing
Generation;
(xi) the current operation Embedded Generator Interface
Protection if different to above;
(xii) details of all Demand loads with Demand reduction capability
of 5 MW or greater, including size in MW and demand reduction
capability from load;
(xiii) whether the Distribution System Operator has been
informed about the intention of the Demand Side Unit
Operator to operate a Demand Side Unit (the Demand Side
Unit Operator is obliged to inform the Distribution System
Operator);
(xiv) whether each Individual Demand Site comprising the
Demand Side Unit is currently participating as or part of any
Aggregated Generator Unit or other Demand Side Unit;
(xv) proposed effective date to Market Operator for first-time
applicants; and
(xvi) proposed date for Grid Code Testing.
(b) Technical Details
(i) total Demand Side Unit MW Capacity (MW) of the Demand
CC 66
Side Unit;
(ii) Demand Side Unit MW Capacity (MW) of each Individual
Demand Site comprising the Demand Side Unit;
(iii) total Demand Side Unit MW Capacity of the Demand Side
Unit available from on-site Generation (MW) operated in
Shaving Mode or Continuous Parallel Mode;
(iv) Demand Side Unit MW Capacity of each Individual
Demand Site comprising the Demand Side Unit available
from on-site Generation (MW) operated in Shaving Mode or
Continuous Parallel Mode;
(v) total Demand Side Unit MW Capacity of the Demand Side
Unit available from avoided Demand consumption (MW) and
on-site Generation (MW) operated in Lopping Mode and on-
site Generation (MW) operated in Standby Mode;
(vi) Demand Side Unit MW Capacity of each Individual
Demand Site comprising the Demand Side Unit available
from avoided Demand consumption (MW) or on-site
Generation (MW) operated in Lopping Mode or on-site
Generation (MW) operated in Standby Mode;
(vii) Demand Side Unit MW Response Time of the Demand Side Unit;
(viii) Demand Side Unit Notice Time of the Demand Side Unit;
(ix) Minimum Down Time of the Demand Side Unit;
(x) Maximum Down Time of the Demand Side Unit;
(xi) Minimum off time of the Demand Side Unit;

(xii) Maximum Ramp Up Rate of the Demand Side Unit;
(xiii) Maximum Ramp Down Rate of the Demand Side Unit;
PC A8 Modelling Requirements from Users
Introduction
The TSO requires suitable and accurate dynamic Models for all Users connected to, or
applying for a connection to, the Transmission System, in order to assess the impact of
the proposed installation on the transient and dynamic performance, and security and
stability of the Power System for a range of timeframes, disturbances and system
conditions. The TSO bases the safe and secure design and operation of the Power System
on the Models provided by the Users. All Users of the Power System shall provide
suitable Models of their Plant in a timeframe and manner specified by the TSO in this Grid
Code.
PC.A8.2 Model Capabilities

The Users shall supply Models that shall be capable of representing the behaviour of the
Plant in balanced root mean-square positive phase-sequence, time-domain studies and
where specified, electromagnetic transient and harmonic studies.
The balanced, root mean-square positive phase-sequence time-domain Model shall include
all material elements that affect the Active Power and Reactive Power output of the
Plant with respect to changes or excursions in Voltage and Frequency at the
Connection Point. The Model shall include all electrical and mechanical phenomena,
where applicable, that impact on the Active Power and Reactive Power output of the
Plant for sub-transient, transient and synchronous dynamics up to and including Primary
Operating Reserve and Secondary Operating Reserve timeframe.
CC 67
The three-phase electromagnetic transient Model shall include all material aspects of the
Plant that affect the symmetrical and asymmetrical voltage and current outputs from the
Plant. The Model shall represent phenomena that materially affect the Voltage and
Frequency at the Connection Point over timeframes of sub-cycles up to 500 cycles
including but not limited to switching of power electronic devices, transformer saturation or
equipment energisation.
PC.A8.2.1 Model Aggregation
The TSO requires the Model to represent the operation of the User’s Plant at
the Connection Point and therefore it is essential that the Models of
individual Generation Units can be aggregated into a smaller number of
Models, each representing a number of Generation Units at the same Site. If
all Generation Units in the User Site are not identical, the Model shall
account for this by accurately representing the overall performance of the
User’s Plant at the Connection Point. A representation of the collector
network and any additional equipment such as Reactive Power compensation
may be included in the aggregate Model of the User’s Plant. Models for the
simulation studies must be single lumped Models, scalable for different Active
Power outputs as seen at the Connection Point.
PC.A8.3 Model Documentation and Source Code
Users are obliged to provide appropriate balanced, root mean-square positive-phase

sequence time-domain Models and three-phase electromagnetic transient Models in
accordance with specifications in this Grid Code. The TSO requires that sufficient
information be provided by the User to allow for Models to be redeveloped in the event of
future software environment changes or version updates. All Models must be accompanied
with appropriate documentation with sufficient detail as specified by the TSO, such
agreement not to be unreasonably withheld. The User shall provide information including,
but not limited to, a full description of the Model structure and functionality, Laplace
diagrams or other suitably understandable information. The User may also choose to
provide the TSO with detailed Model source code. The Models shall be provided in a
software format as specified by the TSO. Alternatively, the User may provide an
unambiguous reference to a standard open-source Model, such as a standard IEEE Model,
or to a dynamic Model previously submitted to the TSO provided this Model accurately
reflects the User’s Plant.
The TSO may, when necessary to ensure the proper operation of its complete system
representation or to facilitate its understanding of the results of a dynamic simulation,
request additional information concerning the Model, this may include Model
documentation or the source code of one or more routines in the model. The User shall
comply with any such request without delay.
PC.A8.4 Confidentiality
The dynamic Models, supporting documentation and associated data are provided to the
TSO in order to carry out its duties to meet its statutory and legal requirements. In that
regard the TSO is entitled to share the information with third party consultants, other TSOs
or DSOs working for or with the TSO to perform coordinated operational and/or planning
studies.
Where the User or any other party, acting reasonably, designates such information as
confidential on the basis that it incorporates trade secrets, the obligation will be with the
TSO to ensure the confidentiality of data shared with other TSOs or DSOs working for or
with the TSO to perform co-ordinated operational and/or planning studies. Where such data
is shared with third party consultants working for or with the TSO such third party
consultants will be obliged to carry out any activities will be subject to stringent
confidentiality agreements.
CC 68
It is the responsibility of the User to provide the dynamic Models, supporting
documentation and associated data to the TSO. Where the User or any other party, acting
reasonably, designates such information as confidential on the basis that it incorporates
trade secrets, the TSO will accept the dynamic Models, supporting documentation and
associated data from a third party manufacturer provided the third party manufacturer
agrees to enter into the TSO’s standard confidentiality agreement for Users. In the event
that the manufacturer cannot agree to this confidentiality contract, the User shall be
responsible for the provision of the dynamic Models, supporting documentation and
associated data to the TSO.
PC.A8.5 Time to comply
The User shall provide a Model of the User’s Plant in accordance with PC.6.6.1. Where a
User requires reasonable time to develop the necessary Model or Models so as to comply
fully with all the provisions in this section, PC.A8.2 and PC.A8.3, the User may apply to
the TSO to be deemed compliant with the provisions of PC.A8.2 and PC.A8.3 on the basis
of GC.10.3 of the General Conditions of the Grid Code. The TSO shall consider any
such application in accordance with GC.10.3, and if the TSO is satisfied as to the User’s
programme for developing and testing the necessary dynamic model, the TSO may, for so
long as the TSO is so satisfied, treat the User as being in compliance with the provisions of
this section. If the TSO decides, acting reasonably, that it is not satisfied as to the User’s
programme for developing and testing the necessary dynamic Model and that the User
cannot be deemed to be in compliance with PC.A8.2 and PC.A8.3, the provisions of
GC.10.4 shall apply and the User shall apply for a derogation under the terms of GC.9.
PC.A8.6 Validation of Model
All Models provided to the TSO for use in dynamic simulations must be validated. The TSO
must be satisfied that the behaviour shown by the Model under simulated conditions is
representative of the behaviour of the real equipment under equivalent conditions.
For validation purposes the User shall ensure that appropriate tests are performed and
measurements taken to assess the validity of the dynamic Model. Where the validity of the
Model has not been confirmed prior to the commissioning of the User’s Plant, appropriate
tests shall be carried out and measurements taken at the User’s site to assess the validity
of the dynamic Model. The tests and measurements required shall be agreed between the
User and the TSO.
The User shall provide the TSO with all available information showing how the predicted
behaviour of the dynamic Model to be verified compares with the actual observed
behaviour of a prototype or production User System under laboratory conditions and/or
actual observed behaviour of the real User System as installed and connected to a
transmission or distribution network.
The User shall simulate the dynamic Models such that Model outputs can be compared
against measurements from Grid Code compliance testing to ensure appropriate
responses from the Model. Tests may include but are not limited to Steady State Reactive
Capability, Voltage Control & Reactive Power Stability, Low Voltage Ride Through (FRT),
High Voltage Ride Through, Low Frequency Response and High Frequency Response.
The tests and measurements required shall be agreed between the User and the TSO. The
TSO shall provide sufficient information on system conditions at the User’s Connection
Point to allow for the User to conduct their studies.
After commissioning, the User shall provide the TSO with documentation comparing the
predicted behaviour of the balanced, root mean square, positive phase- sequence time-
domain Model against the tested performance. If no significant changes are required to the
Model structure the TSO shall update the three-phase electromagnetic transient Model
based on the parameters submitted by the User provided the TSO has sufficient access to
update the relevant Model parameters. The TSO shall also perform studies and ongoing
validation to ensure that Models submitted by the User are representative of the User’s
Plant throughout its operational lifetime.
CC 69
If the on-site measurements, Grid Code compliance tests or other information provided
indicate that the dynamic Model is not valid in one or more respects, the User shall
provide the revised dynamic Model, source code and documentation whose behaviour
corresponds to the observed on-site behaviour as soon as reasonably practicable, but in any
case no longer than 90 Business Days after the conclusion of the Grid Code compliance
tests.
PC.A8.7 Maintenance of Model
All Models provided to the TSO must be maintained and updated to accurately reflect the
operational performance of the User’s Plant over the lifetime of the Plant. The User shall
inform the TSO of any changes to the Plant which may materially affect the accuracy of
the dynamic Model in predicting the Active Power and Reactive Power output of the
Plant with respect to changes or excursions in Voltage and Frequency at the
Connection Point. In this case the User shall re-submit the parameters associated to the
dynamic Model or fully re-submit the dynamic Model of the Plant. Changes which shall be
reported to the TSO may include but are not limited to alterations in Plant protection
settings, modifications to Plant controller settings and alterations to Governor Droop or
Plant Frequency response. In the event of scheduled Plant outages or maintenance the
User must provide appropriate Model updates in advance of the scheduled outage.
Updates of the dynamic Model version shall be supplied by the User to the TSO in a
timeframe agreed with the TSO.
The TSO is entitled to alter, modify and adjust Model parameters or data for the purposes
of better reflecting Plant behaviour with respect to observed operational performance over
the life of the Plant. The TSO shall inform the User of any Model changes prior to
implementing these in their System Models.
PC.A8.8 Software Environment and Model Usability
The User must provide Models in software packages as defined by the TSO. Details of the
current software version, computer platform, compiler version, and Model usability
guidelines, will be provided by the TSO upon request and shall be published on the TSO’s
website. The TSO may from time to time request that the Models be updated to be
compatible with changes in the TSO’s computing environment, namely software version
and/or compiler version. Each User shall ensure that such updated Models are provided
without undue delay or in any event, within 90 Business Days of the date of the request.
The User shall provide Models in the software formats as defined by the TSO, or
additionally in such other format as may be agreed between the User and the TSO.
Changes in the software format requirements for Models shall be subject to the Grid Code
revision process defined in GC.7.
All Models, irrespective of software format, shall be accompanied by a sample case such
that the Model can be tested before being integrated into the Model of the Irish network in
the respective software environment. The sample case shall include the User’s Plant
model, grid transformer and any other associated equipment connected to an infinite bus
via an impedance that is appropriate to represent the Connection Point.
CC 70
Appendix A- PART-3- STANDARD PLANNING DATA
Appendix B
The Single Line Diagrams showing the Details of the User's Connection to the NTDC Transmission
System are included in the Appendix E of the Connection Code.
End of PC
CC 71
CONNECTION CODE
CONTENTS
CC 1 INTRODUCTION
CC 2 PURPOSE AND AIMS
CC 3 TRANSMISSION STATION COMPOUND
CC 4 PLANT DESIGNATION
CC 5 RELEVANT TECHNICAL STANDARDS APPLYING TO USER PLANT AND APPARATUS
CC 6 SPECIFIC DESIGN AND PERFORMANCE STANDARDS
CC 7 TRANSMISSION SYSTEM PERFORMANCE
CC 8 USER PROTECTION AND POWER QUALITY
CC 9 COMMUNICATION FACILITIES
CC 10 SIGNALS TO BE PROVIDED BY USERS
CC 11 POWER SUPPLIES
CC 12 RESPONSIBILITY FOR SAFETY
CC 13 COMMISSIONING AND NOTIFICATION
APPENDIX A OF CONNECTION CODE: LIST OF MINIMUM REQUIREMENTS FOR POWER SYSTEM AND
APPARATUS CONNECTED TO THE TRANSMISSION, DISTRIBUTION, PROVINCIAL AND
SPTLS SYSTEMS
APPENDIX B OF CONNECTION CODE: FORMAT, PRINCIPLES AND PROCEDURES TO BE USED IN THE

PREPARATION SITE RESPONSIBILITY SCHEDULES (SRS)
APPENDIX C OF CONNECTION CODE (ATTACHMENT) PROFORMA FOR SITE RESPONSIBILITY

SCHEDULE (SRS)
APPENDIX D OF CONNECTION CODE (PART-I) PRINCIPLES AND PROCEDURES RELATING TO

OPERATION DIAGRAMS
APPENDIX E OF CONNECTION CODE (PART-II) PRINCIPLES AND PROCEDURES RELATING TO GAS

ZONE DIAGRAMS
APPENDIX F OF CONNECTION CODE (PART-III)
APPENDIX G OF CONNECTION CODE: MINIMUM FREQUENCY RESPONSE REQUIREMENTS SCOPE
APPENDIX H OF CONNECTION CODE: TECHNICAL REQUIREMENTS FOR LOW FREQUENCY RELAYS

FOR THE AUTOMATIC LOAD SHEDDING
APPENDIX J: SCHEME 1: INTERCONNECTION CONFIGURATIONS FOR GENERATORS (CONNECTIONS

AT 11 KV)
CC 72
ANNEXURE E: SCHEME 2: INTERCONNECTION CONFIGURATIONS FOR GENERATORS
(CONNECTIONS AT 66 KV)

(CONNECTIONS AT 132 KV)

(CONNECTIONS AT 220KV AND 500KV)
Annexure F: Figure-1: CONNECTION PROCEDURE FOR NEW CONNECTION OR MODIFICATION OF EXISTING
CONNECTION
CC 73
CONNECTION CODE
CC 1 INTRODUCTION
For the protection of the Transmission System and Users’ Plant and Apparatus directly
connected to the Transmission System, and in order to maintain, insofar as is possible by
Good Industry Practice, stable and secure operation of the Transmission System for the
benefit of all Users, it is necessary to require certain minimum technical, design and
operational criteria to be met by Users’ Plant and Apparatus.
CC 1.1 The System operator shall in good faith negotiate a Connection

Agreement with the Entity requesting a Connection Agreement with the
National Transmission System in accordance with the provisions of
Transmission Licence of the System Operator. The Connection Code
establishes the conditions, principles, Standards and method of connection, Plant
and Apparatus designation and nomenclature, technical standards, performance
standards, data requirements; they altogether define the minimum technical design
criteria and connection requirements to which the Users/Code Participants must be
complied when connected to or when seeking for connection with the National
power transmission system.
CC 1.2 These Connection Conditions supply information as to the performance
characteristics of the Transmission System at the Connection Point, in order to
enable Users and prospective Users to design their Plant and Apparatus and to
provide appropriate control systems and Plant protection schemes.
CC 1.3 The CC also details the application procedure to be adopted by the applicants and
prospective Code Participants and the obligations to be fulfilled by Network
Owner/System Operator in the capacity of System Operator to arrange and provide
connections. The system Operator shall approve the connection applications.
applies to all NTDC Transmission System Users, i.e.:
l) NTDC;
m) All Generators connected at the Transmission system
n) Generators with capacity greater than 10 MW;
o) DISCOs;
p) Transmission-connected Consumers; and
q) Externally Connected Consumers/Parties, like
16. Aggregators
For avoidance of doubt, the above categories of User will become bound by the Planning Code
prior to generating, distributing or consuming electricity, as the case may be, and references to
the various categories (or to the general category) of User should, therefore, be taken as referring
both to a prospective User in that role or to Users actually connected.
CC 74
CC 2 PURPOSE AND AIMS
CC 2.1 The Connection Code provides the framework for connection to the National
Transmission System, and It has primarily the following aims:
(a)to define the normal Transmission System performance standards at the

Connection Point.
(b) to define the uniform principles and guidelines and the minimum standards for
the method of connection to and use of the Transmission System ;
(c) to establish a process to be followed by a prospective Code Participant to
establish or modify a connection to the National Transmission System;
(d) to manage and prepare the System and the Point of Connection for the
applicant seeking connection to the present and future Transmission System;
for instance to outline the types of signals and indications that will be required to be
made available to the SO by each User.
(e)to identify technical design and operational standards which must be complied
with by any User connecting to the Transmission System.
(f) Identify the financial requirements of the connection.
(g) To detail requirements for the designation and nomenclature of all User Plant and
Apparatus connected to the Transmission System.
CC 2.2 The Connection Conditions PRINCIPLES
The conditions and the procedures covered under this Connection Code are based
on, among others, the following principles and conditions:
(a) All prospective Users and applicants shall have an opportunity to form a new
connection to the network, and have access to the services provided by the
System Operator;
(b) The terms and conditions on which connection to the National Transmission
System and provision of network services is to be granted are to be set out in
the Connection Agreement between the System Operator and applicants;
(c) A uniform treatment shall be applied by the System Operator in identifying
terms and conditions for new connection for each applicant; and
(d) Same principles shall hold while modifying an existing connection for the Code
Participants along with Annual System Reliability and Assessment Report
(ASRA).
CC 2.3 Disconnection and reconnection
Alongside the Connection, in case of any circumstance, the User Power Plants and
Apparatus may experience disconnection and reconnection which principles and
procedure shall also be regulated. The following procedures must be adopted for
disconnection of any facility from the National Transmission System.
CC 2.4 Voluntary disconnection
For the voluntary disconnection of any equipment or the facility, the Code
Participant must give advance notice, as established in the Connection
Agreement, in writing, that it intends to disconnect its facility from National
Transmission System, subject to the procedures set out in its Connection
Agreement.
However, it should be ensured that disconnection and reconnection procedures are

made an integral part of the Connection Agreement.
CC 75
Before taking any decision for disconnection of the equipment of the facility, of the
Code Participant, the System Operator shall ensure that such disconnection will
have no impact on the quality or reliability of supply or Systems of other Code
Participants.
Prior to any disconnection, the System Operator shall inform NEPRA about the
disconnection proposal and its expected impact on the network.
All the costs incurred on disconnection of equipment or facility from the network will
be borne by the Code Participant who is seeking the disconnection.
CC 2.5 Involuntary disconnection
The System Operator may disconnect Equipment, Apparatus, or the Facility of a

Code Participant by giving an advance notice in the case of only as per Connection
Agreement if:
The Code Participant is not operating its facility in accordance with the Connection
Agreement or in accord a nee with the law of the land or in accordance with the
NEPRA licence, and other applicable documents.
(a) In case of operational emergencies, where national transmission system

becomes incapable of providing the required services.
(b) In the event of emergencies, the Code Participant's facility must be

disconnected in an orderly manner or as indicated in the Connection
Agreement, such that the security and integrity of the System is not
jeopardized.
(c) In the event of emergencies, the Code Participant's facility must be

disconnected in an orderly manner or as indicated in the Connection
Agreement, such that the security and integrity of the System is not
jeopardized.
In the event of involuntary disconnection, the affected Code Participant must not
bring proceedings against the System Operator to seek to recover any amount for
loss or damage incurred due to the disconnection.
CC 2.6 Reconnection of equipment or facility
The System Operator shall reconnect the Code Participant's facility, equipment, and
apparatus after confirming that:
(a) The Code Participant has rectified all such circumstances, which were the
cause of disconnection; and the System Operator has agreed and reasonably
satisfied with the corrected status of the Code Participant's facility.
(b) the System Operator shall charge such cost as indicated in the Connection
Agreement for reconnection of the facility which was disconnected due to
default.
(c) The facilities, which were disconnected due to emergencies, must be

reconnected as soon as the causes of emergencies were rectified and
National Transmission System has come in steady-state operational
conditions.
CC 2.7 Operational obligations of code participants
All Code Participants must maintain and operate their facilities in accordance with,
but not limited to the following provisions;
(a) Abide by the relevant laws, rules and regulations.
CC 76
(b) Abide by the obligations under Grid Code and Distribution Code (if applicable).
(c) Adopt the prudent electric power industry practices and applicable standards
enumerated in other rules, regulations and guidelines of NEPRA.
(d) Coordinate with the System Operator in activities relating to operation,

maintenance and development of the National Transmission System.
(e) Abide to the conditions set out in the Connection Agreement so that the
Quality of Supply (QoS), and security of the National Transmission System,
and Systems of other Code Participants are not affected.
(f) Utmost care must be observed by the Code Participant in preparation and
submission of technical data and other information required by the System
Operator for planning and development, and day to day operation of the
National Transmission System.
(g) The Code Participant must maintain the Quality of Supply (QoS) and technical
standards set out for the Point of Connections as detailed in the System
Operator Licence, Grid Code, Distribution Code, and other applicable
documents of NEPRA.
(h) The Code Participant must register itself with NEPRA as a licensee to operate
as a Generator, Distribution Company, Interconnection company SPTL or
another Network Operator.
(i) The Code Participants should coordinate with the System Operator and
prepare a program with committed implementation schedule to install SCADA
(online data acquisition and monitoring facilities) on its system and requisite
metering facilities.
(j) Inform the System Operator of any real-time sudden changes on their own
System as soon as possible.
CC 2.8 Maintenance and Replacement of Interconnecting Facilities due to

Aging/damage
The System Operator or the distribution, Provincial & SPTLs companies, as the case
may be, who owns the assets at the Point of Connection shall carry out the
maintenance of the equipment, including the equipment used for connection. All
the costs incurred in this respect shall be borne by the owner of the assets.
The replacement of equipment due to aging shall be the responsibility of the

System Operator or the distribution company, as the case may be, who owns the
assets at the Point of Connection.
CC 2.9 SCADA and SCADA Communications System
The SCADA and SCADA communication system shall be used by System Operator
and Code Participants to monitor and control the NTDC Transmission System,
including 1100 kV, 765 kV, 500 kV and 220 kV grid stations, portions of 132 kV
substations, and to dispatch Generators connected to the National Transmission
System . The SCADA system shall also include data from Generators, and other
Code Participant facilities as required by the System Operator. SCADA is further
elaborated in the Operation Code.
CC 3 TRANSMISSION STATION COMPOUND

The User shall provide a Transmission Station compound, as provided for in the Connection
Agreement, immediately adjacent to the User's facility and otherwise acceptable to the SO
CC 77
for the erection of a Transmission Station, as necessary, for the SO and for installing other
equipment required for connecting the User's System to the Transmission System.
CC 3.1 Connection to the Transmission System must meet the standards defined in the
Planning Code and in these Connection Conditions. The method of connection use
may exceed the standards where this is required by the User and is acceptable to
the SO.
CC 4 PLANT DESIGNATION
CC 4.1 The name of the User Site shall be designated by the User and subsequently
agreed with the TSO, such agreement not to be unreasonably withheld.
CC 4.2 The designation and proposed nomenclature of User Plant and Apparatus
connected to the Transmission System shall be in accordance with the SO standard
practice which, in particular, is designed to ensure that designation and
nomenclature avoids confusion. The User shall notify the designation and proposed
nomenclature of Users’ Plant and/or Apparatus to the SO who may, if the SO
determines that such proposed designation may lead to confusion or does not
conform with the SO standard practice, notify substitute designation which shall
apply to such User Plant and/or Apparatus.
CC 4.3 The SO's standard practice currently requires that, unless otherwise agreed with
the SO, the following standard designations apply:
(a) Generating Units: for hydro, Solar and wind: G1, G2 etc. for
thermal: U1, U2 etc.
(b) Interconnectors: for: I1, I2 etc
(c) Demand Side Units for: DSU
(d) Energy Storage Units for: ESU
(e) Generator transformers and
Interconnector Transformers: at 765 kV; T7001, T7002…
at 500 kV; T5001, T5002 etc. (i.e. Transformers for at 220 kV;
T2001, T2002 etc. Generating Unit production) at 132 kV;
T1001, T1002 etc.
(f) Power Station transformers: at 765 kV; ST7001, ST7002
at 500 kV; ST5001, ST5002 etc. (i.e. dedicated transformers at 220 kV;
ST2001, ST2002 etc. supplying both the Generation at 132 kV; ST1001,
ST1002 etc.
Unit and the Power Station auxiliaries from the HV busbar)
(g) Unit Transformers: UT1, UT2 etc. (i.e. transformers supplying
auxiliaries of a Generating Unit)
(h) Load transformers: for 765/110 kV; T7101, T7102
For 765/220 kV; T7201, T7202
for 500/132 kV; T5101, T5102 etc. for
220/132 kV; T2101, T2102 etc. for
132/38kV; T141, T142 etc.
for 132/20kV; T121, T122 etc.
for 132/11kV and below; T101, T102 etc.
(i) Bus sections, conventional busbars: single bus; A1, A2 etc.

double bus; A1, A2, B1, B2 etc.
(j) Bus sections, ring busbars: each section identified by

designation of Plant and/or
Apparatus item connected to it.
(k) Bus Couplers: K1, K2 etc.
CC 78
(l) Lines and cables: each line or cable at a station identified
by name of station or stations at the
remote end or ends of the line or cable in
alphabetical order.
(m) Circuit Breakers CB.
(n) Main Earth Disconnects DE.
(o) Line Disconnect DL.

(p) Busbar Disconnects DA, DB, etc.
(q) Coupler Disconnects DA, DB, etc.
CC 4.4 CC.5.4 Every User shall be responsible for the provision, erection and maintenance
of clear and unambiguous labelling showing the designation and nomenclature of
its Plant and Apparatus at the User Site.
CC 5 RELEVANT TECHNICAL STANDARDS APPLYING TO USER PLANT AND APPARATUS
CC 5.1 All User Plant and Apparatus associated with the connection to the Transmission
System shall comply with the:
(a) Electric Power Act, 1997 and
(b) the relevant Pakistan Electrotechnical standards; or
(c) if there is no relevant Pakistan Electric standards, such other

International Electricity relevant standard issued by International
Electrotechnical Commission (IEC) and which is in common use in the
Electricity Sector by Utilities;
in each case as current at the date of the User's applicable Connection
Agreement. Where the SO, acting reasonably, determines that in order to
ensure safe and co-ordinated operation of a User’s Plant and/or Apparatus
with the Transmission System, there is a requirement for supplemental
specifications and/or standards to apply to the design of a User’s Plant and/or
Apparatus, the SO shall notify the User and the User shall comply with the
additional requirements. On request from the User, the SO shall provide
reasonable evidence as necessary to demonstrate the need for the
supplemental specifications and/or standards.
CC.6.2 In the event that any standard or specification with which a User's Plant and/or
Apparatus is required to comply under PC.6.1 is amended, the SO will, having
consulted with the affected Users and with the Grid Code Review Panel, make a
recommendation to the NEPRA as to what action should be taken.
CC 6 SPECIFIC DESIGN AND PERFORMANCE STANDARDS
CC 6.1 In order to facilitate secure and stable operation of the Transmission System for the
benefit of all Users, it is necessary that Users’ Plant and Apparatus is designed to be
capable of sustained operation within a range of Transmission System conditions.
CC 6.2 All Users

CC 6.2.1 Earthing
(a) The Earthing of all Users Plant and Apparatus and provision of an
Earthing system shall as a minimum requirement be in accordance with
the recommendations contained in the “Guide for Safety in Alternating
Current Substations”, ANSI/IEEE No. 80, 1986.
CC 79
(b) Earth Fault Factor: For connections to the Grid at all nominal system
voltages, the Grid is solidly earthed with specified earth fault factor below
1.4 (Refer to IEC Standard 60071-2 “Insulation Coordination”)
(c) The SO shall consult with each User regarding the specification for the
Earthing grid to be provided.
(d) Each User’s earth disconnects must be earthed directly to the main station
earth grid.
(e) The User will be obliged to certify (by a competent body) that remote
earths have been isolated from the User's site plus any other affected third
parties’ sites and that adequate precautions shall be taken by the User to
ensure that dangerous grid potential rises are not transferred outside the
Earthing zone. The Transmission Station cannot be energised until this
certification has been received by the TSO.
(f) Each User’s Earthing system shall be bonded to the Transmission Station
earth grid so that both Earthing systems are effectively integrated.
(g) Each User shall ensure that all staff working on the User’s Earthing system
shall be adequately trained to perform such work in a safe manner
CC 6.2.2 Design
a. User Plant and Apparatus shall be designed with the following

minimum capabilities (at the applicable Voltage levels), see Table1-1:
Table1-1. Reference maximum withstand Voltages

Parameter (Minimum) 132kV 220kV 500kV 765kV 1100kV
Insulation Level (kV);
- Lightning Impulse (1.2/50 550 1050 1550 2100 2100

sec.) - -
230 460 1175 1550 1550
- Switching Impulse (0.25/2.5
ms) - - -
- Power Frequency (50 Hz, for

1 min)
Clearance outdoor in air of live metal 1100 2400 4100 4100 4100
parts (mm) phase to earth
Height of live parts above pedestrian 3400 4700 6400 6400 6400
passageways (mm)
Height of bottom of unscreened 2300 2300 2300 2300 2300

live bushings above ground (mm)
Height of live conductors above 8000 9000 10500 10500 10500

roadways (mm)
b. User Plant and Apparatus shall be designed with the following

minimum capabilities (at the applicable Voltage levels),
c. User Plant and Apparatus at the Connection Point shall be

designed taking account of the short circuit current levels specified in
CC 80
CC.8.6. User circuit breakers shall be capable of safely making and
interrupting currents due to faults, taking account of the current levels
specified in CC.8.6. Circuit breakers with a higher rating than the
current levels specified in CC.8.6 may be necessary for a number of
reasons, including, but not limited to the need to provide an adequate
safety margin or to cater for a high DC component in the fault current.
It shall be the responsibility of the User to determine, what safety
margin if any to apply when selecting the User’s Plant and Apparatus.
CC 6.2.3 LV cables and wiring
(a) All multi-core control and protection cables shall be provided with a
suitable metallic screen. Facilities for Earthing these screens at the base
of cabinets shall be provided.
(b) LV supply cable and auxiliary wiring shall be routed from the
Transmission Station to each User’s control building through a mutually
agreed cable corridor. The cables will be laid in concrete troughs with
reinforced concrete covers, or as mutually agreed, to the User’s
marshalling rack, which will be situated near the Transmission Station.
CC 6.2.4 Locking
(a) The facility to lock in the open/closed position and interlocking facilities
shall be provided by each User on appropriate disconnects and/or
circuit breakers (with withdraw facilities) in order to ensure that the
incoming feeder(s) to the facility can be safely isolated when required by
the SO. The specific details of this requirement will be outlined at the
design phase.
(b) Existing Power Stations with Power Generation Electrical Safety Rules
other than NTDC Rules, in accordance with OC11, in operation will be
deemed to comply with CC.7.2.4.1 subject to review by the SO.
CC 6.2.5 Grid Connected Transformers
(a) Generators shall provide on-load tap-changing (OLTC) facilities for all
Generator Transformers. Demand Customers are advised to provide
on-load-tap-changing (OLTC) facilities for all Grid Connected
Transformers. All Users shall liaise with the SO on the design
specification for the performance of the tap-changing facility on Grid
Connected Transformers.
(b) Where the SO specifies the use of blocking of OLTC, the Grid Connected
Transformers at Distribution Facilities shall be capable of automatic or
manual OLTC blocking. The SO will specify the automatic OLTC blocking
functional capability.
(c) Generator Transformer windings shall be connected in star (with the
star point or neutral brought out) on the higher Voltage side and in delta
on the lower Voltage side.
(d) Other Grid Connected Transformers may be connected either:
(i) in delta on the lower voltage side and in star (with the star point or
neutral brought out) on the higher Voltage side; or
(ii) in star on both higher and lower Voltage sides with a delta tertiary
winding provided.
CC 81
(e) Demand Customers and Generators are advised that provision
should be made for the Earthing of the neutral of each of their
Transformers connected to the 132kV or 220kV System as the case may
be, by bringing out the neutral and ensuring that the insulation is such
that the Transformers can be operated unearthed.
(f) The SO will consider on a case by case basis the required treatment of
the 132kV or 220kV System neutral connection of these Transformers.
the 132kV or 220kV System neutral earth switch may be required to be
installed in specific instances and Demand Customers or Generators, as
applicable, will be advised of this at the time of the Connection Offer.
The SO will be responsible for the status of the 132kV or 220kV System
neutral earth switch on these Transformers. For the avoidance of doubt,
this clause does not apply to Transformers located at the TSO-DISCOs,
Provincial and SPTL Companies, boundary where such issues are
agreed between the SO and DISCOs, Provincial and SPTL Companies.
(g) The HV neutrals of all Transformers connected to the 500 kV System and
above should be solidly earthed. The capability of being operated
unearthed is unnecessary.
(h) The SO will provide the facility for the tripping of Grid Connected
Transformer HV circuit breakers from the User’s transformer protection.
(i) An Interconnector Transformer shall be designed such that the
Reactive Power capability is possible over the full range of Transmission
System Voltages (specified in Voltage table) The SO and an
Interconnector owner will liaise on matters related to the Interconnector
Transformer at the design stage.
(j) Interconnector Transformer windings shall be connected in star (with the
star point or neutral brought out) on the higher Voltage side and in delta
on the lower Voltage side or as agreed with the SO.
CC 6.3 Generators
CC 6.3.1 The conditions specified in this section of the code apply to all Generating
Units connected to or connecting to the Transmission System. Unless
explicitly stated all conditions specified apply over the full operating
capabilities of the Generating Unit at the Connection Point. For all
Generating Units where Secondary Fuel Registered Capacity is different
than Primary Fuel Registered Capacity all appropriate Connection
Conditions must be met or agreed with the SO.
CC 6.3.2 Provided the limitation described in Addenda 1, 2 and 3, are taken into
account, each Generating Unit, shall, as a minimum, have the following
capabilities:
(a) operate continuously at normal rated output at Transmission
System Frequencies in the range 49.8Hz to 50.2Hz;
(b) remain synchronised to the Transmission System at Transmission
System Frequencies within the range 47.5Hz to 52.0Hz for a
duration of 60 minutes;
(c) remain synchronised to the Transmission System at Transmission
duration of 20 seconds;
(d) required each time the Frequency is below 47.5Hz;
(e) Remain synchronised to the Transmission System during rate of
change of Transmission System Frequency (ROCOF) of values up to
and including 0.5 Hz per second;
(f) remain synchronised to the Transmission System for a Rate of Change
of Frequency up to and including 1 Hz per second as measured over a
CC 82
rolling 500 milliseconds period. Voltage dips may cause localised Rate
of Change of Frequency values in excess of 1 Hz per second for short
periods, and in these cases, the Fault-Ride Through clause
CC.7.3.1.1(y) supersedes this clause (CC.7.3.1.1(d)). For the avoidance
of doubt, this requirement relates to the capabilities of Generating
Units only and does not impose the need for Rate of Change of
Frequency protection nor does it impose a specific setting for anti-
islanding or loss-of-mains protection relays;
(g) sustained operation at the specified Minimum Generation within the
range 49.8 to 51.0 Hz;
(h) remain synchronised to the Transmission System at normal rated
output at Transmission System Voltages within the ranges specified in
CC.8.3.2 for step changes in Transmission System Voltage of up to
10%.
(i) sustained operation in accordance with the Reactive Power capability
as required by CC.7.3.6 at Transmission System Voltages within the
ranges specified in CC.8.3.2, unless otherwise specified;
(j) remain synchronised during and following any Fault Disturbance
anywhere on the Power System which could result in Voltage dips at
the HV terminals of the Generator Transformer of no greater than 95%
of nominal Voltage (5% retained) for fault durations up to and
including the Fault Ride-Through Times as defined in the table
below and Voltage dips of no greater than 50% of nominal
Voltage (i.e. 50% retained) for fault durations up to and including the
Fault Ride-Through Times as defined in the table below (see also
Fault Ride-Through Envelopes below). Following the fault clearance the
Generating Unit should return to pre-fault conditions subject to its
normal Governor Control System and Automatic Voltage Regulator
response. The use of Extraordinary Governor Response and/or
Extraordinary AVR Response to remain synchronised during and
following a fault is prohibited unless specifically agreed with the SO,
such agreement not to be unreasonably withheld
VOLTAGE DI Fault Ride Through Times

MAGNITUDE
132 kV 220 kV 500 kV 765 kV 1100 kV
System System System System System
0% retained 300 300 300 300 300
50% retained 450 450 450 450 450
Fault Ride-Through Envelopes

For avoidance of doubt, the Generator shall stay connected for voltage within the shaded areas;
depending on the retained voltages of 0% or 50% the Must-stay-connected areas are the pink or
the blue, see Figure-3.2 Fault-Ride Through envelope
CC 83
100%
(% of Pre-fault) C2
Voltage
50%
C1
0%
300 450 Time (ms)
Figure-3.2 Fault-Ride Through envelope
(k) remain synchronised during and following any Fault Disturbance

anywhere on the Power System
(l) remain synchronised to the Transmission System during a negative
phase sequence load unbalance in accordance with IEC 60034-1.
(m) The short circuit ratio of each Generating Unit shall be in accordance
with IEC 60034-1.
(n) Minimum Load not greater than 50% of Registered Capacity for CCGT
Installations and not greater than 35% of Registered Capacity for all
other Generating Units. For CCGT Installations whilst operating in
Open Cycle Mode as a result of combined cycle plant capability being
unavailable, the Minimum Load of each Combustion Turbine Unit must
be not greater than 35% of the Registered Capacity divided by the
number of Combustion Turbine Units.
(o) Ramp up capability not less than 1.5% of Registered Capacity per
minute when the Unit is in the Normal Dispatch Condition.
(p) Ramp down capability not less than 1.5% of Registered Capacity per
minute when the Unit is in the Normal Dispatch Condition
(q) Minimum up-time not greater than 4 hours for Thermal Units.
(r) Minimum down-time not greater than 4 hours for Thermal Units.
(s) Forbidden Zones within the range between normal Minimum Load plus
5% and Registered Capacity less 10%, not more than 2 specified zones
each not greater than 10% of Registered Capacity
(t) Block Loading not greater than 10% of Registered Capacity.
(u) Time off-load before going into longer standby conditions remain in a
hot condition for at least 12 hours and remain in a warm condition for
at least 60 hours.
(v) Time to Synchronise from instruction: hot: not greater than 3 hours
warm: not greater than 8

hour cold: not greater than
12 hours
(a) Time from Synchronising to Minimum Load:
hot: not greater than 40 minutes warm: not greater than

90 minutes cold: not greater than 180 minutes
CC 84
(b) Time to de-load from Minimum Load to De- Synchronising:
not greater than 40 minutes, except where agreed with the

TSO.
(w) Operating Reserve (OC.6.4)
(i) Primary Operating Reserve (POR): not less than 5%

Registered Capacity to be provided, at a minimum, at MW
Outputs in the range from 50% to 95% Registered
Capacity, with provision in the range of 95% to 100%
Registered Capacity to be not less than that indicated by a
straight line with unity decay from 5% of Registered
Capacity at 95% output to 0 at 100% output.
(ii) Secondary Operating Reserve(SOR) not less than 5%
Outputs in the range from 50% to 95% Registered Capacity,
with provision in the range of 95% to 100% Registered Capacity
to be not less than that indicated by a straight line with unity
decay from 5% of Registered Capacity at 95% output to 0 at
100% output
(iii) Tertiary Operating Reserve band 1 (TOR1) not less than 8%
with provision in the range of 92% to 100% Registered
Capacity to be not less than that indicated by a straight line with
unity decay from 8% of Registered Capacity at 92% output to 0 at
100% output
(iv)Tertiary Operating Reserve band 2 (TOR2) not less than 10%

with provision in the range of 90% to 100% Registered Capacity
to be not less than that indicated by a straight line with unity decay
from 10% of Registered Capacity at 90% output to 0 at 100%
output.
(x) The SO may request Generating Units of Registered Capacity
greater than or equal to xxMW to have the capacity to operate
under AGC at all loads between AGC Minimum Load and AGC
Maximum Load.
(y) Remain synchronised to the Transmission System and operate within
the frequency ranges and time periods specified in Table 1-2
(z) Remain synchronised to the Transmission System and operate within
the ranges of the Transmission System Voltage at the connection
point, for an unlimited time period, as specified in Table 1-3.
(aa) Remain synchronised to the Transmission System and continue to
operate stably during and following any Fault Disturbance anywhere
on the Power System which could result in Voltage Dips at the
Connection Point. The voltage-against-time profile specifies the
required capability as a function of voltage and Fault Ride-Through
Time at the Connection Point before, during and after the Fault
Disturbance. That capability shall be in accordance with the voltage-
against-time profile as specified in Figure1-4.
Table 1-2.Minimum Time Periods to remain connected in Operation
Frequency Range Time Period
47 – 47.5 Hz 20 seconds
CC 85
47.5 – 48.5 Hz 90 minutes
48.5 – 49 Hz 90 minutes
49 – 51 Hz Unlimited
51 – 51.5 Hz 90 minutes
51.5 – 52 Hz 60 minutes
Table 1-3. Voltage Range to stay connected

Voltage Voltage Range (p.u.)
1100 0.9 - 1.05
765 kV 0.9 - 1.05
500 kV 0.9 - 1.05
220 kV 198 kV to 245 0.9 -
kV 1.114
132 kV 118.8 to 147 kV 0.9 -
1.118
(450, 50% )
100%
(% of Pre-fault)
Voltage
(300, 50% )
(450, 50% )
50%
0% (300, 0% )
300 450 Time (ms)
Figure1-4. Voltage and connections in fault conditions
Following the fault clearance the Generating Unit should return to pre-
fault conditions subject to its normal Governor Control System and
Automatic Voltage Regulator response. The use of Extraordinary
Governor Response and/or Extraordinary AVR Response to remain
synchronised during and following a fault is prohibited unless
specifically agreed with the TSO, such agreement is not unreasonably
withheld.
(bb) Capable of disconnecting automatically from the Transmission
System in order to help preserve system security or to prevent
damage to the Generating Unit. The Generator and the SO shall agree
on the criteria for detecting loss of angular stability or loss of control.
(cc)Enter into an agreement with the SO regarding technical capabilities of
the Generating Units to aid angular stability under fault conditions.
CC 86
(dd) Equipped with a facility to provide fault recording and monitoring of
dynamic system behaviour. This facility shall record the following
parameters:
— voltage;
— active power;
— reactive power; and
— frequency.
The SO will specify the quality of supply parameters for fault recording and
monitoring of dynamic system behaviour. The settings of the fault recording
equipment and the communications protocols for the recorded data shall be
agreed between the Generator and the SO. The dynamic system
behaviour monitoring shall include an oscillation trigger specified by the
TSO, with the purpose of detecting poorly damped power oscillations. The
facilities for quality of supply and dynamic system behaviour monitoring
shall include arrangements for the Generator and the SO to access the
information.
(ee) With regard to the installation of devices for system operation and
devices for system security, if the SO considers that it is necessary for
a Generator to install additional devices in order to preserve or restore
system operation or security, the SO and the Generator shall
investigate that matter and agree on an appropriate solution.
(ff) The maximum admissible Active Power reduction from Registered
Capacity with falling frequency shall be no greater than:
(i) Steady State Domain: 2% of the Registered Capacity at 50

Hz, per 1 Hz frequency drop, below 49.5 Hz; and
(ii) Transient Domain: 2% of the Registered Capacity at 50 Hz,
per 1 Hz frequency drop, below 49 Hz.
and subject to the ambient condition correction curves as provided by
each individual Generating Unit as well as other relevant technical
factors as agreed between the SO and the Generator.
(gg) For Generating Units using gas as a fuel source at the time of the
Low Frequency Event, the standard ambient conditions for the
measurement of admissible Active Power reduction will be 10°C, 70 %
relative humidity and 1013 hPa.
For all applicable Generating Units:
(hh) The Generating Unit must be capable of starting up on Secondary
Fuel. The Generating Unit must be capable of carrying out an online
fuel changeover from Primary Fuel to Secondary Fuel at Primary Fuel
Switchover Output in no greater than five hours. When operating on
Secondary Fuel, the generator must be capable of operating on
Secondary Fuel at no less than 90% of Primary Fuel Registered
Capacity. The Generating Unit must also be capable of carrying out an
online fuel changeover from Secondary fuel to Primary Fuel at
Secondary Fuel Switchover Output.
(ii) The Generating Unit must store sufficient stocks of Secondary Fuel
equivalent to one, three or five days of continuous running at Primary
Fuel Registered Capacity as defined by Clause CC.7.3.1.2. A minimum
of one day of running at Primary Fuel Registered Capacity on
Secondary Fuel must be stored at the Generator Site. The remainder of
the Secondary Fuel stock requirement can be stored at an Off-Site
Storage Location.
(jj) A Generating Unit is designated as high merit or low merit by the
NEPRA. The Generating Unit that is designated as high merit will be
CC 87
required to hold 5 days of Secondary Fuel stocks, low merit designated
Plant will be required to hold 3 days of Secondary Fuel stocks. Other
Plant as designated by the NEPRA will be required to hold Secondary
Fuel stocks equivalent to one day continuous running at Primary Fuel
Registered Capacity.
(kk) Users shall install Generating Unit governors that comply with
OC.4.3.4. Users shall not change frequency or load related control
settings of Unit governors without agreement with the SO.
(ll) Notwithstanding CC.7.3.1.1 combustion turbine, hydro, or other
technology based Generating Units shall as appropriate, register and
perform to Operating Characteristics giving maximum flexibility of
operation, consistent with their type and model of generation plant, in
accordance with Good Industry Practice. Where appropriate, Operating
Characteristics and in particular start times, should be registered
separately for normal (planned) starts, and for starts required under
conditions of system stress, such as following the loss of a Generating
Unit. The Generator will maintain operational procedures and
practices, which ensure that there are no unnecessary delays in
responding to Dispatch instructions in accordance with the technical
capabilities of the Generation Plant.
(mm) Where the SO approaches a Generator, the Generator will co-operate
with the SO in the development of procedures and facilities to improve
the response of each Generating Unit during conditions of system
stress, including, for example, automatic start-up of fast-start
Generating Units following a loss of Generating Unit(s) or in advance of
an anticipated loss of Generating Unit(s). This shall be subject to the
agreement of the Generator that the procedures are consistent with
secure operation of the Generator’s Plant, such agreement not to be
unreasonably withheld.
CC 6.3.3 Where start-up time of Generating Units exceeds thirty minutes, they
shall be designed to have the capability, where supply from the
Transmission System is lost, to reduce output to match house load and
sustain operation (i.e. tripping to Auxiliaries).
(1) In case of disconnection of the Generating Unit from the Transmission
System, the Generating Unit shall be capable of quick re-synchronisation
as agreed between the SO and the Generator.
(2) Where start-up time of Generating Units exceeds fifteen minutes, they
shall be designed to have the capability, where supply from the
Transmission System is lost, to reduce output to match house load and
sustain operation (i.e. tripping to Auxiliaries). Generating Units must be
designed to trip to house load from any operating point in its Reactive
Power capability. In this case, the identification of house load operation
must not be based solely on the system operator's switchgear position
signals.
(3) Generating Units shall be capable of continuing operation for 4 hours
following tripping to house-load, irrespective of any auxiliary connection
to the external Transmission System.
CC 6.3.4 Control Synchronising shall be provided by Generators at circuit breakers

identified by the TSO, which, depending on the Plant configuration may
include:
(a) the Generating Unit circuit breaker;
(b) the Generator Transformer LV and HV circuit breakers;
The SO will provide to the Generator signals from the SO operated Plant
and Apparatus as are required to facilitate synchronising on the Generator
CC 88
Transformer HV circuit breaker, in accordance with the relevant provisions
of the Connection Agreement.
CC 6.3.5 The Synchronising facilities in CC.7.3.3 shall facilitate Synchronising under

the following conditions:
i. Transmission System Frequency within the limits 48.0 to 52.0 Hz;
ii. Transmission System Frequency within the limits 47.0 to 52.0 Hz;
iii. Transmission System Voltage within the limits as specified in
CC.8.3.2, notwithstanding CC.7.3.6;
CC 6.3.6 Each Generating Unit shall be designed, where practicable, to mitigate the
risk of common mode failure with other Generating Units. In particular
each Generating Unit shall be designed so that it can operate with its
essential auxiliaries supplied through a unit transformer which shall be
connected between the Generating Unit circuit breaker and the Generator
Transformer LV terminals, or from another secure source as agreed with
the TSO. Auxiliary supplies may, provided that they are in accordance with
Good Industry Practice, be taken from an alternative source during
commissioning, testing, start-up or emergencies.
CC 6.3.7 In the case of a CCGT Installation this applies to the Combustion Turbine
Units only.
CC 6.3.8 Reactive Power capability

(1) Notwithstanding the limitations in Addenda 1, 2 and 3 for Solar, Wind and
BESUs, each Generating Unit shall have the following Reactive Power
capability as measured at their alternator terminals:
Table 1-4. Voltage ranges at Generating Unit terminals

Connected at: At Registered At 35% of
Voltage Capacity between: Registered
Range Capacity between:
118.8kV ≤ V ≤ 144kV 132kV 0.93 power factor 0.7 power factor
leading to 0.85 power leading to 0.4 power
factor lagging factor lagging
102kV ≤ V < 118.8kV Unity power factor to 0.7 power factor
0.85 power factor leading to 0.4 power
lagging factor lagging
200kV ≤ V ≤ 245kV 220kV 0.93 power factor 0.7 power factor
leading to 0.85 leading to 0.4 power
power factor lagging factor lagging
190kV ≤ V < 200kV Unity power factor to 0.7 power factor

CC 89

CC 90
At between Registered Capacity and 35% Registered Capacity, Mvar
capability to be not less than indicated by a straight line drawn between
the two points derived from the above, on a plot of Mvar capability against
MW output.
(2) At below 35% Registered Capacity, Mvar capability to be not less than that
at 35% Registered Capacity.
(3) The Generator Transformer shall be designed such that the Reactive
Power capability is possible over the full range of Transmission System
Voltages (specified in Table 1-4).
(4) Generating Units connecting to the Transmission System shall comply
with the following Reactive Power requirements at Registered Capacity
(Pmax) at the Connection Point;
132 kV & 220 kV
500 kV, 765 kV & 1100kV
The Generating Unit shall be capable of moving to any operating point

with its U- Q/Pmax profile in appropriate timescale to target values. The
appropriate timescale shall be identified during the TSO’s Connection Offer
process.
CC 91
(5) The SO and the Generator will liaise on matters related to CC.7.3.6 at the
design stage.
(6) For Generating Units where the Connection Point is remote from the Grid
Connected Transformer, any supplementary Reactive Power compensation
required to offset the Reactive Power demand of the HV line, or cable,
between the Connection Point and the Generating Unit shall be identified
during the TSO’s Connection Offer process.
(7) Generating Units shall be capable of providing Reactive Power at least
down to Minimum Generation.
Even at reduced Active Power output, Reactive Power supply at the
Connection Point shall correspond fully to the Reactive Power capability of
that Generating Unit, taking the auxiliary supply power and the Active
and Reactive Power losses of the step-up transformer, if applicable, into
account. In the event of power oscillations, Generating Units shall retain
steady-state stability when operating at any operating point of the
Reactive Power capability
CC 6.3.9 Each Generating Unit must be fitted with a fast acting proportional turbine
speed governor and unit load controller or equivalent control device to
provide Frequency response under normal operating conditions in
accordance with OC.4. The governor must be designed and operated to
the appropriate:
i. Pakistan Standards; or
ii. In the absence of a relevant Pakistan Standards, such other
International standard, i.e. International Electrotechnical
Commission (IEC) Standards which is in common use within the
Electric Utilities
iii. As at the time when the installation of which it forms a part was
designed. Normal governor regulation shall be between 3% and
5%.
iv. Generating Units shall be capable of setting governor regulation
between 2% and 12%. The default governor regulation setting
shall be 4%.
CC 6.3.10 All Generating Units shall be capable of contributing to control of
Transmission System Voltage by continuous modulation of Generator
Voltage by means of a suitable continuously acting Automatic Voltage
Regulation (AVR) which shall comply with BS4999 part 140, or equivalent
European Standards and the characteristics of which have been accepted
by the SO prior to the Connection Date, such acceptance not to be
unreasonably withheld.
CC 6.3.11 Each Generator Transformer shall have on-load tap changing facilities
(OLTC). The tap step shall not alter the Voltage ratio at the HV terminals
by more than:
i. 2.5% on the 110kV system
ii. 1.6% on the 220kV and 500kV systems or as agreed with the SO.
iii. Xx% on 765 kV & 1100 kV or as agreed with SO
CC 6.4 Demand Side Unit
Each Demand Side Unit shall, as a minimum, have the following capabilities:
(a) Able to provide Demand Side Unit MW Response between 0 MW and the
Demand Side Unit MW Capacity;
(b) Maximum Ramp Up Rate not less than XXX% per minute of Demand
Side Unit MW Response as specified in the Dispatch Instruction;
(c) Maximum Ramp Down Rate not less than XXX%per minute of Demand
CC 92
Side Unit MW Response as specified in the Dispatch Instruction;
(d) Minimum Down Time not greater than 30 minutes;
(e) Maximum Down Time not less than 2 hours;
(f) Minimum off time not greater than 2 hours;
(g) Demand Side Unit MW Response Time of not greater than 1 hour;
(h) maintain Demand Side Unit MW Response at Transmission System

Frequencies in the range 49.5Hz to 50.5Hz;
(i) maintain Demand Side Unit MW Response at Transmission System

Frequencies within the range 47.5Hz to 49.5Hz and 50.5Hz to 52Hz for a
duration of 60 minutes;
(j) maintain Demand Side Unit MW Response at Transmission System
Frequencies within the range 47.0Hz to 47.5Hz for a duration of 20
seconds required each time the Frequency is below 47.5Hz; and
(k) maintain Demand Side Unit MW Response for a rate of change of

Transmission System Frequency up to and including 0.5 Hz per second as
measured over a rolling 500 milliseconds period.
CC 93
CC 7
47 – 47.5 Hz 20 seconds
47.5 – 48.5 Hz 60 minutes
48.5 – 49.5 Hz 60 minutes
49.5 – 50.5 Hz Unlimited
50.5 – 51.5 Hz 60 minutes
51.5 – 52 Hz 60 minutes
On-site Generation operated in Continuous Parallel Mode or Shaving

Mode that forms part of a Demand Side Unit, shall, as a minimum, have the
following capabilities:
(l) operate continuously at normal rated output at Transmission System
(m) remain synchronised to the Transmission System at Transmission
System Frequencies within the range 47.5Hz to 52.0Hz for a duration
of 60 minutes;
(n) remain synchronised to the Transmission System at Transmission
System Frequencies within the range 47.0Hz to 47.5Hz for a duration
of 20 seconds required each time the Frequency is below 47.5Hz; and
(o) remain synchronised to the Transmission System during a rate of
change of Transmission System Frequency of values up to and
including xx Hz per second over a 500 msec windows.
On-site Generation operated in Lopping Mode or Automatic Mains Failure

Mode that forms part of a Demand Side Unit, shall, as a minimum, have the
following capabilities:
(p) operate continuously at normal rated output at Transmission System
CC 94
Figure 1-5. Demand Side Units parameters
CC 7.1.1 Demand Facilities, XXXs, DISCOs, Provincial & SPTLs Companies

shall:
(1) Remain synchronised to the Transmission System and operate within the
frequency ranges and time periods specified in Table 1-5.
Table 1-5.Demand Facilities, Discos, Provincial and SPTLs Companies
47 – 47.5 Hz 20 seconds
47.5 – 48.5 Hz 90 minutes
48.5 – 49.0 Hz 90 minutes
49.0 – 51.0 Hz Unlimited
51.0 – 51.5 Hz 90 minutes
51.5 – 52 Hz 60 minutes
(2) Remain synchronised to the Transmission System and operate within the
ranges of the Transmission System Voltage at the connection point, for
an unlimited time period, see Table 6:
Table 6.Voltage range to stay connected. Voltage Range to stay connected
Voltage Voltage Range (p.u.)
1100 0.9 - 1.05
765 kV 0.9 - 1.05
CC 95
500 kV 0.9 - 1.05
220 kV 198 kV to 245 kV 0.9 - 1.114
132 kV 118.8 to 147 kV 0.9 - 1.118
(3) Demand Facilities which alter their MW consumption at their

Connection Point, based on changes in Transmission System Frequency
and/or Voltage, shall coordinate and agree their controls, protection,
triggers and/or settings with the SO in advance of such alterations as
appropriate.
(4) Reactive Power

1. Demand Facilities without onsite generation shall be capable of
maintaining their steady-state operation at their Connection Point
within a Reactive Power range of 0 to 0.48 [Qmax/PMIC] equal to a
power factor of 1 to 0.9 lagging.
2. Demand Facilities with onsite generation shall be capable of
maintaining their steady-state operation at their Connection Point
within a Reactive Power range of -0.48 [Qmin/max{PMEC,PMIC}] to
0.48 [Qmax/PMEC] which is equal to a power factor of 0.9 lagging to
0.9 leading.
3. The Distribution Systems, Provincial & SPTLs Companies
shall be capable of maintaining steady-state operation at the
Connection Point within a Reactive Power range of -0.48
Qmin/max{PMEC,PMIC} during Reactive Power import/consumption,
and 0.48 Qmax/PMEC during Reactive Power export/production equal
to a power factor of 0.9 lagging to 0.9 leading, except in situations
where either technical or financial system benefits are proved by the
SO and the DISCOs, Provincial & SPTLs Companies through joint
analysis. The SO and DISCOs, Provincial & SPTLs Companies shall
agree on the scope of such an analysis, which shall address the
possible solutions, and determine the optimal solution for Reactive
Power exchange between their systems, taking adequately into
consideration the specific system characteristics, variable structure
of power exchange, bidirectional flows and the Reactive Power
capabilities in the Distribution Systems, Provincial & SPTLs
Companies .
4. The SO may require a Distribution System, Provincial & SPTLs
Companies to have the capability at the Connection Point to not
export Reactive Power (at reference 1 p.u. voltage) at an Active
Power flow of less than 25 % of the Maximum Import Capacity. The
request will be justified through a joint analysis with the XXX or the
Distribution System, Provincial & SPTLs Operators and the SO. If the
requirement is not justified based on the joint analysis, the SO and
the Distribution System, Provincial & SPTLs Operators shall agree on
necessary requirements according to the outcomes of the joint
analysis.
5. Without prejudice to CC.7.4.2.4.3, the SO may require the
Distribution System, Provincial & SPTLs Operators to actively control
the exchange of Reactive Power at the Connection Point for the
benefit of the entire system. The SO and the Distribution System,
Provincial & SPTLs Operators shall agree on a method to carry out
this control, to ensure the justified level of security of supply for both
CC 96
parties. The justification shall include a roadmap in which the steps
and the timeline for fulfilling the requirement are specified.
6. The Distribution System, Provincial & SPTLs Operators may require
the SO to consider its Distribution System, Provincial & SPTLs for
Reactive Power management.
(5) Reconnection
a) The SO will specify the conditions under which Demand Facilities,
Distribution System, Provincial & SPTLs can reconnect following a
Disconnection.
b) Demand Facilities, Distribution System, Provincial & SPTLs shall
facilitate Synchronising to the Transmission System within the limits
47 – 52.0 Hz.
c) The SO shall agree the settings for synchronisation devices with
Demand Facilities, Distribution System, Provincial & SPTLs prior to
connection.
(6) Disconnection
Demand Facilities, Distribution System, Provincial & SPTLs shall be
capable of remote Disconnection from the Transmission System. The
equipment required for automated remote Disconnection will be
specified by the SO. The automated remote Disconnection system will
be required to operate without any time delays, other than those
inherent in the design of the system.
(7) Short-circuit
Demand Facilities, Distribution System, Provincial & SPTLs shall
be capable of withstanding maximum short-circuit currents as specified in
CC.8.6.
CC 7.2 Interconnector
CC 7.2.1 The conditions specified in this section of the Grid Code apply to all
Interconnectors connected to or connecting to the Transmission System.
The provision of services affecting the Transmission System shall be in
accordance with the Interconnector Operating Protocol (InOP) [X] as
agreed with the SO and the External System Operator.
CC 7.2.2 Each Interconnector, shall have the following minimum capabilities,
for the avoidance of doubt, additional performance capabilities are
required from OC.4 System Services:
(a) operate continuously at MW Output at Transmission System
(b) operate and remain connected to the Transmission System at
Transmission System Frequencies within the range 47.5Hz to
52.0Hz
(c) remain connected to the Transmission System at Transmission
duration of 30 seconds required each time the Frequency is
below 47.5Hz;
(d) remain connected to the Transmission System during rate of

change of Transmission System Frequency of values up to and
including 2.5 Hz per Second over a 1 second window;
(e) remain connected to the Transmission System at MW Output at
CC 97
Transmission System Voltages within the ranges and for step
changes in Transmission System Voltage specified in CC.8.3.2;
(f) sustained operation in accordance with the Reactive Power

capability referred to in CC.7.5.10 at Transmission System
Voltages within the ranges specified in CC.8.3.2, unless
otherwise specified;
(g) remain connected during and following Voltage dips at the HV

terminals of the Interconnector Transformer of 100% of
nominal Voltage (0% retained) for duration 0.2 seconds and
Voltage dips of 50% of nominal Voltage (i.e. 50% retained) for
duration of 0.6 seconds. Following the fault clearance the
Interconnector should return to pre-fault conditions subject to
normal Frequency Response and Voltage Regulation;
(h) operate within all normal operating characteristics at a

minimum short circuit level at the Connection Point of xxxx
MVA;
(i) remain connected to the Transmission System during a

negative phase sequence load unbalance in accordance with
IEC 60034-1;
(j) have support triggers to allow the Interconnector to provide

System Services as outlined in OC.4, notwithstanding the
Interconnector Operating Protocol;
(k) in Emergency capable of reversing the power flow on the

Interconnector at a rate which shall be no less than the
Interconnector Registered Capacity within five seconds, up to ten
times during the life of the plant and no more than two times in
any given twelve months;
(l) Interconnector Minimum Load: not greater than the lesser of 3%

the Interconnector Registered Capacity or 65 MW;
(m) Interconnector Ramp-up Capability: not less than the greater of

10% of the Interconnector Registered Capacity per minute or 65
MW per minute, when the Interconnector is in the Normal
Dispatch Condition;
(n) Interconnector Ramp-down Capability: not less than the greater

of 10% of the Interconnector Registered Capacity per minute or
65 MW per minute, when the Interconnector is in the Normal
Dispatch Condition;
(o) Forbidden Zones: within the lesser range of between + and - 3%

of the Interconnector Registered Capacity or xx MW in either flow
direction or not more than 2 specified zones.
(p) Block Load for an Interconnector: not greater than the lesser of
3% of the Interconnector Registered Capacity or 30 MW in either
flow direction.
(q) Time from off-line to Interconnector Minimum Load in either

flow direction: Not greater than 30 minutes.
(r) Time from Interconnector Minimum Load in either flow

direction to off-line: Not greater than 30 minutes.
(s) The SO may request Interconnectors to have the capacity to
CC 98
operate under AGC at all loads between AGC Minimum Load and
AGC Maximum Load
CC 7.2.3 Where the SO approaches an Interconnector Operator and/or the

Reference Load dispatch Center (RLDC) , the Interconnector Operator
and/or the Reference Load dispatch Center (RLDC) will co-operate with the
SO in the development of procedures and facilities to improve the
response of each Interconnector during conditions of system stress. This
shall be subject to the agreement of the Interconnector Operator that the
procedures are consistent with secure operation of the Interconnector
Operator’s Plant, such agreement not to be unreasonably withheld.
CC 7.2.4 The Interconnector Operator and/or the Reference Load dispatch Center
(RLDC) must ensure that the reversal of flow capabilities is provided for
such that the average Interconnector Ramp Rate from Interconnector
Registered Export Capacity to Interconnector Minimum Import Load or
Interconnector Registered Import Capacity to the Interconnector
Registered Export Capacity of at least 65 MW per minute. For the
avoidance of doubt this aggregate Interconnector Ramp Rate will include
any time needed to pass through deadbands or Forbidden Zones of
operation.
CC 7.2.5 The Interconnector will be able to connect to the Transmission System
under the following conditions:
i. Transmission System Frequency within the limits 47.5 to
52.0 Hz;
ii. Transmission System Voltage within the limits as specified
in CC.8.3.2, notwithstanding CC.7.5.9;
iii. Transmission System Short Circuit Level at the point of
connection no less than xxxx MVA.
iv. Where supply from the Transmission System is temporarily
lost, Interconnectors must be able to reconnect to the
Transmission System and reach Minimum Load within 30
minutes of the Transmission System supply being restored.
CC 7.2.6 Each Interconnector:

i. Must ensure that they do not cause any sub synchronous
resonance, undamped oscillations or harmful shaft torsional
oscillations to Users on the Transmission System. This shall be
demonstrated by simulation prior to connection by the
Interconnector using best industry practice as agreed by the
SO and according to the SO’s TSSPS procedure.
ii. Where it is determined by the SO that the Interconnector

does cause such harmful oscillations or resonances the
operation of the Interconnector shall cease until a solution is
agreed with the SO;
iii. Where further studies are required to examine an oscillation

or resonance issue there shall be an exchange of the
necessary data between the Interconnector Operator and the
SO, such exchange of data shall not be unreasonably
withheld. The Interconnector Operator shall provide a
report to show the contribution that the Interconnector control
system design will have on the torsional mode frequencies.
iv. Input provisions for addition of a future sub synchronous

damping controller shall be made by the Interconnector
Operator;
CC 7.2.7 Each Interconnector must be capable of:

CC 99
i. contributing to Frequency Control by continuous modulation
of Active Power supplied to the Transmission System;
ii. contributing to Voltage Control by continuous changes to

the Reactive Power supplied to the Transmission System;
CC 7.2.8 Users shall install Interconnector controllers that comply with OC.4 System
Services, notwithstanding the InOP and Annexes.
CC 7.2.9 Users shall not change frequency or load related control settings of the
Interconnector controllers without agreement with the SO .
CC 7.2.10 Standards for Frequency Response
Each Interconnector must be fitted with a fast acting control device

to provide Frequency Response under normal operating conditions in
accordance with OC.4.3. The control device must be designed and
operated to the appropriate:
(i) Pakistan Standards; or

(ii) In the absence of a relevant Pakistan Standards, such other
International standard, i.e. International Electrotechnical
Commission (IEC) Standards which is in common use within the
Electric Utilities and
(iii) Interconnection Operating protocol and Contractual Agreement.
CC 7.2.11 Interconnector Frequency Response

Notwithstanding the InOP and Annexes, an Interconnector must be
capable of maintaining its Active Power output (i.e. when operating in
Import mode) to the Transmission System at a level not less than the
amount determined by the linear relationship shown in the figure below
for System Frequency changes within the range f1 to f2 Hz, such that if
the System Frequency drops to f1 Hz the Active Power output shall
not decrease by more than 100 - P1 where P1 is the upper active power
limit as a percentage of the Active Power output before the frequency
change event, where:
i. f2≥f1
ii. 48Hz≤f1≤50Hz
iii. 48Hz≤f2≤50Hz
iv. 95%≤P1≤100% Active Power
Active Power
100% Active Power
P1
CC 100
f1 f2
Settings for each of f1, f2 and P1 shall be specified by the SO at least 120
Business Days prior to the Interconnector’s scheduled Operational
Date. The Interconnector Operator shall be responsible for implementing
the appropriate settings during Commissioning.
Alterations to these settings may be requested in real-time by the SO and

the implementation of the settings shall commence within 10 seconds of
receipt of the signal from the TSO.
Note: This clause is in addition to any other obligations for Frequency

Performance that the Interconnector may already have within the InOP
and Contract Agreement.
CC 101
Notwithstanding the InOP and Contractual Agreement, an
Interconnector must be capable of maintaining its Active Power
input (i.e. when operating in Export mode) from the Transmission
System at a level not greater than the amount determined by the
linear relationship shown in the figure below for System Frequency
changes within the range f3 to f4 Hz, such that if the System Frequency
drops to f3 Hz the Active Power input decreases by more than 100 -
P3 where P3 is the lower Active Power limit as a percentage of the
Active Power output before the frequency change event, where:
i. f4≥f3
ii. 48Hz≤f3≤50Hz
iii. 48Hz≤f4≤50Hz
iv. 0%≤P3≤100% Active Power
Active Power
100% Active Power
P3
f3 50Hz f
CC 102
Settings for each of f3, f4 and P3 shall be specified by the SO at least 120
Business Days prior to the Interconnector’s scheduled Operational
Date. The Interconnector Operator shall be responsible for
implementing the appropriate settings during Commissioning.
Alterations to these settings may be requested in real-time by the SO and

the implementation of the settings shall commence within 10 seconds of
receipt of the signal from the SO.
Note: This clause is in addition to any other obligations for Frequency

Performance that the Interconnector may already have within the
InOP and Contract Agreement.
CC 7.2.12 At the Grid Connection Point the Active Power output under steady state
conditions of any Interconnector directly connected to the Transmission
System should not be affected by Voltage changes in the normal operating
range specified by more than the change in Active Power losses at
reduced or increased Voltage. The Reactive Power output under steady
state conditions should be fully available at normal operating range.
CC 7.2.13 The Frequency Deadband for all Interconnectors should be no greater than
xxxxHz (for the avoidance of doubt, ±XXXXXHz).
CC 7.2.14 Automatic Voltage Regulation

(1) All Interconnectors shall be capable of contributing to control of
Transmission System Voltage by continuous modulation of Interconnector
Voltage by means of a suitable continuously acting Automatic Voltage
Regulation (AVR) which shall be in accordance with Pakistan Standards.
and the characteristics of which have been accepted by the SO prior to the
Connection Date, such acceptance not to be unreasonably withheld.
(2) The Voltage Regulation System shall be capable of receiving a Voltage
Regulation Set-point for the Voltage at the Connection Point. The Voltage
Regulation System shall act to regulate the Voltage at this point by
continuous modulation of the Interconnector’s Reactive Power output,
within its Reactive Power range. A change to the Voltage Regulation Set-
point shall be implemented by the Interconnector within 20 seconds of
receipt of the appropriate signal from the SO.
(3) The Voltage Regulation System Slope Setting shall be capable of being set
to any value between 1% and 10%. The setting shall be specified by the
SO at least 120 Business Days prior to the Interconnector’s scheduled
Operational Date. The Interconnector shall be responsible for
implementing the appropriate settings during Commissioning. The slope
setting may be varied from time to time depending on Transmission
System needs. The SO shall give the Interconnector a minimum of 1
Business Days’ notice if a change is required. The Interconnector shall
formally confirm that any requested changes have been implemented
within 1 Business Days of receiving the SO’s formal request.
(4) The speed of response of the Voltage Regulation System shall be such
that, following a step change in Voltage at the Connection Point the
Interconnector shall achieve 90 % of its steady-state Reactive Power
response within 1 second. The response may require a transition from
maximum Mvar production to maximum Mvar absorption or vice-versa.
CC 7.2.15 Interconnector Reactive Power

(a) There is a requirement for a continuously-acting automatic control
system to provide control of the Voltage (or zero transfer of Reactive
Power as applicable for Current Source Technology) at the Grid
CC 103
Connection Point without instability over the entire operating range of
the Interconnector.
(b) An Interconnector must be capable of maintaining zero transfer of
Reactive Power at the Grid Connection Point at all Active Power output
levels under steady state Voltage conditions. The steady state
tolerance on Reactive Power transfer to and from the Transmission
System expressed in Mvar shall be no greater than 5% of the rated
MW.
(c) An Interconnector (excluding Current Source Technology) must be
capable of supplying rated MW import / export at any point between
the limits 0.95 Power Factor lagging and 0.95 Power Factor leading
based on the Interconnector Registered Export Capacity at the
Connection Point. For the avoidance of doubt, Interconnectors shall be
capable of operating at any point within the shaded section for the
Power Factor ranges for Registered Import Capacity or Registered
Export Capacities illustrated in Figure CC.7.5.10. The box shape is
defined by the higher figure between Interconnector Registered Import
Capacity and Interconnector Registered Export Capacity.
CC 7.2.16 Interconnection Agreement

(1) The Interconnection Agreement shall consist of an Interconnector
Operating Protocol (InOP) between at least, the SO, the Interconnector
Operator and the External System Operator but may include the
Interconnector Operator. The agreement shall provide operational details;
requirements and services affecting the System and the External Systems.
For clarity, this shall not supersede any other agreements and is required
to ensure System Security when operating the Interconnector. The
Interconnection Agreement shall be agreed not less than 6 months prior to
operation.
CC 8 TRANSMISSION SYSTEM PERFORMANCE
CC 8.1 The System Operator shall ensure that National Transmission System complies with
the following technical, design and operation criteria at the Connection Site with a
User.
CC 8.2 This section contains detailed technical transmission system requirements, which
the System Operator shall specify in consultation with other Code Participants and
Users (the System Operator to provide detailed specifications outlined below if not
included thus for).
CC 8.3 The connected User shall assure that assure that the connection is designed to
operate within the limits of allowed Transmission System Performance
Characteristics.
CC 8.4 The SO shall in accordance with Prudent Utility Practice plan, design and operate
the Transmission System so as to endeavour to maintain the performance targets
at the Connection Point as set out in this CC.8.
CC 8.5 Transmission System Frequency
CC 8.5.1 The Transmission System Frequency is nominally 50 Hz and shall be
controlled:
(a) Between 49.8 to 50.2 Hz in Normal operating conditions:
(b) During Transmission System disturbances: 48.0 to 52.0 Hz.
(c) During exceptional Transmission System disturbances: 47.0 to 52.0

Hz.
CC 104
CC 8.5.2 The System Frequency could rise to 52.0 Hz or fall to 47.0 Hz in
exceptional circumstances, design of user's plant and apparatus must
enable operation of that plant and apparatus within that range in
accordance with the following:
i. 51.5 Hz – 52 Hz Operation for a period of at least 15 minutes is
required each time the Frequency is above 51.5 Hz.
ii. 51.0 Hz - 51.5 Hz Operation for a period of at least 90 minutes is
required each time the Frequency is within the range 51.0 – 51.5
Hz.
iii. 49.0 Hz – 51.0 Hz Continuous operation is required.
iv. 47.5 Hz - 49.0 Hz Operation for a period of at least 90 minutes is
required each time the Frequency is within the range 47.5 - 49.0 Hz.
v. 47.0 Hz - 47.5 Hz Operation for a period of at least 20 seconds is
required each time the Frequency is below 47.5 Hz.
For the avoidance of doubt, disconnection, by frequency or speed
based relays is not permitted within the frequency range 47.5 Hz to
51.5 Hz, unless agreed with the SO.
Other users should ensure that their equipment is designed or
protected for these exceptional circumstances.
CC 8.6 Transmission System Voltages

CC 8.6.1 Introduction
Under (N-0) normal operating conditions, System Operating Voltages of
the Total System shall be maintained within the bandwidth of +8% to -5%
of Nominal System Voltage.
Under (N-1) contingency operating conditions, the voltage variation shall
be in the range of +10% and -10% of Nominal System Voltage.
However, 132 kV System Operating Voltages at the Points of Connection
shall be governed by the limits provided in the Performance Standards
(Transmission} and/or Performance Standards (Distribution} as applicable.
CC 8.6.2 The Transmission System Voltages are nominally 1100kV, 765kV, 500kV,
220kV and 132kV. Normal operating ranges are show below:
Nomina
Max Min
l
[kV] [kV]
[kV]
1100kV 1188 1045
765kV 826 726
500kV 540 475
220kV 238 209
132kV 143 125
CC 8.6.3 During Transmission System disturbances or following transmission faults

voltage shall be within the values shown below:
Nominal Max Min
[kV] [kV] [kV]
CC 105
1100kV 1210 990
765kV 841 688
500kV 550 450
220kV 245 198
132kV 145 119
CC 8.6.4 Some Transmission System disturbances (e.g. earth faults, lightning

strikes) will result in short-term Voltage deviations outside the above
ranges.
CC 8.7 The negative phase-sequence component of the phase Voltage of the Transmission
System Voltages will generally not exceed 1% under normal operating conditions.
CC 8.8 The Transmission System is an effectively earthed neutral system with an earth
fault factor less than 1.4.
CC 8.9 The Transmission System is designed and operated to maintain the Initial
Symmetrical Short-Circuit Current below the following:
(a)80kA on the 1100kV system
(b) 63kA on the 765kV system;
(c)50kA on the 500kV system;
(d) 40kA on the 220kV system;
(e)25 kA on the 132 kV system generally;
(f) 31.5 kA at designated locations on the 110kV system.
The SO shall notify any User with a connection to the Transmission System
at a location to which item (d) above applies that the location is so designated.
The SO shall publish annually a list of locations designated in accordance with item
above.
Some Transmission System disturbances (e.g. earth faults, lightning strikes) will
result in short-term Voltage deviations outside the above ranges.
CC 8.10 The negative phase-sequence component of the phase Voltage of the Transmission
System Voltages will generally not exceed 1% under normal operating conditions.
CC 8.11 The Transmission System is an effectively earthed neutral system with an earth
fault factor less than xxx.
CC 8.12 The Transmission System is designed and operated to maintain the Initial
Symmetrical Short-Circuit Current below the following:
(a) 50kA on the 400kV system;
(b) 40kA on the 220kV system;
(c) 25 kA on the 110 kV system generally;
(d) 31.5 kA at designated locations on the 110kV system.
CC 106
The SO shall notify any User with a connection to the Transmission System
at a location to which item (d) above applies that the location is so designated.
The SO shall publish annually a list of locations designated in accordance with item
above.
CC 9 USER PROTECTION AND POWER QUALITY

CC 9.1 CC.8 shall apply to the DISCO, Generators, Interconnectors and Demand Customers.
CC.8.1 Every User shall, acting in accordance with Good Industry Practice, be
responsible, insofar as is reasonably practicable, for ensuring that faults on Plant
and Apparatus cause minimal disturbance to the Power System. Faults on Plant
and/or Apparatus connected to the Transmission System should be cleared as soon
as possible with no deliberate time delay introduced and, in any event, should be
cleared within a maximum time of:
a. XXX milliseconds for the 110 kV system;
b. XXX milliseconds for the 220 kV system; and
c. XXX milliseconds for the 500 kV system.
d. XXX milliseconds for the 765 kV system.
e. XXX milliseconds for the 1100 kV system
CC 9.2 These clearance times are from primary protection systems only. Without limiting
this obligation, a User shall as a minimum prior to connection of the User's System
to the Transmission System install and maintain, in accordance with Good Industry
Practice, the protection equipment specified in CC.8.8 and CC.8.9.
CC 9.3 For the avoidance of doubt, the adequacy of protection equipment installed by the
User for protecting the User's Plant and Apparatus against Transmission System
disturbances is for the User to determine. It should also be noted that the SO’s
requirements are primarily intended to protect the Transmission System facilities,
although they afford a level of protection to Users, they are not primarily designed
to protect User’s facilities
CC 9.4 For the purpose of CC.8.1 the minimum protection requirements for a User facility
connecting to the Transmission System will vary according to type, size, Earthing
and method of connection. User protection required by the SO should always be in
service when associated plant is in service.
CC 9.5 It should be noted that high speed automatic reclosing (HSAR) is a feature of
Transmission System operation. This feature is characterised by the sudden re-
energisation of the power supply after a dead time of approximately 600
milliseconds. All tripping and high speed reclosing on the 132 kV System is three
pole. Tripping and high speed reclosing on the 220 kV and 500 kV Systems is a
combination of single pole and three pole.
CC 9.6 It is recommended that Users take precautions against disturbances on the
Transmission System including without limitation protection against:
(i) load unbalance (negative sequence) protection;
(ii) over/under-voltage;
(iii) over/under-frequency;
(iv) a combination of (b) and (c) that may result in overfluxing; and
(v) high speed automatic reclosing (HSAR), where applicable.
Users may consult with the SO with respect to protection adequacy.
CC 9.7 In order to ensure secure operation of the Transmission System and correct co-
ordination and discrimination between faults on the Transmission System and the
Distribution Systems, Provincial and SPTLs Systems, and User Systems, settings for
CC 107
User's protection systems that may have an Operational Effect, shall be notified to
the SO and it will be necessary for the SO to, and the SO may, prohibit the settings
of some User protection systems within certain ranges. Protection systems where
such limitations will apply include, but are not limited to:
(i) Generating Unit under-frequency, over-current, or distance protection;
(ii) transformer over-fluxing, over-current, or distance protection;
(iii) loss-of-mains protection.
A mechanism for the notification, and where applicable approval and

determination, of such settings will be set out in the User's Connection
Agreement or other agreements.
CC 9.8 The SO shall provide to the User the information and signals necessary for the
interface co-ordination and operation of the User’s protection, in accordance with
the relevant provisions of the Connection Agreement, other agreements and
CC.7.2.5.6.
CC 9.9 Where it is feasible to do so, the SO shall provide circuit breaker fail protection on
Grid Connection Point circuit breakers installed in new transmission stations.
CC 9.10 Generators
CC 9.10.1 Generators shall provide:
a. differential protection on the Generator Transformer. The

connections between the Grid Connection Point circuit breaker and the
HV terminals of the Generator Transformer shall be included in the
protected zone of this differential protection.
b. backup protection (to the Transmission System) on Generating Units.

The SO acting reasonably shall require one or more of the following to
be installed: generator overcurrent protection, voltage controlled
generator overcurrent protection or generator distance protection;
c. under frequency protection; and
d. Generating Unit loss of excitation protection.
CC 9.10.2 The SO may require a single Generating Unit, or group of Generators, to

install additional protection and/or control schemes, where the SO can
reasonably show that it is prudent or necessary to do so. These schemes
may include but are not limited to the following:
a. Generating Unit over/under-voltage protection.
b. Generating Unit over-frequency protection.
c. Generating Unit transformer neutral displacement voltage

detection.
d. loss-of-mains protection (rate of change of frequency or vector shift).
e. Generating Unit pole slip protection.
f. Power System stabiliser.
CC 9.10.3 Distance protection shall be provided by the SO on the Grid Connection

Point circuit breaker of Generator Transformers.
CC 9.10.4 The schemes and settings of the different control devices of the
Generating Units that are necessary for Transmission System stability and
for taking emergency action shall be coordinated and agreed between the
SO and the Generator. Any changes to the schemes and settings, of the
CC 108
different control devices of the Generating Units shall be coordinated and
agreed between the SO and the Generator.
CC 9.10.5
a. The SO shall specify the schemes and settings necessary to protect the
Transmission System, taking into account the characteristics of the
Generating Units. The protection schemes needed for the
Generating Units and the Transmission System as well as the
settings relevant to the Generating Units shall be coordinated and
agreed between the SO and the Generator. The protection schemes and
settings for internal electrical faults must not jeopardise the
performance of a Generating Unit.
b. Electrical protection of the Generating Units shall take precedence

over operational controls, taking into account the security of the system
and the health and safety of staff and of the public, as well as
mitigating any damage to the Generating Units.
c. Changes to the protection schemes needed for the Generating Unit

and the Transmission System and to the settings relevant to the
Generating Unit shall be agreed between the SO and the
Generating Unit.
CC 9.10.6 The Generator shall organise its protection and control devices in
accordance with the following priority ranking (from highest to lowest):
i. Transmission System and Generating Unit protection;
ii. Synthetic inertia (if applicable);
iii. Frequency Control;
iv. Power restriction; and
v. Power gradient constraint.
CC 9.10.7 Generators shall be capable of exchanging information with the SO in real

time or periodically with time stamping, as specified by the SO. The SO
shall specify the content of information exchanges including a precise list
of data to be provided by the Generator.
CC 9.10.8 Generators shall be capable of remaining connected to the Network during
single- phase or three-phase auto-reclosures on meshed Network lines.
The details of that capability shall be subject to coordination and
agreements on protection schemes and settings as referred to in CC.9.9.5.
CC 9.11 DISCOs, Provincial & SPTLs Companies

CC 9.11.1 The DISCOs, Provincial & SPTLs Companies shall provide differential-
protection on Grid Connected Transformers.
CC 9.11.2 The SO may require the DISCOs, Provincial & SPTLs Companies to
install additional protection schemes, where the SO can reasonably show
that it is prudent or necessary to do so, such schemes may include but are
not limited to the following:
i. directional overcurrent protection or distance protection on User’s

transformer(s);
ii. direct inter-tripping between the Grid Connection Point

circuit breaker and the User Connection Point circuit
breaker;
iii. neutral voltage displacement protection on HV side of User’s

transformer(s);
CC 109
iv. loss of mains protection;
v. under/over voltage protection;
vi. under/over frequency protection;
vii. unit (differential) type protection on Distribution, Provincial &

SPTLs System lines or cables;
viii. distance protection on the User Connection Point circuit breaker on

Distribution, Provincial & SPTLs lines or cables;
ix. bus zone protection on 132 kV Distribution, Provincial & SPTLs

System busbars; and
x. tele protection channels (for use with distance protection) between

the Grid Connection Point circuit breaker and Distribution,
Provincial & SPTLs circuit breaker.
CC 9.11.3 Distance protection or over-current protection shall be provided by the SO

on Grid Connection Point circuit breaker(s) unless where otherwise agreed
by the SO and Distribution, Provincial & SPTLs Companies
CC 9.11.4 The SO shall specify the devices and settings necessary to protect the
Distribution, Provincial & SPTLs System, on a site- specific basis. The
protection schemes needed for the Distribution, Provincial & SPTLs
System and the Transmission System, as well as the settings relevant to
the Distribution, Provincial & SPTLs System, shall be coordinated and
agreed between the SO and the Distribution, Provincial & SPTLs Electrical
protection of their Power System shall take precedence over operational
controls, taking into account the security of the system and the health and
safety of staff and of the public, as well as mitigating any damage to the
Distribution, Provincial & SPTLs System.
CC 9.11.5 The SO and the Distribution, Provincial & SPTLs System owner shall agree
on changes to the protection schemes relevant for the Distribution
System, and on the arrangements for the protection schemes of the
Distribution, Provincial & SPTLs System.
CC 9.11.6 The SO and the Distribution, Provincial & SPTLs Companies shall agree on
the schemes and settings of the different control devices of the
Distribution, Provincial & SPTLs Systems relevant for system security on a
site-specific basis. The SO and the Distribution, Provincial & SPTLs
Companies shall agree on any changes to the schemes and settings of the
control devices. This agreement shall include the following elements:
i. isolated (network) operation;
ii. damping of oscillations;

iii. disturbances to the Transmission System;
iv. automatic switching to emergency supply and restoration to normal
topology; and
v. automatic circuit-breaker re-closure (on 1-phase faults).
CC 9.11.7 The Discos, Provincial & SPTLs Companies shall set the protection and
control devices of its Distribution, Provincial & SPTLs System in
compliance with the following priority ranking, organised in decreasing
order of importance:
i. Transmission System protection

ii. Distribution System protection
iii. Frequency control (active power adjustment)
iv. Power restriction
CC 110
CC 9.12 Demand Customers
CC 9.12.1 Demand Customers shall provide differential-protection on Grid Connected
Transformers.
CC 9.12.2 The SO may require Demand Customers to install additional protection
schemes, where the SO can reasonably show that it is prudent or
necessary to do so, which may include the following:
i. directional overcurrent protection or distance protection on Grid
Connected Transformer(s) where the User System contains
Embedded Generating Plant;
ii. neutral voltage displacement protection on HV side of Grid
Connected Transformer(s);
iii. loss of mains protection where the User System contains
Embedded Generating Plant;
iv. under/over voltage protection where the User System contains
Embedded Generating Plant; and
v. under/over frequency protection where the User System contains
Embedded Generating Plant.
CC 9.12.3 Distance protection or over-current protection shall be provided by the SO
on the Grid Connection Point circuit breaker(s).
CC 9.12.4 The SO shall specify the devices and settings necessary to protect the
Demand Facility, on a site- specific basis. The protection schemes needed
for the Demand Facility and the Transmission System, as well as the
settings relevant to the Demand Facility, shall be coordinated and agreed
between the SO and the Demand Facility owner.
Electrical protection of the Demand Facility shall take precedence over
operational controls, taking into account the security of the system and
the health and safety of staff and of the public, as well as mitigating any
damage to the Demand Facility.
CC 9.12.5 The SO and the Demand Facility owner shall agree on changes to the
protection schemes relevant for the Demand Facility, and on the
arrangements for the protection schemes of the Demand Facility.
CC 9.12.6 The SO and the Demand Facility owner shall agree on the schemes and
settings of the different control devices of the Demand Facility relevant for
system security on a site-specific basis. The SO and the Demand Facility
owner shall agree on any changes to the schemes and settings of the
control devices. This agreement shall include but may not be limited to the
following elements:
i. isolated (network) operation;
ii. damping of oscillations;
iii. disturbances to the Transmission System;
iv. automatic switching to emergency supply and restoration to
normal topology; and
v. automatic circuit-breaker re-closure (on 1-phase faults).
CC 9.12.7 The Demand Facility owner shall set the protection and control devices
of its Demand Facility in compliance with the following priority ranking,
organised in decreasing order of importance:
i. Transmission System protection
ii. Demand Facility protection
iii. Frequency control (active power adjustment)
iv. Power restriction
CC 9.13 Interconnectors
CC 9.13.1 Interconnectors shall provide:
CC 111
(a) differential protection on the Interconnector Transformer. The
connections between the Grid Connection Point circuit breaker and
the HV terminals of the Interconnector Transformer shall be included
in the protected zone of this differential protection, or in the event
that other plant such as filter banks or reactors are connected to
these connections, they shall be protected by a suitable bus zone or
differential protection scheme.
(b) primary and backup protection for any plant (e.g. filter banks,
reactors, damping resistors) which may be connected between the
Grid Connection Point circuit breaker and the Interconnector
Transformer.
(c) backup protection (to the Transmission System) on

Interconnectors. The SO acting reasonably shall require one or
more of the following to be installed: Interconnector overcurrent
protection, Voltage controlled Interconnector overcurrent protection
or Interconnector distance protection.
(d) over/ under Frequency protection; and over/under-voltage protection.
CC 112
CC 9.13.2 The SO may require an individual Interconnector Operator, to install
additional protection and/or control schemes, where the SO can
reasonably show that it is prudent or necessary to do so. These schemes
may include but are not limited to the following:
i. Power System Stabiliser;
ii. Ability to accept set points and commands (e.g. to ramp up or ramp
down or reverse MW and or Mvar flows) from external System
Integrity Protection schemes.
CC 9.13.3 Distance protection shall be provided by the SO on the Grid Connection
Point circuit breaker of Interconnector Transformers.
CC 9.14 Power Quality.

CC 9.14.1
(a) Harmonic Voltage Distortion
Users shall ensure that their connection to the Transmission System
does not result in an increase in the level of harmonic distortion of the
supply Voltage on the Transmission System, at the Connection Point,
exceeding that allocated to them. These incremental limits will be
determined by the SO for each User’s connection, to ensure compliance
of Total Harmonic Distortions (THD) level in accordance with
IEEE Standard 519-1992 on the Transmission System.
The necessary data will be exchanged between both parties and the
exchange of data shall not be unreasonably withheld. This data may
consist of but is not limited to:
(i) Impedance Loci at the Connection Point,
(ii) background distortion levels and
(iii) Allocated Harmonic Distortion Limits (AHDL).
(b) Voltage Fluctuations:

Users shall ensure that their connection to the Transmission System
does not result in the level of fluctuation of the supply Voltage on the
Transmission System at the Connection Point exceeding limits set out
below. Any necessary data will be exchanged between both parties and
the exchange of data shall not be unreasonably withheld.
The voltage fluctuation at any Users connection point with a fluctuating

demand shall not exceed one 1% of the nominal voltage level for step
changes which may occur repetitively. Occasional step changes may be
allowed up to a level of 3% provided that this does not pose a risk to the
Transmission System or to the System of any other user.
(c) Voltage Flicker:
Users shall take responsibility for limiting Voltage Flicker caused by their
Plant to remain within the maximum permissible Voltage Flicker limits at
the Connection Point as allocated to them by the SO or, as a minimum,
those defined in Table 5 of IEC/TR 61000-3-7. For voltages above 132kV,
the flicker severity at any connection point in the Transmission System
shall not exceed the limits of the Flicker Severity Index (Short-term) Pst
of 0.8 Unit and Flicker Severity Index (Long-term) Plt of 0.6 Unit, both
95th percentile values measured over a period of one week. For
voltages of 132kV and below, Flicker Severity (Short Term) Pst of 1.0
Unit and a Flicker Severity (Long Term) Plt of 0.8 Unit.
(d) Rapid Voltage Change
OC-1 113
Users shall ensure that the disturbance levels introduced by their Plant
and/or Apparatus do not promote rapid Voltage changes exceeding
those specified in the above table or alternative limit allocated to them
by the SO during normal system operation.
Type of rapid Voltage ∆𝑼 Timeframe

Limit
change
𝑼𝑵
(%)
Must recover to
Temporary
5 nominal Voltage
Voltage
in 3 seconds
Depression
Step Change 3 One cycle
The User can be connected to the Transmission System provided that

the required studies have been completed by the User to show
compliance with the limits outlined in CC.10.13.1 (a) and CC.10.13.1 (b)
and have been reviewed by the TSO. Following consultation with the TSO,
a conditional connection may be allowed to Users where modelling of the
connection shows a breach of the limits to be marginal or only occurring
during contingencies as defined by the TSO. This may allow the User to
verify that the installation is compliant by monitoring, or to implement a
mitigation solution.
The User’s Allocated Harmonic Distortion Limits and any special

conditions pertaining to power quality will be referenced in the
Connection Agreement. These are subject to verification of compliance
by the SO and through an ongoing monitoring programme as described
in OC10.2.2 (c).
In the event that a User causes any such limits in CC.10.13.1 (a) and
CC.10.13.1 to be breached, the SO shall be entitled to require the User to
take such steps as the SO reasonably considers to be necessary in order to
prevent such breach from continuing and the User shall comply with the
TSO’s instructions without delay.
CC 9.14.2 The aggregate power factor for a Demand Customer is calculated in

accordance with the following formula:
APF=
∑P
√ (∑ P )2+(∑ Q )2
Where:
- APF is the Aggregate Power Factor for the Demand
Customer
- Sum P is the Energy exchanged with the Demand
Customer at the Connection Point for any half-hour period;
and
- Sum Q is the Reactive Energy exchanged with the Demand
Customer at the Connection Point for the same half-hour
period.
CC 9.14.3 A Demand Customer shall ensure that at any load above 50% of Maximum
Import Capacity the aggregate power factor as determined at the
Connection Point in any half-hour period shall be within the range 0.90
lagging to unity.
OC-1 114
CC 10 COMMUNICATION FACILITIES
CC 10.1 The communication facilities required to be provided by Users are addressed in the
Operating Codes.
CC 11 SIGNALS TO BE PROVIDED BY USERS
CC 11.1 Each User shall provide such signals and indications in relation to the User's Plant
and Apparatus as are required by the SO (acting reasonably) in accordance with the
CC 11.2 Signals and indications required to be provided by Users will include but shall not be
limited to the following:
(a) LV switchgear positions pertinent to the status of each Grid Connected
Transformer through a set of two potential free auxiliary contacts (one contact
normally open and one contact normally closed when circuit breaker is open) for
each circuit breaker;
(b) kV at transformer low Voltage terminals; and
(c) a minimum of four sets of normally open potential free auxiliary contacts in
each transformer LV bay for fault indication.
(d), (e), (f), (g), (h), (i) and (j) are applicable to Generators only:
(d) MW and +/-Mvar at alternator terminals of each Generating Unit;

(e) kV at Generator Transformer LV terminals;
(f) Generator Transformer tap position;
(g) Measured or derived MW output on each fuel, from Generating Units that can
continuously fire on more than one fuel simultaneously;
(h) Where it is agreed between the SO and the Generator that signals are not
available on the HV terminals, +/- MW and +/- Mvar shall be provided at the
Grid Connected Transformer low Voltage terminals; and
(i) Remaining Secondary Fuel capability (where applicable) in MWh equivalent
when running at Registered Capacity;
(j) With regard to real-time monitoring of Frequency Sensitive Mode, as
described in OC.1, the Generator shall be equipped to transfer in real time
and in a secured manner, at least the following signals:
1. status signal of Frequency Sensitive Mode (on/off);
2. actual parameter settings for Active Power frequency response; and
3. Governor Droop and Frequency Response Deadband.

The SO shall specify additional signals to be provided by the Generator by
monitoring and recording devices in order to verify the performance of the active
power frequency response provision of participating Generating Units.
(k) and (l) are applicable to Demand Customers only:
(k) MW and +/- Mvar at the HV terminals of the Grid Connected Transformer; and
(l) Grid Connected Transformer tap position.
(m), (n), (o), (p), (q), (r), (s) and (t) are applicable to Demand Side Unit Operators
who represent a Demand Side Unit:
(m) Demand Side Unit MW Response from Generation operating in Continuous

Parallel Mode or Shaving Mode;
OC-1 115
(n) Demand Side Unit MW Response from avoided Demand consumption and
Generation operating in Lopping Mode, Standby Mode or Automatic Mains
Failure Mode;
(o) Remaining Demand Side Unit MW Availability;
(p) Demand Side Unit MW Response from each Individual Demand Site with a
Demand Side Unit MW Capacity of greater than or equal to XXX MW;
(q) MW Output from Generating Units with a Capacity greater than or equal to 5
MW;
(r) Mvar Output from Generating Units with a Capacity greater than or equal to 5
MW at Individual Demand Sites with a Maximum Export Capacity specified in
the Connection Agreement or DSO Connection Agreement as applicable, as
required by the TSO;
(s) Aggregate MW Output from Generating Units with a combined Capacity of
greater than or equal to 5 MW on an Individual Demand Site, as required by the
TSO; and
(t) Demand Side Unit MW Response from each Individual Demand Site that
comprises the Demand Side Unit, as required by the TSO.
(u), (v), (w), (x) and (y) are applicable to Interconnectors only:
(u) +/-MW and +/-Mvar at the high Voltage terminals of the Interconnector
Transformer;
(v) kV at Interconnector Transformer high Voltage terminals;
(w) Interconnector Transformer tap position;
(x) Interconnector status; and
(y) Frequency.
CC 11.3 Where signals or indications required to be provided by the User under CC.11.2
become unavailable or do not comply with applicable standards due to failure of the
Users’ technical equipment or any other reason under the control of the User, the
User shall, acting in accordance with Good Industry Practice, restore or correct the
signals and/or indications as soon as possible.
CC 11.4 Signals to be provided by Users shall be presented in such form as is nominated by
the SO.
CC 11.5 Where, the SO, acting reasonably, determines that because of a Modification to the
Transmission System or otherwise to meet a Transmission System requirement,
additional signals and/or indications in relation to a User's Plant and Apparatus are
required, the SO shall notify that requirement to the User. On receipt of such a
notification the User shall promptly, and in accordance with Good Industry Practice,
ensure that such signals and/or indications are made available at the relevant
marshalling rack.
CC 11.6 Demand Side Unit Operators and Generator Aggregators shall provide the SO the
specification of the method of aggregation of SCADA from multiple sites. The
minimum specifications shall be agreed with the SO in advance and shall include:
(i) signals from Demand Side Unit Operators shall be relayed to the SO
Telecommunication Interface Cabinet which reflect the Demand Side Unit
MW Response to an accuracy of within 1 MW of the actual Demand Side Unit
MW Response within 15 seconds of change occurring to the Demand Side
Unit MW Response; and
(ii) a single failure of an item of the Demand Side Unit Operator’s equipment will
not result in:
a. loss of control of more than one Individual Demand Site;
b. loss of Demand Side Unit MW Response of more than one Individual
Demand Site; or
c. the Demand Side Unit MW Response from Generation or Demand
Side Unit MW Response from avoided Demand consumption signals
OC-1 116
being incorrect by more than the Demand Side Unit MW Capacity of
the Individual Demand Site with the highest Demand Side Unit MW
Capacity comprising the Demand Side Unit.
CC 12 POWER SUPPLIES
CC 12.1 Each User shall provide:

(a) 400 V ac / 230 V ac power supplies as required by the SO for Transmission
Station facilities, the capacity and detail of which shall be as specified by the
SO and provided for in the User's Connection Agreement;
(b) a standby supply for all ac power supplies for Transmission Station facilities by a
diesel generator, unless alternative means are agreed with the SO, such
agreement not to be unreasonably withheld. In the event of loss of mains,
standby supplies shall be capable of being sustained for a minimum of 10 hours.
CC 13 RESPONSIBILITY FOR SAFETY
CC 13.1 For each User Site and in consultation with the User, the SO shall detail in the
Operation Instructions the demarcation of responsibility for safety of persons
carrying out work or testing at the User's Connection Site and on circuits which
cross the User's Site at any point.
CC 13.2 More detailed information on procedures and responsibilities involved in safety
procedures is set out in OC.11.
CC 14 COMMISSIONING AND NOTIFICATION
CC 14.1 The SO and the User shall, in accordance with the provisions set out in the
Connection Agreement, meet to discuss Commissioning, including Commissioning
Tests and Grid Code Tests. The User's obligations in relation to Testing set out in
this CC.13 are in addition to the requirements under the Connection Agreement.
CC 14.2 Users are required to carry out such tests (which are defined to be Grid Code Tests)
as are required in order to confirm that the User's Plant and Apparatus meets all the
requirements of the Grid Code which must be met prior to the Operational Date.
The SO may, under the Connection Agreement, notify to the User such Grid Code
Tests as it requires the User to carry out. The SO may not necessarily test for
CC.7.3.1.1, (b), (c), (d)(i) and (e) but reserve the right to test to establish design
and operational compliance. For the avoidance of doubt it is the responsibility of
Users at all times to ensure their compliance with the Grid Code and testing
successfully or otherwise shall not in any way diminish or reduce such
responsibilities.
CC 14.3 Where Commissioning is likely to involve a requirement for Dispatch for Test
purposes, the User shall, as soon as possible, notify the SO of this requirement,
including reasonable details as to the duration and type of Testing required. Users
shall give the SO reasonable advance notice (being not less than xxxxx Business
Days) of the time of carrying out of the Commissioning Tests. The time and date of
such commissioning shall be reconfirmed not less than XXXX Business Days before
the time of carrying out such tests. In the event that, having given such
confirmation the User determines that such tests must be carried out prior to the
time and the date previously confirmed, then provided the User gives the SO
reasonable notice of the re-scheduled tests, he shall not be deemed to have failed
to give the notices required. The User shall as soon as it becomes aware of the
OC-1 117
same, subsequently notify the SO of any material changes in the requirement and
details so notified.
CC 14.4 The information provided under CC.13.3 is for indicative purposes only, and the
User shall subsequently make a formal request to the SO for a Commissioning Test
requiring Dispatch in accordance with the following provisions of this CC.13, and
shall not carry out such a Commissioning Test except as Dispatched in accordance
with this CC.13.
CC 14.5 Users shall make a request in writing to the SO for every Commissioning Test
requiring Dispatch, in accordance with CC.13.4. Such request to include the
following information:
CC 14.5.1 Details of the proposed Commissioning Test;
CC 14.5.2 Dispatches, where necessary, required by Users for completion of the
Commissioning Test, if any, including the duration of the Dispatch. Where
the User may not know the entire Dispatches required for completion of
the Test until part of the Test is completed then the User when proposing
the Test shall:
i. divide the Commissioning Test into sections as appropriate;
ii. indicate and discuss which sections of the Commissioning Test can
be completed in stages and which cannot;
iii. indicate possible variations of the Commissioning Test for the
sections which can be completed in stages.
CC 14.5.3 the preferred time or times for the Commissioning Test;
CC 14.5.4 the milestones for individual sections of the Commissioning Test (if any)
which can be completed separately, and/or do not require to be repeated if
the Commissioning Test is interrupted by the SO after completion of each
section.
CC 14.6 Generators and Interconnectors will be subject to SDC1 and SDC2 a minimum of
xxxxx days prior to the Operational Date and the Generating Unit or Interconnector
will be available for Dispatch from the Operational Date.
CC 14.7 Following the Connection Date but not later than the Operational Date Users shall
verify (by giving the SO such evidence as it may reasonably require including,
without limitation, the results of the relevant Commissioning Test or Grid Code Test)
technical data provided under the Planning Code and other technical data which the
SO reasonably requires to be verified to assess compliance with the Grid Code or
the Connection Agreement.
CC 14.8 The values as confirmed or verified under CC.13 shall be included in the User’s
Registered Operating Characteristics and Registered Data.
CC 14.9 The Generator shall demonstrate to the SO that it has complied with Generating
Unit requirements by successfully completing the Operational Notification
Procedure for connection of each Generating Unit.
CC 14.10 Operational Notification Procedure
CC 14.10.1 The Operational Notification Procedure for connection of each Generating

Unit requires the completion of three sequential processes, consisting of:
i. Energisation Operational Notification (EON);
ii. Interim Operational Notification (ION); and
iii. Final Operational Notification (FON).
CC 14.10.2 Energisation Operational Notification

The SO will issue an EON to the Generator for a Generating Unit,
subject to completion of the EON checklist. This checklist will require
agreement on the protection and control settings relevant to the
Connection Point. Upon receipt of the EON, a Generator may energise its
internal network and auxiliaries for the associated Generating Unit by
using the grid connection that is specified for the Connection Point.
OC-1 118
CC 14.10.3 Interim Operational Notification
The SO will issue an ION to the Generator for a Generating Unit, subject
to completion of the ION checklist. Upon receipt of the ION, a Generator
may operate the associated Generating Unit and generate power for a
limited period of time, by using the grid connection that is specified for the
Connection Point. The limited period of time shall be agreed with the SO
and shall not be longer than 24 months. An extension to this period of time
may be granted via a derogation undertaken according to GC.9.3, if the
Generator can demonstrate sufficient progress towards full compliance
and outstanding issues are clearly identified.
CC 14.10.4 Final Operational Notification

(1) The SO will issue a FON to the Generator for a Generating Unit, subject
to completion of the FON checklist. Upon receipt of the FON, a
Generator may operate the associated Generating Unit and generate
power by using the grid connection that is specified for the Connection
Point.
(2) If the SO identifies a reason not to issue a FON, the Generator may seek
a derogation via the process described in GC.9.3.
(3) Where a request for a derogation is rejected, the SO shall have the right
to refuse to allow the operation of the Generating Unit until the
Generator and the SO resolve the incompatibility and the SO considers
that the Generating Unit is compliant with Grid Code. If the SO and the
Generator do not resolve the incompatibility within a reasonable time
frame, but in any case not later than 6 months after the notification of
the rejection of the request for a derogation, each party may refer the
issue for decision to the NEPRA.
CC 14.11 A Generator issued with a FON shall inform the SO immediately in the following
circumstances:
a. the facility is temporarily subject to either significant modification or
loss of capability affecting its performance; or
b. equipment failure leading to non-compliance with some relevant
requirements.
CC 14.12 Limited Operational Notification (LON)

CC 14.12.1 A Generator shall apply to the relevant system operator for a Limited
Operational Notification (LON), if the Generator reasonably expects the
circumstances described in CC.13.11 to persist for more than three
months.
CC 14.12.2 The SO will then issue a LON containing the following information:
i. the unresolved issues justifying the granting of the LON;
ii. the responsibilities and timescales for the expected solution; and
iii. a maximum period of validity which shall not exceed 12 months.
The initial period granted may be shorter with the possibility of an
extension if evidence is submitted to the satisfaction of the SO
demonstrating that substantial progress has been made towards
achieving full compliance.
CC 14.12.3 The FON shall be suspended during the period of validity of the LON with
regard to the items for which the LON has been issued.
CC 14.12.4 A further extension of the period of validity of the LON may be granted
upon a request for a derogation, via the process described in GC.9.3, made
to the SO before the expiry of that period.
CC 14.12.5 The SO shall have the right to refuse to allow the operation of the
Generating Unit, once the LON is no longer valid. In such cases, the FON
shall automatically become invalid.
CC 14.12.6 If the SO does not grant an extension of the period of validity of the LON in
accordance with CC.13.12.4 or if it refuses to allow the operation of the
OC-1 119
Generating Unit once the LON is no longer valid in accordance with
CC.13.12.5, the Generator may refer the issue for decision to the NEPRA
within six months after the notification of the decision of the SO.
CC 14.13 Operational Notification Procedure

CC 14.13.1 The operational notification procedure for connection of each Demand
Facility, Distribution Facility, Distribution, Provincial & SPTLs System
requires the completion of three sequential processes, consisting of:
i. energisation operational notification (EON);
ii. interim operational notification (ION); and
iii. final operational notification (FON).
CC 14.13.2 Energisation Operational Notification (EON)
The SO will issue an EON to the Demand Facility Owner, and DISCOs,
Provincial & SPTLs for a Demand Facility, Distribution Facility and
Distribution, Provincial & SPTLs System, subject to completion of the
EON checklist. This checklist will require agreement on the protection and
control settings relevant to the Connection Point. Upon receipt of the EON,
a Demand Facility Owner, Distribution, Provincial & SPTLs Operators
may energise its internal network and auxiliaries for the associated
Demand Facility, Distribution Provincial & SPTLs Facility or Distribution,
Provincial & SPTLs System by using the grid connection that is specified
for the Connection Point.
CC 14.13.3 Interim Operational Notification
The SO will issue an ION to the Demand Facility Owner, and Distribution,
Provincial & SPTLs Operators for a Demand Facility, Distribution
Facility and Distribution, Provincial & SPTLs Operators System subject to
completion of the ION checklist. Upon receipt of the ION, a Demand
Facility Owner, and Distribution, Provincial & SPTLs Operators may
operate the associated Demand Facility, Distribution Facility or
Distribution, Provincial & SPTLs Operators System, by using the grid
connection that is specified for the Connection Point for a limited time
period. The limited period of time shall be agreed with the SO and shall not
be longer than 24 months. An extension to this period of time may be
granted via a derogation undertaken according to GC.9.4, if the Demand
Facility Owner, Distribution, Provincial & SPTLs Operators can
demonstrate sufficient progress towards full compliance and outstanding
issues are clearly identified.
CC 14.13.4 Final Operational Notification (FON)

(1) The SO will issue a FON to the Demand Facility Owner, Distribution,
Provincial & SPTLs Operators for a Demand Facility, Distribution Facility
or Distribution, Provincial & SPTLs System, subject to completion of the
FON checklist. Upon receipt of the FON, a Demand Facility Owner,
Distribution, Provincial & SPTLs Operators may operate the associated
Demand Facility, Distribution, Provincial & SPTLs Facility or
Distribution, Provincial & SPTLs System and generate power by using
the grid connection that is specified for the Connection Point.
(2) If the SO identifies a reason not to issue a FON, the Demand Facility
Owner, Distribution, Provincial & SPTLs Operators may seek a
derogation via the process described in GC.9.4. Where a request for a
derogation is rejected, the SO shall have the right to refuse to allow the
operation of the Demand Facility, Distribution, Provincial & SPTLs
Facility or Distribution, Provincial & SPTLs System until the Demand
OC-1 120
Facility Owner, Distribution, Provincial & SPTLs Operators and the SO
resolve the incompatibility and the SO considers that the Demand
Facility, Distribution, Provincial & SPTLs Facility or Distribution,
Provincial & SPTLs System is compliant with Grid Code.
If the SO and the Demand Facility Owner, Distribution, Provincial &
SPTLs Operators do not resolve the incompatibility within a reasonable
time frame, but in case not later than 6 months after the notification of
the rejection of the request for a derogation, each party may refer the
issue for decision to the NEPRA.
CC 14.14 Limited Operational Notification (LON)

CC 14.14.1 A Demand Facility Owner, Distribution, Provincial & SPTLs Operators issued
with a FON shall inform the SO within 24 hours of the incident, in the
following circumstances:
(a) the facility is temporarily subject to either significant modification or
loss of capability affecting its performance; or
(b) equipment failure leading to non-compliance with some relevant
requirements.
A longer time to inform the SO can be agreed with the Demand
Facility Owner, Distribution, Provincial & SPTLs Operators
depending on the nature of the changes.
CC 14.14.2 A Demand Facility Owner, Distribution, Provincial & SPTLs Operators shall
apply to the relevant system operator for a limited operational notification
(LON), if the Demand Facility Owner, Distribution, Provincial & SPTLs
Operator reasonably expects the circumstances described in CC.13.15.1 to
persist for more than three months.
CC 14.14.3 The SO will then issue a LON containing the following information:
i. the unresolved issues justifying the granting of the LON;
ii. the responsibilities and timescales for the expected solution; and
iii. a maximum period of validity which shall not exceed 12 months.
The initial period granted may be shorter with the possibility of an
extension if evidence is submitted to the satisfaction of the SO
demonstrating that substantial progress has been made towards
achieving full compliance.
CC 14.14.4 The FON shall be suspended during the period of validity of the LON with
regard to the items for which the LON has been issued.
CC 14.14.5 A further extension of the period of validity of the LON may be granted
upon a request for a derogation, via the process described in GC.9.4, made
to the SO
CC 14.14.6 The SO shall have the right to refuse to allow the operation of the Demand
Facility, Distribution, Provincial & SPTLs System, once the LON is no longer
valid. In such cases, the FON shall automatically become available.
CC 14.14.7 If the SO does not grant an extension of the period of validity of the LON in
accordance with CC.13.15.5 or if it refuses to allow the operation of the
Demand Facility, Distribution, Provincial & SPTLs Facility or Distribution,
Provincial & SPTLs System once the LON is no longer valid in accordance
with CC.13.15.6, the Demand Facility Owner, Distribution, Provincial &
SPTLs Operator may refer the issue for decision to the NEPRA.
OC-1 121
CC 15 APPENDIX A OF CONNECTION CODE: LIST of Minimum requirements for Power
System and Apparatus connected to the Transmission, Distribution, Provincial and
SPTLs Systems
(a) Requirements Relating to Generator/power system Connection Points
i. Generating Unit and Power Plant Protection Arrangements required related to
power system safety and security.
ii. Minimum Requirements.
a. Instantaneous (< 100 ms) fault clearance of generator and unit
transformer short circuit
b. Instantaneous (< 100 ms) fault clearance of unit transformer HV
winding earth fault
c. Back-up fault clearance of connected transmission short circuits and
earth faults
d. Loss of excitation protection
e. Pole slip protection
f. Deviating frequency protection
g. Deviating voltage protection
h. Circuit breaker failure protection
iii. Critical Fault Clearance Times.
iv. Equipment to be Provided.
v. Signals of Tariff Metering (CTs and PTs).
vi. Work on Protection Equipment: procedure.
(b) Requirements Relating to Network Operator and Non-embedded Consumers Connection

Points
i. Protection Arrangements for Network Operators and Non-embedded
Consumers.
 Fault Clearance Times ≤ 150 ms.
 Fault Disconnection Facilities.
 Automatic Switching Equipment.
 Work on Protection Equipment: procedure.
 Equipment to be provided.
 Protection of Inter-connections.
(c) General Generating Unit Requirements

i. Technical, Design and Performance Requirements
 Reserve and Ancillary Service Obligations.
 Maintenance Outage Requirements.
 Stability and Suitability Requirements
 Insulation Level Requirements.
 Lightning Protection
ii. Plant Performance Requirements

 All Generators Units must be capable of supplying rated power output (MW)
at any point between the limits 0.80 power factor lagging and 0.90 power
factor leading at the Generating Unit terminals. The short circuit ratio of
Generating Units shall be not less than 0.5%;
 Each Generating Unit must be capable of Continuously maintain constant
output for system frequency changes within the range 50.5 to 49.5 Hz; and
 The Active Power output under steady-state conditions of any Generating
Unit directly connected to the NTDC Transmission System should not be
affected by voltage changes in the normal operating range. The Reactive
Power output under steady-state condition should be fully available within
the voltage range of ±5% at all voltage levels.
iii. Control Arrangements
OC-1 122
 Each Generator, if technically possible, must be capable of contributing to
frequency and Voltage Control by continuous, modulation of Active Power
and Reactive Power supplied lo the National Transmission System;
 Each Generator must be fitted with a fast-acting turbine speed governor and
Unit Load Controller or equipment control device to provide frequency
response under normal operation conditions. The governor must be
designed and operated to the appropriate international standard; and
 A continuously-acting automatic excitation control system is required to
provide constant terminal voltage control of the Generator without
instability over the entire operating range of the Generator.
 Frequency and Voltage Control Modulation Minimum Frequency Response
Requirements (Appendix C).
 Steady-State Load Inaccuracies
The standard deviation of load error at steady state load over a 30 minutes
period must not exceed 2.5% of a Generating Unit.
 Neutral Earthing
At Nominal System Voltage of 132kV and above the higher voltage windings
of a transformer of a Generating Unit must be star-connected with the star
point suitable for connection to earth.
 Frequency Sensitive Relays
Generators shall be responsible for protecting all their Generating Units
against damage if frequency excursions outside permissible range ever
occur. Should such excursions occur, it is up to the Generator to decide
whether to disconnect his Apparatus Plant or Facility for reasons of safety of
Apparatus, Plant and/or personnel.
(d) General Network Operator and Transmission-connected Consumer Requirements
This part of the Grid Code describes the technical and design criteria and performance
requirements for authorized electricity operators and Transmission connected
Consumers.
(a) Neutral Earthing: earth fault factor < 1.4

(b) Frequency Sensitive Relays
Technical Requirements for Low Frequency Relays for the Automatic Load
Shedding (Appendix D)
(e) Communications System

i. Communication Requirements
ii. Control Telephony
iii. Operational Metering
iv. Instructor Facilities
v. Electronic Data Communication Facilities
vi. Facsimile Machines
vii. Busbar Voltages
(f) System Monitoring
(g) Site Related Conditions

i. Responsibilities of Construction, Commissioning, Control, Operation and
maintenance of Facilities
ii. Responsibility for Safety

 System Operator Safety Rules and Their Area of Application
 User's Safety Rules and Their Area of Application
 The System Operator Authorization to User/Network Operator to Carryout
Works
OC-1 123
 User's/Network Operator's Authorization to the System Operator to Carry
Out Works
iii. Site Responsibility Schedules
 Format, Principles and Procedures to be used in the preparation Site
Responsibility Schedules (SRS) (Appendix A)
 Proforma for Site Responsibility Schedule (SRS) (Attachment to Appendix A)
iv. Operation and Gas Zone Diagrams

 Appendix B (Part-I)
Principles and Procedures Relating to Operation Diagrams.
 Appendix B (Part-II)
Principles and Procedures Relating to Gas Zone Diagrams.
 Appendix B (Part-III)
List of all Apparatus to be shown on Operation and Gas Zone Diagrams.
 Operation Diagrams
 Gas Zone Diagrams
 Preparation of Operation and Gas Zone Diagrams for User's Sites
 Changes to Operation and Gas Zone Diagrams
v. Site Common Drawings

 Preparation of Site Common Drawings for a User Site
 Preparation of Site Common Drawings for Transmission system Sites
vi. Physical Access
 Physical Access Requirements and Conditions.
vii. Maintenance Standards
viii. Site Operational Procedures
(h) Ancillary Services

i. System Ancillary Services
ii. Commercial Ancillary Services
OC-1 124
CC 16 APPENDIX B OF CONNECTION CODE: FORMAT, PRINCIPLES AND PROCEDURES TO BE
USED IN THE PREPARATION SITE RESPONSIBILITY SCHEDULES (SRS)
CC.B.1 Principles
Principles which form the basis of developing SRS
CC.B.1.1 Types of Schedules
a. Construction b. Commissioning
c. Control d. Operation
e. Maintenance f. Testing
CC.B.1.2 New Connection Sites
CC.B.1.3 Sub-division of Connection Sites; if any
CC.B.1.4 Description of each Item of Plant and Apparatus at the Connection Site.
CC.B.1.5 Additional Detail of Plant and Apparatus, if any.
CC.B.1.6 Lines and Cables Emanating from Connection Sites.
CC.B.1.7 Issuance of draft SRS
CC.B.1.8 Accuracy Confirmation by concerned Parties
CC.B.1.9 Site Responsibility Schedule (Signed by the System Operator)
CC.B.1.10 Distribution of SRS
CC.B.1.11 Availability of Site Responsibility Schedules (SRS)
CC.B.1.12 Alterations/Revisions to Existing Site Responsibility Schedules; if any
CC.B.1.13 Revised Site Responsibility Schedules
CC.B.1.14 Finalization of Site Responsibility Schedules
CC.B.1.15 Urgent Changes
CC.B.1.16 Names and Designation of Authorized Person and Safety Coordinators
CC.B.1.17 De-commissioning of Connection Sites
OC-1 125
CC 17 APPENDIX C OF CONNECTION CODE (ATTACHMENT) PROFORMA FOR SITE
RESPONSIBILITY SCHEDULE (SRS)
This Performa should at least contain the following:
1. Number of Schedule, Issue, Number and Date.

2. Name of Complex and Connection Site.
3. Identification of Apparatus.
4. Name of the Owner of the Apparatus.
5. Name of the Person in charge of the Work Site (Authorized Person)
6. Item of Plant Apparatus.
7. Name of the Safety Co-ordinator.
8. Details of the Operations carried out on each Apparatus.
9. Safety Rules and Precautions.
10. Operational Procedures.
11. Party Responsible for Undertaking Inspections, Fault Investigation and Maintenance.
12. Remarks
OC-1 126
CC 18 APPENDIX D OF CONNECTION CODE (PART-I) PRINCIPLES AND PROCEDURES
RELATING TO OPERATION DIAGRAMS
(The Operation Diagram shall include all HV Apparatus and the Connections to all external
circuits including Numbering, Nomenclature, Labeling as set out in OC 1 0).
OC-1 127
CC 19 APPENDIX E OF CONNECTION CODE (PART-II) PRINCIPLES AND PROCEDURES
RELATING TO GAS ZONE DIAGRAMS
(Areas of the Connection Sites where gas-insulated metal enclosed switchgear and/or gas-
insulated HV apparatus is installed shall be depicted by a chain detted line which intersects the
Gas Zone boundaries. A Gas Zone Diagram is to be prepared for each Connection Site where a
gas-insulated switchgear/apparatus has been used. These Diagrams shall conform to the
Operation Diagrams in terms of Graphical symbols and Nomenclature)
OC-1 128
CC 20 APPENDIX F OF CONNECTION CODE (PART-III)
List of all apparatus to be shown on the Operation and Gas Zone Diagrams that is installed at
the Connection Sites including its present status as it pertains to the System Operation.
OC-1 129
CC 21 APPENDIX G OF CONNECTION CODE: Minimum Frequency Response Requirements
Scope
CC.G.1 Scope
CC.G.2 Plant Operating Range
CC.G.3 (a) Minimum Frequency Response Capability Profile in the graphical form;
(b) Interpretation of Initial and Secondary Response Values by the Connecting Party in the graphical
form
CC.G.4. Testing of Minimum Frequency Response Capability
CC.G.5 Repeatability of Response
OC-1 130
CC 22 APPENDIX H OF CONNECTION CODE: TECHNICAL REQUIREMENTS FOR LOW
FREQUENCY RELAYS FOR THE AUTOMATIC LOAD SHEDDING
CC.H.1 Low Frequency Relays
(Technical Specifications and Setting as per Connection Agreement)
CC.H.2 Low Frequency Relay Voltage Supplies
(Secured voltage supply arrangement for the low frequency relay)
CC.H.3 Scheme Requirements
a. Minimum dependability functional requirements at each Connection Site.
b. Outage requirements with respect to load shedding specified by the System Operator.
OC-1 131
CC 23 APPENDIX J: Scheme 1: INTERCONNECTION CONFIGURATIONS FOR GENERATORS
(Connections at 11 kV)
Connections at 11 kV
The Generators may adopt any of the configurations depending on its location with reference to the
substation and existing feeders and loading and operating condition of the feeders.
To Consumers
Licencee’s
Substation
Generator Substation
To Consumers
Licencee’s
Substation
OC-1 132
CC 24 Annexure E: Scheme 2: INTERCONNECTION CONFIGURATIONS FOR GENERATORS
Connections at 66kV
For connection of Generators at 66kV, two configurations have been indicated which may be adopted
according to the system conditions. The new Generators may opt for new configurations, which
System Operator may accept after carrying out necessary system studies.
66 kV 66 kV
Licencee’s Licencee’s
Substation Substation
OC-1 133
Annexure E: Scheme 2A: INTERCONNECTION CONFIGURATIONS FOR GENERATORS
Connections at 66kV
66 kV 66 kV
OC-1 134
Connections at 132kV
For interconnection of Generators to 132kV system two configurations schemes 3&3A have been
provided. Both the schemes are in use by existing Generators. However, the new Generators may opt
for new configurations, which the System Operator may accept according to prevailing and expected
future conditions of the Transmission System.
132 kV 132 kV
OC-1 135
(Connections at 220kV and 500kV)
Connections at 220kV and 500kV and future higher voltage levels
(To be provided by the System Operator)
OC-1 136
CC 27 Annexure F: Figure-1: CONNECTION PROCEDURE FOR NEW CONNECTION OR
MODIFICATION OF EXISTING CONNECTION
CC.F.1 ESTABLISHING OR MODIFYING CONNECTION
Under the requirements of the Transmission Licence, existing and proposed Users may assess
opportunities for connection to the National Transmission System in two ways:
(a) By reference to the Annual "NTDC Plan (IGCEP)", "Transmission Plant (TESP)" and
"System Operator Investment Plan" as described in the Planning Code (PC) in
accordance with the requirements of its Transmission Licence.
(b) An Offer by the System Operator to enter into a Transmission Service Contract for
Connection to the NTDC Transmission System for the following:
i. Existing Transmission Connection Points.
ii. New Transmission Connection Points.
iii. Modifications at an existing Transmission Connection Point.
A Connection Agreement is required for every Transmission Connection Point for each User at
that Connection Point. Therefore, for any of the above connection options, existing and
potential Users are required to enter into a Connection Agreement or to modify existing
Connection Agreements.
CC.F.1.1 Process and Procedures
The existing or prospective Code Participants seeking new connection or modifying the
existing connection shall comply with the following process and procedures [also shown in
Annexure F (figure 1)].
(a) Generators, distribution companies, Interconnection link companies, BPCs and SPTL
shall submit the connection application to System Operator if connecting directly to the
National Transmission System. Whereas, Generators and BPC connecting indirectly shall
submit their applications to the respective distribution companies and System Operator
simultaneously. The distribution companies shall evaluate their application for providing
the connection and shall forward to System Operator after review and approval for
registration as a Code Participant.
CC.F.1.2 Intention Application
An existing or prospective Code Participant wishing to modify its existing connection or

connect to the National Transmission System for the first time shall first prepare an
intention application. A form for intention application shall be available from the System
Operator. The application shall indicate:
(a) The type of facilities it intends to establish (generator, distribution company, BPC, etc.);
(b) Magnitude of Load Demand/Generation capability for the facility and load profile;
(c) Proposed Point of Connection;
(d) Tentative schedule for connection; and
(e) Proposed activity
The System Operator shall evaluate the intention application within 30 business days
(preliminary evaluation time) based on the following considerations and make
communication with the applicant.
(a) Evaluate the application and accompanied information;

(b) Check suitability of the proposed Point of Connection;
(c) Linear Load Flow analysis, contingency analysis and fault level studies in accordance
with the Planning Code by the System Operator on behalf of applicant;
(d) List out functional design requirements, Performance Standards requirements, and
specification; and communicate to the applicant in the next communication;
(e) Preliminary cost analysis for connection and estimated connection and registration fee;
OC-1 137
(f) Indicate if additional information is required from the applicant; and,
(g) Consultation of System Operator with other Code Participants to obtain their input
regarding impact on their facilities due to this connection application.
If the System Operator requires additional information· from the applicant, the applicant
must be advised within 30 business days (preliminary evaluation time period) to provide
such information and the application for connection must include such information as may
be required by System Operator from time to time. If System Operator does not require such
information, the applicant must be offered within the preliminary evaluation time period
formally to apply for connection to the network.
In case the applicant has been requested to provide additional information, it must provide
such information within 10 business days after receipt of request from the System Operator.
The System Operator shall provide the information/data related to its Transmission System
to applicant, which should help the applicant prepare its application. The required
information is listed, but not limited to, as follows:
(a) A list of the technical data as discussed in CC 5.4 and CC 6 to be included with the
application for connection which may vary depending on the connection requirements;
and the type, rating and location of the facility to be connected. Required technical data
are listed in CC 5.4 and CC 6 of this Connection Code.
(b) The preliminary estimate for connection fee and registration fee. Fees shall be
determined and shall be payable on submission of application for connection, and shall
cover the following:
i. Reasonable costs of all works anticipated to arise from investigating the
application to connect and preparing the associated offer to connect. This should
include additional capital cost related to the new connection, and to make the
connecting transmission system at par with the system before the connection.
ii. (ii) If one or more Code Participants are already connected to the proposed
Point of Connection, the new Connection may affect quality of supply to other
Code Participants. The cost required to mitigate such effects shall be estimated
by the System Operator and the applicant shall pay this cost at time of
submission of its application. The cost shall be paid at the time of issuance of
demand note.
iii. iii) If the applicant wishes to be connected to the National Transmission
System, the connection shall be of in-out arrangement. If the transmission line is
loaded near its operating limits and expected to affect the quality of supply of
the bulk power system, the applicant shall bear the full cost of upgrading the
transmission system needed as a consequence of yhe new connection. The cost
shall be paid at the time of issuance of demand note.
The System Operator shall use its reasonable endeavor to advise the applicant of all risks
and obligations in respect of the proposed connection associated with planning and
compliance with environmental laws of the Environmental Protection Agency (EPA) of
Pakistan not contained in this Code
The costs of assets (these assets do not include the existing assets of Transmission
Connection Points) at the Point of Connection including material, civil works, cost of land and
other ancillary costs shall be borne by the applicant. However, the System Operator shall
provide a preliminary cost estimate for the new connection.
CC.F.1.3 Application for Connection or Modification
On receipt of "Offer for Connection" from System operator, the applicant must submit the
formal application within 30 business days from the date of offer for connection. The
application must accompany the following information for evaluation of the System
Operator.
(a) Technical and commercial feasibility report;

(b) Detailed design of the facility that the applicant intends to install;
OC-1 138
(c) A final committed implementation schedule showing proposed milestones for
construction and commissioning of the applicant's facilities;
(d) Fees for registration and connection to the network;
(e) Details of the protection arrangements and relay settings;
(f) Copies of all safety rules and local safety instructions applicable at applicant's Sites;
and
(g) Power quality monitoring mechanism
If the System Operator considers that the applicant's proposed connection may possibly
adversely impact the networks of other Code Participants or Users, the affected Code
Participants and Users shall also be invited to evaluate the impacts and negotiate an
agreement with the applicant.
The applicant shall pay registration and connection fees to the System Operator; and the
remaining information and data required should be submitted to the System Operator as
soon as possible.
(Note: If the applicant is seeking connection to a distribution company, the distribution

company shall carryout preliminary evaluation of the application and if the application is in
line with the policies and technical criteria as outlined in the Grid Code and Distribution
Code, it shall send its concurrence to the System Operator to allow Connection with its
System. The System Operator shall evaluate the application with reference to its
obligations under the Transmission Licence and process the application of the applicant
who is seeking connection to the distribution company's system).
If the applicant wants to have multiple Points of Connections to the National Transmission
System, it should include all the Point of Connections in the same application; however, the
term and conditions for each Point of Connection may vary in accordance with the
conditions prevailing at each Point of Connection.
The System Operator shall evaluate this application and its contents within 30 business
days (final evaluation time period), and then invite the applicant to have negotiations for a
CC.F.1.4 Connection agreements
All the information forming basis of terms and conditions of the Connection Agreement for
"Connection and Use-of-System" must be supplied by the applicant to the System Operator
prior to completion date of the Agreement. Such information as listed below is referenced
here for guidance but not limited to:
(a) updated Planning Data as specified in the Planning Code with estimated values being
confirmed or replaced with validated actual values and updated Forecast Data such as
Load Demand pursuant to the Planning Code;
(b) details of the protection arrangements and settings referred to in the relevant Sections
of CC 5.4 below;
(c) copies of all safety rules and local safety instructions applicable at the User's Sites
which will be used at the System Operator/User interface. These instructions must be to
the satisfaction of the System Operator as set out in OC 9, CC 5.4 below;
(d) Information to enable the System Operator to prepare Site Responsibility Schedules on
the basis set out in the relevant sections of CC 5.4, and Appendix A of this sub-code;
(e) an Operation Diagram for all HV Apparatus on the User side of the Transmission
Connection Point as specified in CC 5.4, and Appendix B of this sub-code;
(f) the proposed name of the User Site, which shall not be the same as the name of any
transmission network Site, or any other User Site;
(g) written confirmation that the Safety Coordinators acting on behalf of the User are
authorised and competent pursuant to the requirements of OC 9, and relevant sections
of CC 5.4;
(h) a list of Managers who have been duly authorised to sign Site Responsibility Schedules
on behalf of the User;
(i) information to enable the System Operator to prepare Site Common Drawings;
OC-1 139
(j) a list of the telephone numbers for the User's facsimile machines; and
(k) the System Operator shall provide written confirmation to the User that the Safety
Coordinators acting on behalf of NTDC are authorised and competent pursuant.
On receipt of an "Offer to Connect" to the National Transmission System, the applicant

(Other than a Consumer):
(a) Must apply for a respective NEPRA licence to operate as a Generator or a distribution
company or Special Purpose Transmission Licence (SPTL);
(b) Must register with NTDC to operate as a Code Participant.
(c) Must agree to comply with all the provisions of the Grid Code, and Distribution Code (if
applicable).
(d) Must abide by all related rules and regulations already issued or to be promulgated in
the future by the GOP or the relevant authorities.
(e) Must agree to abide by all bindings, which are set out by the environmental agencies.
the System Operator shall inform NEPRA that a Connection Agreement has been entered
into between them, and forward to NEPRA relevant technical details of the proposed plant,
apparatus, facilities and connection, including the proposed metering installation and the
terms upon which a Code Participant is to supply any ancillary services under its
CC.F.1.5 Connection arrangements for generators
The System Operator is required under its licence to process a connection application or to
make an offer to connect for the provision of transmission network services to the
Generator.
The Generator shall follow the same procedure for seeking connection to the NTDC
Transmission System as mentioned in CC 4. However, as a basis for negotiation for the
connection agreement, the Generators:
(a) must provide to the System Operator such information as is reasonably requested
relating to the expected operation of its Generating Units; and
(b) the System Operator must provide to the Generator such information as is reasonably
requested to allow the Generator to fully assess the commercial significance of the
connection arrangements sought by the Generator.
A Generator may seek its Open Access arrangements at any level of power transfer
capability between zero and the maximum power injection into the National Transmission
System of the Generator' Registered Capacity.
the System Operator shall make arrangements to provide connection to the Generator to
its Transmission System. However, the costs of establishing the connection at the Point of
Connection shall be borne by the Generator.
The augmentation or the required extensions of the affected transmission networks to

provide appropriate transfer capabilities to other Code Participants with the new connection
in place shall be carried out by the System Operator; and the costs incurred for such works
shall be reflected in the transmission tariff of the System Operator.
The Generator shall post a performance bond in the name of the System Operator, in an
amount equal to the estimated the System Operator cost to construct new facilities needed
for the connection of the Generator. The bond shall be returned to the Generator upon
successful commercial operation of the Generator's facilities. If the Generator fails to bring
its project to commercial operation, then the System Operator shall collect the performance
bond.
Other procedures and requirements for intent application, offer to connect to the network,
preparation of connection application, evaluation of application and the Connection
Agreement shall be according to the Connection Code of the Grid Code.
OC-1 140
DISCO NTDC APPLICANT
Evaluate the
Evaluation Prepare
Application
with respect Intension
Preliminary
to Grid Code Application
Evaluation
Submit Intension
Application to NTDC
and DISCO
Simultaneous
Comments
Provide Additional
Information if Required
Offer for Connection
Submit Formal
Application for
Connection
Final Evaluation of
Application
Prepare Negotiation Negotiation Prepare Negotiation
Connection Agreement Connection Agreement
Comments on
Metering and
Protection
Make connection
End of CC
OC-1 141
OPERATION CODE NO. 1
OPERATING – OBJECTIVES AND PRICIPLES
CONTENTS
OC 1.1. INTRODUCTION......................................................................... 143
OC 1.2. OPERATING PRINCIPLES............................................................. 143
OC-1 142
OC 1. OPERATION CODE NO. 1
OPERATING OBJECTIVES AND PRINCIPLES
OC 1.1. INTRODUCTION
The Operating Code specifies the Technical and Operating Criteria, and Procedures
to be followed by the Transmission Network Operator (TNO) and the System
Operator (SO) and Code Participants in the operation of the power system. The
System Operator2 shall be responsible for the safe, openly-accessible, cost-effective,
equitable, environmentally acceptable and reliable operation and development of
the power system. The Code Participants shall have the obligation to cooperate with
the TNO and the SO and follow the technical, design, and operation Criteria and
Procedures as identified in this Grid Code necessary for an appropriate and stable
operation and protection of the power system.
The functions and responsibilities of the System Operator are subject to the
conditions as specified in the System Operator licence, and includes Operation,
Control and Discipline of the National bulk transmission system (as defined below):
(a) Means one or more systems comprising electrical facilities including, without
limitation, electrical wires or circuits, electrical plant, transformers, sub-
stations, switches, meters, interconnection facilities or other facilities
operating at or above minimum transmission voltage constructed, owned,
managed, controlled or operated by the Licensee or by one or more special
purpose transmission licensees and used for transmission of electric power
from the generation facility to sub-stations or to or from other generation
facilities or between sub-stations or to or from any interconnection facilities or
from the distribution facilities of one licensee to the distribution facilities of
another licensee or from a generation facility to a distribution facility or a
bulk-power consumer. The Operating Code describes the procedures by which
the System Operator shall carry out its responsibilities along with its
performance obligations.
OC 1.2. OPERATING PRINCIPLES

The System Operator shall prepare an Operating Plan prior to bringing scheduled
generation on-line for the next day to meet the forecasted load demand. Procedures
for implementation of the Plan are described in the Scheduling and Dispatch Code.
The Operating Plan shall include the following Operating Principles:
(a) Adequate margins for operating reserve, voltage regulation and frequency
control must be ensured at all times under normal system conditions.
(b) Generation and Transmission facility outage co-ordination and assessment of

system security impacts should be carried out prior to real-time operations.
(c) Frequency control and regulation requirements must be provided by power

system Users, suitable generators, energy storage plants and external
Consumers & Parties if designed to provide frequency control.
(d) Transmission congestion management and contingency event management

must be provided in accordance with the Operating Criteria and Principles laid
down in the Operating Sub-Code (OC 4) of this sub-code.
(e) Appropriate and fair spinning reserve allocation must be made among all the
on-line generators, energy storage plants and external Consumers & Parties if
designed to provide reserve.
2
The term System Operator refers to the system control functions being performed by the National Power Control Centre processor WAPOA system
as defined in the NTDC licence
OC-1 143
(f) Adequate reactive reserve management and voltage regulation must be
carried to meet the Operating Standards stated in OC 4.9.1 of this Code.
(g) Procurement of adequate Ancillary Services must be ensured prior to real-

time operations.
(h) Re-dispatch for transmission considerations must be carried by the System

Operator , after generation scheduling process done by the Central Power
Purchasing Agency (CPPA G), if power system security is not fulfilled .
(i) Provision of adequate generation protection and control based on the

principles laid down in Protection & Metering Code (PMC) must be provided by
the TNO.
j) Functioning of dual communication systems during system operation and

dispatch must be ensured by the System Operator/Grid Code Participants.
(k) Provision of pre-operational plans regarding black start facilities and pre-
tested system restoration plan under black out conditions must be ensured by
the System Operator.
(I) Minimization of energy imbalances at all times must be ensured by the

System Operator.
(m) The System Operator must ensure that all the thermal loadings, voltages,
system stability (both steady-state and dynamic) are well within established
limits as provided in the Operating Code 4 of this sub-code.
END OF OC 1
OC-1 144
DEMAND FORECASTS
CONTENTS
OC 2.1. INTRODUCTION, OBJECTIVE & SCOPE............................................................. 146
OC 2.2. DATA REQUIRED BY NTDC & MARKET IN THE PRE-OPERATIONAL STAGE...........147
OC 2.3. POST CONTROL PHASE.................................................................................. 148
OC 2.4. DATA REQUIRED BY NTDC & MARKET FOR THE OPERATIONAL STAGE...............149
OC-2
DEMAND FORECASTS
OC 2.1. INTRODUCTION, OBJECTIVE & SCOPE
OC 2.1.1. This sub-code is concerning Demand Forecasting as related to Operational

Timescales with the specific objective of ensuring that the highest levels of
security of power supply are maintained for Consumers at all times. The scope
of this sub-code applies to all Users connected to the Transmission System,
i.e. Generators, Distribution Companies and Consumers directly connected to
the National Transmission System, and other Parties consuming power from
the National Transmission System.
OC 2.1.2. This sub-code covers Active Demand and Reactive Demand forecasts which
are necessary to match generation output with generation variation and
forecasted system energy requirements
OC 2.1.3. Four phases are recognised in system operation: Pre-Operational Stage, the
Operational Stage, the Control Stage and the Post Control Stage
OC 2.1.4. In this OC.2 deals with the provision of data on Demand Control in the Pre-
Operational Stage, the Operational Stage, the Control Stage and the Post
Control Stage.
OC 2.1.5. In Pre-Prerational Stage, demand forecasting shall be consolidated/developed
by the Market Operator (MO)on the basis of demand and generation variation
forecasts provided by individual Users, see PC.3.
OC 2.1.6. For Operational Stage, System operator shall conduct its own demand
forecasting taking into account information supplied by all the Users, and any
other external factors that it may deem necessary
OC 2.1.7. In this OC 2, the Points of Connection of Users, Generators, Consumers and
External-connected parties shall be considered as a Transmission Connection
Points.
OC 2.1.8. In this OC 2, Year O means the current Calendar Year at any time, Year 1
means the next Calendar Year at any time, Year 2 means the Calendar Year
after Year 1 and so on.
OC 2.1.9. References in OC 2 to data being supplied on an hourly basis refers to it being
supplied for each period of 60 minutes ending on the hour
OC 2.1.10. The reference in this OC.1 to a “day” shall mean the period covered by the
Trading Day, even though that may not be a calendar day.
The objectives of OC.1 are to:
OC 2.1.11. Ensure the provision of data to the SO and MO by Users in the Pre-Operational
Stage, the Operational Stage, Control Stage and Post Control Stage; and
OC 2.1.12. Describe the factors to be taken into account by the SO when Demand
forecasting in the Operational Stage and Control Stage.
OC 2.1.13. The term 'Operations' means Operational Stage
The scope of this Code applies to all NTDC Transmission System Users, i.e.
r) NTDC;
s) All Generators connected at the Transmission system
t) Generators with capacity greater than 10 MW;
u) DISCOs;
v) Transmission-connected Consumers; and
w) Externally Connected Consumers/Parties, like
OC-2
22. Aggregators
OC 2.2. DATA REQUIRED BY NTDC & MARKET IN THE PRE-OPERATIONAL STAGE
OC 2.2.1. The data is to be supplied to NTDC & the Market Operator by:
Each User directly connected to the National Transmission System in relation
to Demand Forecast.
For year 1 the following data shall be supplied in writing to the Market
Operator by calendar week 40. in year 0:
(a) The DISCOs, Demand Customers, External connected Consumers &
Parties shall supply typical profiles of the anticipated Demand (averaged
over any half hour on any Grid Supply Point) on half hourly and Grid
Supply Point basis for defined categories of day type as determined by
the MO;
(b) The DISCOs, Demand Customers, External connected Consumers &

Parties shall supply MW profiles of the amount and duration of
anticipated Demand Control which may result in a Demand change of
10MW or more (averaged over any half hour on any Grid Supply Point)
on half hourly and Grid Supply Point basis;
(c) The DISCOs and External connected Parties shall supply typical MW
profiles for the operation, or Availability as appropriate, of Embedded
Generation where the total Registered Capacity of Generating units
on a single Site exceeds 10MW for defined categories of day type as
determined by the SO. The method for submitting MW schedules and/or
Availability shall be agreed between the SO and the DISCOs, External
connected Parties, such agreement not to be unreasonably withheld;
(d) Notwithstanding OC.1.4.2(c), if the SO considers the Site to be critical for

Transmission System operation, SO may request the DISCOs,
External Parties typical MW profiles for the operation, or Availability as
appropriate, of Embedded Generation where the total Registered
Capacity of Generating units on a single Site exceeds 5MW, for
defined categories of day type as determined by the SO.
(e) The method for submitting MW schedules and/or Availability shall be

agreed between the SO and the DISCOs and External connected
Parties, such agreement not to be unreasonably withheld.
OC 2.2.2. The DISCOs, Demand Customers, External connected Consumers & Parties
shall inform the MO & SO of any changes to the information supplied under
OC.1.4.2 as soon as this information is available. This information will be
provided In Writing, or as otherwise agreed between the DISCOs, Demand
Customers, External connected Consumers & Parties and the MO & SO, such
agreement not to be unreasonably withheld.
(a) In particular, the DISCOs and Demand Customers, External
connected Consumers & Parties shall provide to the MO & SO In
Writing information pertaining to new connections greater than
2MW immediately this information is available. This information must
OC-2
include anticipated connection date, location of connection, size of
connection category of connection (e.g. residential, industrial etc.)
and the typical profiles of the anticipated Demand on half hourly
basis for defined categories of day type as determined by the SO;
(b) In particular, the DISCOs, Demand Customers, External connected
Consumers & Parties shall provide to the MO & SO In Writing
information pertaining to disconnection of existing Demand
immediately this information is available. This information must include
anticipated disconnection date, location of connection, size of
connection, and the revised typical profiles of the anticipated Demand
on a half hourly basis at the Grid Supply Point for defined categories
of day type as determined by the SO;
OC 2.2.3. On the 5th last Business Day of every month the DISCOs, Demand Customers,
External connected Consumers & Parties shall verify In Writing that the most
recently submitted MW Demand profiles for the following two months are in
accordance with their current best estimate of these values.
OC 2.3. POST CONTROL PHASE
The following is required by the SO In Writing (or by such electronic data

transmission facilities as have been agreed with the SO) by 14.00 hours each
day in respect of Active Power data and Reactive Power data:
a) MW profiles for the previous Trading Day of the amount and duration
of Demand reduction achieved from the use of Demand Control of
10MW or more (averaged over any half hour on any Grid Supply
Point), on a half hourly and Grid Supply Point basis, from the
DISCOs, Demand Customers, External connected Consumers &
Parties;
b) MW profiles of the amount and duration of Demand reduction achieved

from the use of Customer Demand Management of 10MW or more
on a half hourly basis during the previous Trading Day, Demand
Customers, External connected Consumers & Parties;
c) Details of half hour Active Power output and Reactive Power

produced or absorbed by Embedded Generation, with a single Site
with Registered Capacity in excess of xxxMW, during the previous
Trading Day, from the DISCOs, Demand Customers, External
connected Consumers & Parties;
d) (Where requested by the SO), details of half hour Active Power output
and Reactive Power produced or absorbed by Generation Plant
during the previous Trading Day, from Generating Units Plants,
DISCOs, Demand Customers, External connected Consumers &
Parties.
OC 2.4. DATA REQUIRED BY NTDC & MARKET FOR THE OPERATIONAL STAGE
OC 2.4.1. For a period of 4 weeks ahead of the real-time day, the following shall be
supplied to Market Operator in writing by 10.00 a.m. each Monday. The 4-
week period is a rolling period.
Demand Management
OC-2
Each distribution company and other Code Participants (as instructed by the
Market Operator) shall supply MW profiles, in relation to their peak demand, of
the amount and duration of their proposed use of demand management which
may result in a demand change of xx MW or more on any Transmission
Connection Point (averaged over an hour which may be changed later by the
Authority to ½ hourly basis).
OC 2.4.2. For the period of up to eight (8) days ahead of the real-time day, the following
shall be supplied to the System Operator in writing by 10:00 a.m. each
Wednesday.
Demand Management
Each distribution company and other Code Participants (as instructed by the
System Operator) shall supply MW profiles, in proportion to their peak
demand, of the amount and duration of their proposed use of demand
management which may result in a demand change of 5MW or more
(averaged over an hour which may be changed by the Authority to ½ hourly
basis) on any Transmission Connection Point. The quantum of load to be shed
by each Distribution Company shall be at the discretion of the System
Operator. However, the System Operator shall carryout Load Management in
fair manner.
OC 2.4.3. Each Generating Unit shall, if required , supply the System Operator with MW
schedules for the operation of Generating power plants on an hourly basis in
writing by 10.00 a.m. each day (or such other time specified by from time to
time) for the next day.
OC 2.4.4. Under OC 3, each distribution company and other Code Participants as
specified by the System Operator shall notify the System Operator of any
demand management proposed by itself which may result in a demand
change of 5MW or more averaged over an hour on any Transmission
Connection Point which is planned after 10.00 a.m. on an operational day, and
of any changes to the planned demand management notified to the System
Operator prior to 10.00 a.m. as soon as possible after the formulation of the
new plans.
OC 2.4.5. Generation from RES (renewables) and IPP shall, if required, supply the
Market/System Operator with MW schedules for the operation of power plants
on an hourly basis in writing by 10.00 a.m. each day (or such other time
specified by the System Operator from time to time) for the next day.
OC 2.4.6. Interconnectors shall supply the Market/System Operator with MW transfer
power schedules for the operation of power plants on an hourly basis in writing
by 10.00 a.m. each day (or such other time specified by the System Operator
from time to time) for the next day.
OC 2.5. DEMAND FORECAST

OC 2.5.1. Demand forecast shall be done by CPPA G (Market Operator) in cooperation
with NTDC with the data given from DISCOs, Demand Customers, External
connected Consumers & Parties.
The following additional factors will be taken into account by the SO when
conducting
Demand forecasting in the Operational and Control Stage:

(a) Historic Demand data;
(b) Weather forecasts and the current and historic weather conditions;
(c) The incidence of major events or activities which are known to the SO in
OC-2
advance;
(d) Transmission System losses;
(e) Embedded Generation;
(f) Demand Control of xxMW or more (averaged over any half hour at any
Grid Supply Point) proposed to be exercised by the DSO and of
which the SO has been informed,
(g) Customer Demand Management of 10MW or more (averaged over

any half hour) proposed to be exercised by Suppliers and of which the
SO has been informed,
(h) Other information supplied by Users, and
(i) Growth rates.
OC 2.5.2. Taking into account the factors specified in OC.1.6.1 the SO uses Demand
forecast methodology to produce forecasts of Demand.
OC 2.5.3. The methodology will be based upon factors (a), (b), (c) and (d) above to
produce, by statistical means, unbiased forecasts of Demand including that to
be met by Embedded Generation. Demand will be calculated from these
forecasts but will also take into account factors (e), (f), (g), (h) and (i) above.
End of OC 2
OC-2
DEMAND MANAGEMENT
CONTENTS
OC 3.2. CODE CLARIFICATION.................................................................................... 152
OC 3.3. OBJECTIVE.................................................................................................... 154
OC 3.4. SCOPE.......................................................................................................... 154
OC 3.5. PROCEDURE FOR THE NOTIFICATION OF DEMAND MANAGEMENT INITIATED

BY DISTRIBUTION COMPANIES (OTHER THAN FOLLOWING THE
INSTRUCTIONS OF THE SYSTEM OPERATOR)................................................... 154
OC 3.6. PROCEDURE FOR THE IMPLEMENTATION OF DEMAND MANAGEMENT ON

THE INSTRUCTIONS OF SYSTEM OPERATOR.................................................... 154
OC 3.7. AUTOMATIC LOW FREQUENCY DEMAND DISCONNECTION................................ 156
OC 3.8. AUTOMATIC FREQUENCY RESTORATION......................................................... 157
OC 3.9. VOLTAGE DEMAND DISCONNECTION.............................................................. 158
OC 3.10. EMERGENCY MANUAL DISCONNECTION........................................................ 159
OC 3 APPENDIX 1- EMERGENCY MANUAL DEMAND REDUCTION/DISCONNECTION

SUMMARY SHEET...................................................................................................... 160
OC-3
DEMAND MANAGEMENT
OC 3.1. INTRODUCTION, OBJECTIVE & SCOPE
OC 3.1.1. Operation Code No. 3 (OC 3) deals with the provisions to be made for the
power system Users by the DISCOs, Demand Customers, External connected
Consumers & Parties and, by the SO to permit the reduction of Demand in the
event of:
a.available Generating Plant and transfers from External

Interconnections being insufficient to meet Demand, or
b. breakdown or operating problems such as in respect of System
Frequency, Voltage levels or Thermal Overloads on any part of the
The Demand Control arrangements may also apply where there are
insufficient Generating Plant or transfers to meet Demand in all or any
part of the Other Transmission System and/or in the event of problems
on the Other Transmission System, within the limits of the contractual
agreement for external assistance, in circumstances where the SO is able
to assist the Other SO and where doing so would not have a detrimental
effect on the security of the Transmission System.
OC 3.1.2. The objective of OC 3 is to provide facilities and procedures which shall enable
the Transmission Network Operator to achieve a reduction in demand that will
relieve planned and unforeseen operating conditions on the National
OC 3.1.3. OC3 applies to the Transmission Network Operator and to Users:
a. Distribution Companies;
b. Transmission Network Operator in relation to Consumers directly
connected to the National Transmission System; and
c. Externally Connected Consumers/Parties, like
i. Special Licensee Transmission Company
ii. Provincial Companies
iii. Interconnector Operators
iv. Aggregators
v. Independent Power Producers (IPP)
vi. Demand Customers
OC 3.2. CODE CLARIFICATION
OC 3.2.1. Demand Management may be achieved by any of the following:
a. Aggregated Demand Site reduction instructed by the SO

b. Customer Demand/Aggregated Demand Site reduction instructed by the
SO;
c. Customer Demand/Aggregated Demand Site reconnection instructed by
the SO;
d. Automatic low Frequency Demand Disconnection;
e. Automatic low Voltage Demand Disconnection; and
f. Automatic Frequency Restoration.
The term “Demand Control” is used to describe any or all of these methods of
achieving Demand reduction, or in the case of (b) and (e), a Demand increase.
OC-3
OC 3.2.2. In all situations considered in OC 3, demand management is exercisable by
NTDC by means of:
a. DISCOs
b. Aggregators
c. Interconnector
d. Special Licensee and Provincial Companies
e. By reference to distribution companies’ system directly connected to
the National Transmission System; and
f. by Transmission Network Operator in relation to Consumers directly
connected to the National Transmission System
OC 3.2.3. Demand management in emergency situations relates to the physical
organisation of the Total System Demand, and not to any contractual
arrangements.
OC 3.2.4. The procedures set out in OC.5 includes a system of Alerts, issued to Users, to
give advance notice of Demand Control that may be required by the SO under
this OC.3.2.1.
OC 3.2.5. Data relating to Demand Control shall include details relating to MW.
OC 3.2.6. Demand Control shall not, so far as be possible, be exercised in respect of

Priority Customers. OC.5, therefore, applies subject to this exclusion.
OC 3.2.7. Notwithstanding OC.3.2.6, Demand Control shall be exercised equitably in

respect of Customers connected to the Distribution System, Demand
Customers, Special Licensee Company and Provincial Companies.
OC 3.2.8. Explanation
OC 3.2.8.1. Demand Control is exercised through operation of the Distribution

System, Special Licensee Company and Provincial Companies. or of the
Transmission System (in the case of Demand Customers). Demand
Control relates to the physical organisation of the total System, and
not to any contractual arrangements that may exist. Where Demand
Control is needed in a particular area, the SO would not know which
Supplier to contact and (even if it were to) the resulting Demand
Control implemented, because of the diversity of contracts, may not
produce the required result.
OC 3.2.8.2. Demand management shall be implemented by distribution, Special

Licensee and Provincial Companies. where the Consumers are within
their own systems which are directly connected to the National
Transmission System; and by Transmission Network Operator where
Consumers are directly connected to the NTDC transmission System.
OC 3.2.8.3. In most instances of Demand Control, Demand Control will be

exercisable by the DISCO, Special Licensee and Provincial Companies
and may impact other Consumers of the distribution company within
its geographical boundary. Suppliers should note, however, that,
although implementation of Demand Control in respect of their
Customers may not be exercisable by them, their Customers can be
affected by Demand Control.
OC 3.3. OBJECTIVE
OC 3.3.1. The overall objective of OC.3 is to require the provision of facilities by DISCOs,
Demand Customers, External connected Consumers & Parties to enable the
SO to achieve the reduction in Demand that will either avoid or relieve
OC-3
operating problems on the Transmission System, and subject to the
circumstances set out in OC.3.1.1, the Other Transmission System, in whole or
in part, and thereby to enable the SO to instruct Demand Control in a manner
that does not unduly discriminate against, or unduly prefer, any one or any
group of Users. It is also to ensure that the SO is notified of any Demand
Control utilised by Users other than following an instruction from the SO.
OC 3.4. SCOPE
OC.3 applies to the SO and to all Users, which term in this OC.3 means:
a) The Distribution System Operator;
b) Suppliers;
c) Transmission-connected Consumers; and
d) Externally Connected Consumers/Parties, like:
4. Aggregators
6. Demand Customers
OC 3.5. PROCEDURE FOR THE NOTIFICATION OF DEMAND MANAGEMENT INITIATED BY

DISTRIBUTION COMPANIES (OTHER THAN FOLLOWING THE INSTRUCTIONS OF THE
SYSTEM OPERATOR)
OC 3.5.1. By 10.00 a.m. of each day, distribution companies and other Code
Participants, as specified by the System Operator, shall provide the System
Operator with a summary of any demand reductions of 5MW or greater during
the last 24 hours, and of any planned demand reductions within the next 24
hours.
OC 3.5.2. Any changes from the planned demand management shall be communicated
to the System Operator as soon as possible.
OC 3.5.3. In the above the summary of planned or historic demand reductions, the
information supplied to the System Operator shall include the magnitude,
time, location, date and details of the demand management methods
employed.
OC 3.6. PROCEDURE FOR THE IMPLEMENTATION OF DEMAND MANAGEMENT ON THE

INSTRUCTIONS OF SYSTEM OPERATOR
OC 3.6.1. Where a shortage of generation capacity or other reason for the exercising of
Demand Control is foreseen, the SO will alert the DISCOs, Demand Customers,
External connected Consumers & Parties by means of a Demand Control Alert.
OC 3.6.2. The System Operator shall provide as much warning as possible of any
unforeseen circumstances which are likely to result in demand management
procedures being implemented. This shall ensure that all the distribution
companies and all other relevant Code Participants shall be in a state of
readiness to implement their planned demand management procedures.
OC-3
OC 3.6.3. All the relevant Code Participants participating in the demand management
are required to be able to respond at a short notice to the System Operator
instructions to implement demand management.
OC 3.6.4. Where reasonable notice of the need for Demand Control is available, the SO
will initiate the Rota Load Shedding Plan and Demand Control will be
implemented in accordance with the Rota Load Shedding Plan. The SO, the
DISCOs, Demand Customers, External connected Consumers & Parties will
each be responsible for maintaining procedures and will co-operate with each
other so as to provide for the implementation of Demand Control in
accordance with the Rota Load Shedding Plan.
OC 3.6.5. Where the requirement for Demand Control arises at short notice, it may be
necessary for practical reasons to implement Demand Control other than in
accordance with the Rota Load Shedding Plan. The SO and the DISCOs,
Demand Customers, External connected Consumers & Parties will each
maintain procedures (and will co-operate in forming such procedures) to
provide that Demand Control can be exercised rapidly when required, in
accordance with the SO’s instructions.
OC 3.6.6. In the event of Demand Control being exercised other than in accordance with
the Rota Load Shedding Plan (due to reasons of short notice or otherwise), and
if the Demand Control is expected to be sustained, then the SO will arrange
for the Rota Load Shedding Plan to be implemented as soon as practicable.
The SO may instruct certain modifications in the application of the Rota Load
Shedding Plan to provide for those Customers which have been subject to
shedding in the initial phase prior to the initiation of Planned Rota Load
Shedding
OC 3.6.7. The Rota Load Shedding Plan provides for disconnection and reconnection of
defined blocks of demand on instruction from the SO, In this way the SO can
instruct the necessary level of disconnection (and reconnection) required by
the circumstances at the time. The DISCOs, Demand Customers, External
connected Consumers & Parties shall comply with instructions issued by the
SO in accordance with the Rota Load Shedding Plan, and in particular will not
reconnect Demand other than in accordance with the SO’s instructions.
OC 3.6.8. The Rota Load Shedding Plan shall also provide for the issue of information to
Customers through the media of the expected duration of Demand Control,
and which blocks of Customers are at most risk of disconnection at which
times.
OC 3.6.9. NTDC_SO, the DISCOs, Demand Customers, External connected Consumers &
Parties will maintain records of the disconnection and reconnection of
customers exercised under the Rota Load Shedding Plan, (and, for the
avoidance of doubt, of any Demand Control exercised in accordance with
OC.3.6.4).
OC 3.6.10. DISCOs, Demand Customers, External connected Consumers & Parties have
an obligation to provide full details of their demand reduction plans to the
System Operator on an annual basis ahead of time.
OC 3.6.11. The System Operator shall endeavour to limit demand reductions equal to the
loss of generation up to a maximum of 30% of the Total System.
Demand at the time of implementation of the demand reduction. The System

Operator shall, to the extent possible, formulate consistent and fair policy of
demand management among DISCOs and other Users.
OC 3.6.12. Following the implementation of demand management, distribution companies

and any Consumers directly connected to the National Transmission System
OC-3
may only restore their systems to normal operation upon the instructions of
OC 3.6.13. After restoration to normal operating conditions, distribution companies and

Provincial Companies are obliged to supply information to the System
Operator, which shall include the magnitude, date and time, location and
details of the demand management methods employed.
OC 3.7. AUTOMATIC LOW FREQUENCY DEMAND DISCONNECTION
OC 3.7.1. All Transmission Connection Points shall be provided with low frequency
disconnection facilities. This is necessary to ensure that in the event of a large
generating unit failure, there is a staged and phased demand disconnection to
ensure system stability for connected consumers.
OC 3.7.2. Any low frequency disconnection scheme must take into account of all
embedded generation on the low voltage systems of the distribution
companies.
OC 3.7.3. When there is a low frequency disconnection, distribution companies and

other Code Participants, as specified by the System Operator, are obliged to
follow the System Operator instructions when restoring power supplies.
OC 3.7.4. The DISCOs, Demand Customers, External connected Consumers & Parties
shall make arrangements that will enable automatic low Frequency
Disconnection of a percentage of its total peak Customer Demand (based on
xxxxxx) as specified by the SO, in order to seek to limit the consequences of a
major loss of Generation or an event on the total system which leaves part of
the total system with a Generation deficit, provided that, so far as possible,
Demand of Generating units which is required to enable the Generating units
to start-up shall not be subject to automatic low Frequency Disconnection. The
SO retains the right to specify the Frequency settings on percentages of
Demand subject to automatic low Frequency Disconnection.
OC 3.7.5. The DISCOs, Demand Customers, External connected Consumers & Parties of
which are subject to automatic low Frequency Disconnection will be split into
discrete MW blocks. The number, location, size and the associated low
Frequency settings of these blocks, will be as specified by the SO by week 40
in every three calendars year following discussion with the DISCOs, Demand
Customers, External connected Consumers & Parties and will be reviewed
every three years by the SO. The distribution of the blocks will be such as to
give reasonably uniform Disconnection within the Power systems of DISCOs,
Demand Customers, External connected Consumers & Parties across all Grid
Supply Points.
OC 3.7.6. Demand Customers shall provide automatic low Frequency Disconnection,

which will be split into discrete blocks. The number and size of blocks and the
associated low Frequency settings will be as specified by the SO by week 40
every three calendar years following discussion with the Demand Customers.
In the case of a User, it is not necessary for it to provide automatic low
Frequency Disconnection under OC.3.5 if it is providing low Frequency
Disconnection at a higher level of Frequency as an Ancillary Service.
OC 3.7.7. DISCOs, Demand Customers, External connected Consumers & Parties shall be
capable of automatic low Frequency Disconnection between 47 – 50 Hz.
OC 3.7.8. The proportion of demand subject to automatic low Frequency Disconnection

shall be agreed with SO. For Demand Customers, up to 30% of the Demand
may be made subject to automatic low Frequency Disconnection at the SO’s
direction.
OC-3
OC 3.7.9. The automatic low Frequency Disconnection scheme for a DISCOs, Demand
Customers, External connected Consumers & Parties shall be capable of
disconnecting Demand in stages for a range of operational frequencies. The
specifics performance requirements of the scheme shall be specified and
agreed with the SO.
OC 3.7.10. The automatic low Frequency Disconnection scheme shall allow for operation
from a nominal AC input to be specified by the SO, and shall meet the
following functional capabilities:
 Frequency range: at least between 47-50 Hz, adjustable in steps of

0.05 Hz;
 Operating time: no more than 200 ms after triggering the Frequency

setpoint;
 Voltage lock-out: blocking of the functional capability shall be possible

when the voltage is within a range of 20 to 90 % of reference 1 p.u.
voltage; and
 Provide the direction of active power flow at the point of disconnection.
The AC voltage supply used in providing these automatic low Frequency

Disconnection functional capabilities, shall be measured from the at the
Connection Point.
OC 3.8. AUTOMATIC FREQUENCY RESTORATION
OC 3.8.1. The DISCOs, Demand Customers, External connected Consumers & Parties will
make arrangements that will enable automatic Frequency restoration of
Demand that is subject to automatic low Frequency Demand Disconnection.
The SO retain the right to specify the Frequency settings on blocks of Demand
subject to automatic Frequency restoration.
OC 3.8.2. Once an automatic low Frequency Demand Disconnection has taken place, the
DISCOs, Demand Customers, External connected Consumers & Parties shall
not reconnect Customers until instructed by the SO, or otherwise in
accordance with agreed procedures.
OC 3.8.3. Where conditions are such that, following automatic low Frequency Demand
Disconnection, it is not possible to restore a large proportion of the total
Demand so Disconnected within a reasonable period of time, the SO may
instruct the DISCOs, Demand Customers, External connected Consumers &
Parties to implement additional Demand Disconnection manually, and restore
an equivalent amount of the Demand that had been Disconnected
automatically. The purpose of such action is to ensure that a subsequent fall in
Frequency will again be contained by the operation of automatic low
Frequency Demand Disconnection. If the requirement for Demand Control is
expected to continue for a sustained period of time, then the SO will initiate
the implementation of the Rota Load Shedding Plan in accordance with OC.3.6.
OC 3.8.4. Once the Frequency has recovered, the DISCOs, Demand Customers, External
connected Consumers & Parties will abide by the instructions of the SO with
regard to reconnection, and/or shall implement agreed procedures for
Demand reconnection, without undue delay.
OC 4.
OC 4.1. VOLTAGE DEMAND DISCONNECTION
OC 4.1.1. The SO may from time to time determine that there is a requirement for
automatic low Voltage Disconnection of Customer Demand, in order to limit
OC-3
the consequences of the loss of a Generating unit(s), or an event on the total
System, which otherwise would result in part of the total System with Voltages
outside the levels specified in xxxxx.
OC 4.1.2. The SO may exercise the required Automatic Low Voltage Demand
Disconnection (ALVDD) at the level of the Transmission System. However,
depending on the extent of ALVDD required, and in order not to disconnect
more Customer Demand than reasonably required in response to a specific
incident or set or circumstances, it may be preferable that ALVDD is carried
out at the level of the DISCOs, Provincial Companies, SPTLs, Demand
Customers, External connected Consumers.
OC 4.1.3. On request by the SO, the DISCOs, Demand Customers, External connected
Consumers & Parties will co-operate with the SO as to the design and
implementation of ALVDD at locations on the DISCOs, Provincial Companies,
SPTLs, Demand Customers, External connected Consumers, where the
requirement is indicated in accordance with OC.3.7.2. The SO will retain full
control over the enabling/disabling of the ALVDD, and the Voltage settings at
which ALVDD will be initiated in each circumstance. In general, the settings
will be specified by the SO by week 40 in every three calendars year following
discussion with the DISCOs, Provincial Companies, SPTLs, Demand Customers,
External connected Consumers, but the specification of settings may be
altered by the SO at other times to address specific circumstances pertaining
at the time. The DISCOs, Provincial Companies, SPTLs, Demand Customers,
External connected Consumers shall respond to any change in specification by
altering the settings without undue delay.
OC 4.1.4. The SO will specify the functional capabilities for low voltage demand
disconnection, where the SO identifies the need, in co-ordination with DISCOs,
Provincial Companies, SPTLs, Demand Customers, External connected
Consumers, on a site specific basis, and will include as a minimum: monitoring
voltage by measuring all three phases; and blocking of the relays operation
based on direction of either Active Power or Reactive Power flow.
OC 4.1.5. Low voltage demand disconnection shall be implemented automatically or

manually.
OC 4.1.6. The SO may specify the requirement for on-load tap changer blocking. DISCOs,
Demand Customers, External connected Consumers & Parties will be advised
as necessary, on a case-by-case basis, taking into consideration the site-
specific requirements.
OC 4.2. EMERGENCY MANUAL DISCONNECTION
OC 4.2.1. Each DISCOs, Demand Customers, External connected Consumers & Parties
shall provide the System Operator in writing by week 40 in each calendar
year, in respect of the next following year beginning week 40, on each
Transmission Connection Point basis the information contained in the
Appendix 1 of this sub-code.
OC 4.2.2. In the event of a System Emergency, irrespective of the frequency, the

System Operator may instruct DISCOs, Demand Customers, External
connected Consumers & Parties to disconnect demand at specific
Transmission Connection Points on an urgent basis. Quantum of load and
specific location of load reduction shall be at the discretion of the System
Operator depending on the conditions prevailing at that time. This action may
be necessary to protect life, limit plant damage and to maintain supplies to
the majority of Consumers. However, the System Operator shall fairly carry
out demand management according to OC 3.6.11.
OC-3
OC 4.2.3. The System Operator shall have a right of involuntarily disconnection of any
facility of the Code Participants in the case of system operational emergency
when it is determined by the System Operator that transmission system might
or could become incapable of providing the required services as mandated in
its licence.
OC 4.2.4. Distribution companies are obliged to comply with the System Operator
instructions when restoring supplies.
OC-3
OC 5. OC 3 APPENDIX 1- EMERGENCY MANUAL DEMAND REDUCTION/DISCONNECTION
SUMMARY SHEET
Name of Company/Code Participant/Transmission Connected Consumer:
Peak Demand [Year] MW
(132 & 66kV Radial Lines, 132/11kV & 66/11kV Transformers)
Transmission Peak % of Load Demand Reduction or Remarks

Connection (MW) Disconnection with respect to Duration of
Point Peak MW at the Transmission Load
Connection Point (%) Management
(Hours)
Note: Data to be provided annually by week 40 to cover the following calendar year.
End of OC 3
OC-3
OPERATIONAL PLANNING
CONTENTS
OC 4.2. NETWORK BOUNDARIES OF EXISTING DISTRIBUTION COMPANIES....................163
OC 4.3. OUTAGE CO-ORDINATION.............................................................................. 164
OC 4.4. PLANNING OF GENERATION OUTAGES............................................................ 165
OC 4.5. PLANNING OF TRANSMISSION SYSTEM OUTAGES............................................ 167
OC 4.6. CHANGES TO THE COMMITTED OUTAGE PROGRAMME WITHIN THE

IMPLEMENTATION YEAR (YEAR 0).................................................................. 169
OC 4.7. OTHER INFORMATION TO BE NOTED ABOUT ANCILLARY SERVICE

PROVISION................................................................................................... 170
OC 4.8. DATA REQUIREMENTS................................................................................... 171
OC 4.9. INSUFFICIENT POWER OPERATING MARGIN.................................................... 172
OC-4
OPERATIONAL PLANNING
OC 4.1 INTRODUCTION, OBJECTIVE & SCOPE

Secure operation of an electricity system requires that maintenance of production facilities
(Generating units, Interconnectors, Aggregated Generating Units and Aggregated Demand
Units, DISCOs, Provincial companies, SPTLs) should be carried out in a timely and orderly
fashion. This is essential in order to enable the SO to fulfil its obligations relating to operation
of the Transmission System, and to enable DISCOs, Generating units, Interconnectors,
Aggregated Generating Units and Aggregated Demand Units, Provincial companies, SPTLs to
plan their Outages in an orderly way with due regard to Plant requirements and resource
limitations. The mechanisms by which this is achieved are formalised in this Operational
Planning Code.
Operating Code No. 4 details the information including procedures required by the
System Operator and Users to ensure efficient co-ordination and harmonisation of the
dispatch of all Generation facilities, and User's obligations to enable the National
Transmission System to operate under normal and emergency conditions, and/or
during construction, repair and maintenance outage periods.
The primary objective of OC.2 is to promote the development and implementation of

a co-ordinated Generation Outage Programme (GOP), consistent with security of
supply and requirements for the secure and economic operation of the Transmission
System and the Other Transmission System, and with the needs of Generators,
Interconnector Operators, External Connected Parties, Generator Aggregators, or
Demand Side Operators in respect of Plant maintenance requirements and resource
limitations.
In order to achieve this objective, OC.4 defines:

(a) the procedure for formal notification of Outages by Generators,
Interconnector Operators, External Connected Parties,
Generator Aggregators or Demand Side Operators, to the SO;
(b) the procedures by which the Long, Medium and Short Outage
Programmes are reviewed by the SO, in consultation with
Generators, Interconnector Operators, External Connected
Parties, Generator Aggregators or Demand Side Operators
(c) the co-ordination of Outage planning and the interchange of Outage
schedules with the Other SO; and
(d) the procedure for formal notification by Generators, Generator

Aggregators, Externally Connected Parties or Demand Side
Operators of:
• a decision to cancel a major Outage of a Generating Unit;
• the findings during or following a major Outage of a

Generating Unit;
• an unexpected and unplanned failure of a Generating Unit.
OC.2 shall apply to all proposed Outages that may affect the ability of a
Generators, Interconnector Operators, External Connected Parties, Generator
Aggregators or Demand Side Operators to achieve, in accordance with its
Registered Operating Characteristics, either its full Registered Capacity,
appropriate to each Registered Fuel, Interconnector Registered Capacity or its
Demand Side Unit MW Capacity as the case maybe.
OC-5 162
OC.2.7 also requires Generators, Interconnector Operators, External
Connected Parties, Generator Aggregators or Demand Side Operators to
inform the SO of other proposed maintenance of a Generating unit,
Interconnector, Aggregated Generating Unit, Demand Side Unit or any
associated Plant or Apparatus, where such maintenance will affect the
availability of Ancillary Services in respect of that Generating Unit.
OC 4.1.1. To plan ahead, Operational Planning is required for several timescales. . The
data provided by CPPA G is communicated to the System Operator. The system
operator shall review the proposed generating dispatch, regarding active and
reactive power balance as well as transmission bottlenecks, to assure that the
Standards of Security of Supply as set out in this Code.
OC 4.1.2. The scope of this Code applies to all Grid Code participants, i.e.
(a) National Transmission System Operator and Dispatch Company, CPPA
G (Market Operator);
(b) Generators;
(c) Distribution Companies;
(d) Transmission Connected Consumers;
(e) Externally-connected Consumers; and
(f) Externally Connected Parties, like

4. Aggregators
OC 4.2 NETWORK BOUNDARIES OF EXISTING DISTRIBUTION COMPANIES
Restructured Network
The Transmission Network Operator shall operate the assets of entire Ultra High
Voltage AC 1100KV and 765KV, High Voltage AC 500kV and 220kV and High Voltage DC
1100KV, 800KV, 660KV, 500KV transmission and substations.
The Transmission Network Operator owns and maintains assets at 1100 kV, 765 kV,
500KV, 220KV transmissions and substations, 66kV AC voltages at 220/66KV Nishatabad
grid and 132kV at all 220/132kV grids. Furthermore, Transmission Network Operator
maintains some of the 132kV transmissions lines connecting with WAPDA hydel power
plants and IPPs assets.
All Code Participants, including generation connected to 132/66 kV network shall be

connected to the National Transmission network; and embedded generation shall be
connected to the bulk power system through the DISCO's 11kV distribution network.
The DISCOs, Provincial and Special Transmission licensee Companies shall own and
operate the assets of 132kV and 66kV sub-transmission lines, 11kV primary
distribution network and 400V, secondary distribution system located in their
defined Service Territories, and in conformance with the Territory specified in their
respective licenses.
OC 4.2.1. Bifurcation of network between National Transmission Network and

Generation Companies
The network bifurcation point between National Transmission System and a

Generator's substation shall be the line connections on the National Transmission
OC-5 163
System terminal structure at the Generator substation. The Transmission System
Operator's maintenance jurisdiction shall be up to the tension strings of the same
terminal structure towards the line side.
In case a Generator does not own a generating substation then the bifurcation
point shall be the line connection on the Generator's terminal structure. In this
case, the Transmission System Operator's maintenance jurisdiction shall be up to
the tension strings of the same terminal structure towards gantry side.
For the Generators connected to the 132/66 kV network of distribution companies,

the above Principle shall also apply. However, the maintenance shall be carried out
by the concerned distribution company after the approval of the System Operator.
OC 4.2.2. Bifurcation of network between the National Transmission Network

and Distribution Companies
The Network Bifurcation Point between NTDC and Distribution Companies shall be
the dropper from the terminal structure of 220 kV grid station to the licensee's
132kV or 66kV line, which shall also be the Connection Point for that Licensee. The
NTDC's maintenance jurisdiction shall be up to the tension strings of the same
terminal structure towards gantry side.
From those NTDC substations where 11kV feeders emanate which, in additional to
station auxiliary supply, also feed the Consumers of the respective distribution
companies, the point of bifurcation of such feeders shall be the jumpers of 11kV
power cable coming from outgoing panels and the 11kV distribution line at the
terminal structure.
Within next three years of the implementation of this Code efforts should be made
that the distribution companies shift their 11kV load from 220 kV Grid Stations to
132 kV stations of the distribution companies.
Bifurcation of Network between the Transmission Network and KESC
The network bifurcation point between the Transmission Network and KESC shall
be according to the principles established in "Interconnection Agreement" between
NTDC and KESC as and when finalized between the parties.
OC 4.2.3. Bifurcation of Network between the Transmission Network and

HVDC Interconnectors, Provincial and Special Transmission
Licensee Companies
The network bifurcation point between the Transmission Network and the
connected part shall be according to the principles established in "Interconnection
Agreement" between the transmission Network Operator and the connected part
as and when finalized between the parties.
OC 4.2.4. Point of Connection
These are points of Connection which shall be in conformance with clause (xiv) of
Section 2 of the NEPRA Act, which states the connection of one company’s
electrical facilities to another company’s electrical facilities. These are 220/132/66
kV substations where 132/66 kV lines originate into the User's network.
OC 4.3 OUTAGE CO-ORDINATION
OC 4.3.1. Outage Co-ordination
In order to ensure the uninterrupted, smooth and stable operation of the

National Transmission System, several Parties need to interact with each
other. In summary these are:
(a) Each Generator with the System Operator in respect of outages, plant defects,
availability etc.
OC-5 164
(b) The System Operator with respective Generator in respect of transmission
outages and constraints relevant to that Generator.
(c) The System Operator with respective distribution company/Provincial Special

Transmission Licensee Companies in respect of outages and constraints on the
transmission system, Power Plants, and at Transmission Connection Points.
(d) The System Operator with respective distribution company, Provincial, Special
Transmission Licensee Companies and each Transmission-connected Consumer in
respect of outages and constraints on the National Transmission System, power
plants, and at each transmission Connection Point relevant to that distribution
company and the transmission connected Consumer.
(e) Each distribution company, Provincial Companies Special Transmission Licensee

Companies and each transmission Consumer connected to the National
Transmission System in respect of User system outages relevant to System
Operator.
(f) Each External-connection Operator with the System Operator for outages and
constraints on their systems and vice versa.
(g) Each Interconnector with the system operator in respect of outages, plant defects,
availability etc.
(h) The System Operator with the Interconnector in respect of transmission outages
and constraints relevant to that Interconnector
OC 4.4 PLANNING OF GENERATION OUTAGES
Throughout OC.4.4 the current year shall be defined as year 0, the following year as year 1, and
so on. The Outage planning process in respect of a Generation Unit,
Interconnector, Aggregated Generating Unit and Demand Side Unit shall
commence not later than one (1) year prior to the Scheduled Operational Date
or from the date of the relevant agreements, whichever is the later.
OC 4.4.1. Short Term Planning (Year 0)
OC 4.4.1.1. In this Code, short term is the financial current year, or Year 0 of the Financial
Year. In rolling over the Generation Outage Programme from one year to the
next, for every year except the first year of the planning process, the basis for
Operational Planning for Year 0 shall be the revised Year 1 Final Generation
Outage Programme prepared by each Generator, Interconnector Operator,
Generator Aggregator, and/or Demand Side Unit Operator, and submitted to
the System Operator will be on the Financial Year basis.
OC 4.4.1.2. The closer the prepared outage programme is to real-time operations, the
more accurate it must be to ensure there is adequate generation to match
demand. There shall be several timelines whereby there shall be an exchange
of information, on a quarterly basis. between each Generator and the System
Operator. In each case the Generator is required to return their most up to date
outage proposals, thereby enabling the System Operator to plan generation
availability and forecast generation requirements. The precise timetable for the
provision and acknowledgement of this information is produced as Appendix 1
(P:45) of this sub-code. Each Generator shall only undertake the Outage
Programme only as agreed to in writing by the System Operator.
OC 4.4.2. Medium Term Planning (Year 1-2)
OC 4.4.2.1. In this Code, medium term is the two financial years following Year 0, or Years
1 & 2 of the Financial Year. The basis for Operational Planning for Year 1 & 2
shall be the "revised Year 2 & 3" Final Generation Outage Programme, agreed
between each Generator, Interconnector Operator, Generator Aggregator,
and/or Demand Side Unit Operator, and the System Operator.
OC-5 165
OC 4.4.2.2. At intervals specified in Appendix 2 (P:46), there shall be an exchange of
information concerning the Final Generation Outage Programme between each
Generator and the System Operator on a Financial Year basis.
OC 4.4.3. By the end of April in year 0, Generators, Generator Aggregators and

Demand Side Unit Operators shall submit to the SO, for each
Generation Unit, Aggregated Generating Unit or Demand Side Unit,
details of Outages and estimates of the Forced Outage Probabilities
for inclusion in:
(a) the Short-Term Outage Programme (STOP) for year 1. Other than
in the first year after the planning process has commenced, this will be
based on the previous year's Medium Term Outage Programme for year
2, which period through the passage of time has now become year 1, and
any changes may only reflect the Generator's, Interconnector
Operator’s, Generator Aggregator’s, and Demand Side Unit
Operator’s reasonable response to changed circumstances;
(b) the Medium Term Outage Programme (MTOP) for years 2 and 3.
OC 4.4.4. Long Term Planning (Year 3-5)

OC 4.4.4.1. In this Code Long Term is for the three-year period covering Years 3, 4 & 5 of
the Financial Year.
OC 4.4.4.2. At the beginning of Year 3 for the next three years, Year 3, 4 & 5, each
Generators, Interconnector Operators, Generator Aggregators and Demand
Side Unit Operators shall provide, in writing, to the System Operator, a
provisional Generation Outage Programme showing the best estimate of its
Usable Output for the Years 3, 4, and 5 (Appendix-3, P:47).
In the case of Aggregated Generating Units, and Demand Side Units which
consist of Aggregated Demand Sites, the Generator Aggregator or Demand
Side Unit Operator shall provide the aggregated Outages, and upon request
from the SO the Generator Aggregator or Demand Side Unit Operator shall
provide the Outage for each individual site, in a reasonable time period.

Side Unit Operators shall specify with regard to each of their Generation Units,
Interconnector, Aggregated Generating Units or Demand Side Units, the start
date and time and the duration of each Outage.
OC 4.4.4.3. The process of iterative discussions and updating of the Final Generation
• \
Outage Programme shall be concluded by April, 30th of each financial year to
be notified by the System Operator by May 31st of each financial year. Year 1
programme shall form the basis of the Year 0 Final Generation Outage
Programme and so on.
OC 4.4.4.4. The Market Operator/System Operator shall prepare the annual Forecast
Demand including values for the peak Summer Demand.
The System Operator shall notify respective Generators, Interconnector
Operators, Generator Aggregators and Demand Side Unit Operators of any
forecasted outages on the National Transmission System, for construction or
maintenance work. The process of Medium Term planning, between the
Market Operator/SO and each Generators, Interconnector Operators,
Generator Aggregators and Demand Side Unit Operators, shall terminate by
the beginning of the tenth month of Financial Year 3.
OC-5 166
OC 4.4.4.5. Every effort shall be made by the System Operator and each Generators,
Interconnector Operators, Generator Aggregators and Demand Side Unit
Operators to agree on the Final Generation Outage Programme which when
summated will meet the Forecast Total System Demand for the Financial
Years 3 to 5. All agreements shall be recorded for future reference. It is
acknowledged that this agreement on the Final Generation Outage
Programme at this stage is not a commitment on the part of the Generators,
Interconnector Operators, Generator Aggregators and Demand Side Unit
Operators. In the event that a Generator's, Interconnector Operators’,
Generator Aggregators’ and Demand Side Unit Operators’ outages later on
differ from those given in the Final Generation Outage Programme, or they
conflict with the Transmission System Outage Programme, the Transmission
Network Operator is not committed to alter its own Transmission System
outage programme for the sake of Generators, Interconnector Operators,
Generator Aggregators and Demand Side Unit Operators.
OC 4.5 PLANNING OF TRANSMISSION SYSTEM OUTAGES
OC 4.5.1. Short Term Planning (Year 0)
In this Code short term is the current Financial year, or year 0 of the Financial Year.
OC 4.5.1.1. Each DISCOs, Generating units, Interconnectors, Aggregated Generating Units

and Aggregated Demand Units, Provincial companies, SPTLs, Demand
Consumers may at any time during Year 0 request in writing to the System
Operator for changes in the outages requested by them in future years. The
System Operator shall determine if the changes are acceptable, and shall reply
in writing to each DISCOs, Generating units, Interconnectors, Aggregated
Generating Units and Aggregated Demand Units, Provincial companies, SPTLs,
Demand Consumers advising them if the proposed changes are acceptable to
the System Operator. However, the System Operator is not committed to alter
its own Transmission System Outage Programme due to changes proposed by
the Users.
OC 4.5.1.2. Depending on the System Operator response to OC 4.5.1.1, there may follow a
series of discussions between all Parties to determine a mutually acceptable
solution for all including the System Operator.
OC 4.5.1.3. The System Operator shall review the Final Outage Programme with respective
Code Participants at eighth week (8) before real-time. All parties are obliged to
co-operate at this stage in any outage changes requested by the System
Operator, DISCOs, Generating units, Interconnectors, Aggregated Generating
Units and Aggregated Demand Units, Provincial companies, SPTLs, Demand
Consumers
OC 4.5.1.4. This process of confirming and mutually amending the Final Outage
Programme continues in more and more detail right up to the real-time
operation. Appendix 4 (P:48) of this Code details the time scales of the
Transmission Outages and obligations. which each Code Participant must
observe to achieve this objective.
OC 4.5.2. Medium Term Planning (Year 1-2)
In this Code, Medium-Term is the two financial years period following Year 0, or Year
1-2 of the Financial Year.
OC 4.5.2.1. The System Operator is required to update the National Transmission System
Outage programme, to take into account of outages, required for National
transmission system maintenance purposes.
OC 4.5.2.2. There shall be a series of reviews similar to this given in OC 4.4.2 for Medium-
term generation outages. By April, 30th of each Financial Year i.e. Year 0, the
OC-5 167
System Operator shall publish information on Outage Programme to all the
respective Code Participants. Appendix 5 (P:48) of this Code details the time
scales of Transmission which the System Operator and each Code Participant
must observe to achieve this objective.
OC 4.5.3. Long Term Planning (Year 3-5)
In this Code long term is for the three-year period covering Years 3, 4 & 5 of the
Financial Year
OC 4.5.3.1. The System Operator shall plan the National Transmission System outages for
Years 3-5 on the basis of construction and refurbishment requirements;
whereas the National Transmission System outage programmes for Years 1-2
are for maintenance requirements.
OC 4.5.3.2. For each of the three Years 3, 4, and 5 there will be a number of timelines
whereby the System Operator and Users shall exchange information. The time
scales for the information exchange are detailed in Appendix 6 (P:48) to
achieve this objective. This process should be complete by the beginning of the
eighth month of each Financial Year.
OC 4.5.3.3. At the end of the exchange of information period, the System Operator shall
prepare a draft Transmission System outage plan (Appendix 6) Page 48 for
Years 3 to 5. The System Operator shall also issue, in writing, those aspects of
the Plan which may cause operational difficulties for Generators, DISCOs or
Transmission Connected Consumers. The System Operator shall also indicate
where they may need to issue Emergency Instructions to Users in accordance
with the Operation Code to allow that the security of supply of the National
Transmission System remains within the requirements of the Transmission
Licence.
OC 4.5.3.4. For outages in the transmission system with influence on Nuclear Power Plant
consideration must be made to assure redundant power supply to the plant
auxiliary system, due to nuclear safety.
OC 4.5.3.5. When submitting proposed Outages for inclusion in the STOP, MTOP and LTOP,
Side Unit Operators shall, unless they reasonably substantiate that an Outage is
inflexible, specify:
(a) an alternative preferred window, or alternative preferred
windows, of opportunity within each year for any Outage;
(b) the minimum Outage duration which would be acceptable, if less

than the scheduled Outage duration;
(c) situations where the paralleling of Outages of two or more of its

Generation Units, Interconnectors, Aggregated Generating
Units, Demand Side Units or Aggregated Demand Side Units
may be required, desirable, undesirable or not possible;
(d) a priority order associated with the various Outages scheduled by

the Generation Units, Interconnectors, Aggregated
Generating Units, and Demand Side Unit Operator;
(e) any Outages where it is particularly desirable that they should take
place within the year scheduled; or
(f) any Outage where its timing is dependent on Generation Unit run hours,
equivalent run hours or starts.
OC 4.6 CHANGES TO THE COMMITTED OUTAGE PROGRAMME WITHIN THE

IMPLEMENTATION YEAR (YEAR 0)
OC-5 168
OC 4.6.1. A request for a change to an Outage included in the Short Term Outage
Programme or an additional Outage may be initiated either by the SO or by
a Generator, Interconnector Operator, Generator Aggregator or Demand
Side Unit Operator at any time.
OC 4.6.2. Request initiated by the SO
OC 4.6.2.1. The SO may at any time request from a Generator, Interconnector
Operator, Generator Aggregator or Demand Side Unit Operator a
change in the timing or duration of any Outage of one of the
Generator's Generation Units, Interconnectors, Demand Side Unit
Operator’s Demand Side Units or an Individual Demand Site which
constitutes the Demand Side Unit in the Committed Outage
Programme.
OC 4.6.2.2. A Generator, Interconnector Operator, Generator Aggregator or
Demand Side Unit Operator may respond either by declining the
request, or by agreeing to the request (in which case the STOP
shall be deemed to be amended accordingly). Generators,
Interconnector Operators, Generator Aggregators and Demand
Side Unit Operators shall make every reasonable effort to co-
operate with changes requested by the SO.
OC 4.6.2.3. If a Generator, Interconnector Operator, Generator Aggregator or
Demand Side Unit Operator responds by agreeing to the request
subject to specific conditions, the SO may respond by either
confirming agreement to those conditions, in which case the
conditions specified by the Generator, Interconnector Operator,
Generator Aggregator or Demand Side Unit Operator shall be
deemed to have been accepted, or by declining agreement. Where
the SO agrees to the conditions the STOP shall be deemed to be
amended accordingly. Where the SO declines to agree to the
conditions, then the SO may negotiate with the Generator,
Interconnector Operator, Generator Aggregator or Demand Side
Unit Operator as to revised or alternative conditions, which would
be acceptable.
OC 4.6.3. Change Initiated by a Generator, Interconnector Operator, Generator

Aggregator or Demand Side Unit Operator
OC 4.6.3.1. Generators, Interconnector Operators, Generator Aggregators or
Demand Side Unit Operators may at any time request the SO for a
change in the timing or duration of any Outage of one of the
Generator's Generation Units, Interconnectors or Demand Side Unit
Operator’s Demand Side Units or an Individual Demand Site which
constitutes the Demand Side Unit in the Committed Outage
Programme.
OC 4.6.3.2. Where a change to the STOP is proposed by a Generator,
Interconnector Operator, Generator Aggregator or Demand Side
Unit Operator, the SO shall evaluate whether the change is likely to
have a detrimental effect on Capacity Adequacy or on the secure
operation of the Transmission System. This shall be done within a
reasonable time frame, taking into consideration the extent of the
change and the timing of the Outage.
OC 4.6.3.3. Where the request is not likely to have a detrimental effect on
Capacity Adequacy or the secure operation of the Transmission
System then the SO shall amend the STOP accordingly. The
Generator, Interconnector Operator, Generator Aggregator or
Demand Side Unit Operator shall be advised by the SO that the
change has been accepted.
OC-5 169
OC 4.6.3.4. Where the Outage change is likely to have a detrimental effect on
Capacity Adequacy or requirements for the secure operation of the
Transmission System then the SO shall not amend the STOP. The
SO shall contact the Generator, Interconnectors, Generator
Aggregator or Demand Side Unit Operator and inform the
Generator, Interconnector Operator’s, Generator Aggregator or
Demand Side Unit Operator that the change to the STOP has not
been accepted, the SO shall at the Generator’s, Interconnector
Operator, Generator Aggregator’s or Demand Side Unit Operator’s
request enter into discussions with the Generator, Interconnector
Operator, Generator Aggregator or Demand Side Unit Operator to
facilitate an alternative modification which may meet the
requirements of the Generator, Interconnector Operator, Generator
Aggregator or Demand Side Unit Operator while not having an
unacceptable effect on Capacity Adequacy or requirements for
secure operation of the Transmission System. In the event that the
Generator, Interconnector Operator, Generator Aggregator or
Demand Side Unit Operator wishes to avail of an alternative
modification, it shall submit a change request in accordance with
OC.4.6.3.1.
OC 4.6.3.5. Where the Generator, Interconnector Operator, Generator

Aggregator or Demand Side Unit Operator has been notified that
the change to the STOP has not been accepted, but in the view of
the Generator, Interconnector Operator, Generator Aggregator or
Demand Side Unit Operator it must force the Generation Unit,
Interconnector or Demand Side Unit to be unavailable due to
technical or safety issues, then the Generator, Interconnector
Operator, Generator Aggregator, Demand Side Unit Operator shall
inform the SO immediately in accordance with the requirements to
submit an Availability Notice.
OC 4.7 OTHER INFORMATION TO BE NOTED ABOUT ANCILLARY SERVICE PROVISION
OC 4.7.1. Generator, Interconnector Operator, Generator Aggregator or Demand Side

Unit Operator will inform the SO of any proposed maintenance, in addition
to Outages, which will, or is likely to, affect the capability of the Generation
Unit or Interconnector to provide Ancillary Services, as soon as is
reasonably possible.
OC 4.7.2. The SO may, where security of supply or the secure operation of the
Transmission System or the Other Transmission System would be at risk,
request alterations to maintenance notified under Section OC.4.7.1. The SO
shall make reasonable endeavours to give as much notice as possible for
such requests for alterations.
Where the SO makes such a request, the Generator, Interconnector Operator,
Generator Aggregator or Demand Side Unit Operator shall use reasonable
endeavours to comply with the request in arriving at the User's final
programme for such maintenance.
OC 4.7.3. The DISCOs, Provincial and SPTLs Companies, shall co-operate with the SO
and Embedded Generators and Demand Side Unit Operators in all phases
of Outage planning to promote Capacity Adequacy and ensure system
security.
OC 4.7.4. Generator, Interconnector Operator, Generator Aggregator or Demand Side
Unit Operator must immediately notify the SO on making the decision to
cancel a major Outage of a Generating Unit.
OC 4.7.4.1. Following the decision in OC.4.7.4 to cancel a major Outage of a
Generating Unit the Generator, Interconnector Operator, Generator
OC-5 170
Aggregator or Demand Side Unit Operator must report to the SO,
on an on-going basis, practical, useful, and proportionate
information to allow the SO to make the necessary assessments
and propose mitigation measures in relation to security of supply.
OC 4.7.4.2. The reports should cover the following:
(a) an explanation for the cancellation of a major Outage;
(b) annual notification of major changes to the operational intentions of

the Generator, Interconnector Operator, Generator
Aggregator or Demand Side Unit Operator and/or characteristics
of the Generation Unit as a result of the OC4.7.4.1.1 decision not
to proceed with the major Outage;
(c) assessments covering the risks of sudden and catastrophic failure.
OC 4.7.5. A Generator, Generator Aggregator must immediately notify the SO in the

event of sudden and catastrophic failure of a Generating Unit .
OC 4.7.5.1. The Generator, Generator Aggregator must report to the SO the
impact of the failure of the Generating Unit and the future
operation of the Generating Unit.
OC 4.7.5.2. The SO must notify the Regulatory Authority if the assessments
covering the sudden and catastrophic failure of a Generating Unit
highlight the emergence of potential risks to the security of supply
and the operation of the System.
OC 4.8 DATA REQUIREMENTS
OC 4.8.1. The Generator, Interconnectors, Generator Aggregators and Demand Side

Unit Operator are required to submit to the System Operator technical
information on each of their generating units. The information must include
a realistic performance chart for each unit. The information required shall
be as set out in Appendix 7 for Generator Performance Charts; set out in
Appendix 8 for Generation Planning Parameters; set out in Appendix 9 for
RES/BESS technical parameters; and as set out in Appendix 10 for
Interconnectors technical parameters.
OC 4.8.2. The Generation Planning Parameters supplied to the System Operator shall
only be used by the System Operator for planning purposes and not in
connection with the operation of the Balancing Mechanism (to be notified
by the Authority).
OC 4.8.3. By 10.00 a .m. one week prior the operational day, each User must inform
the System Operator of any changes to circuit details as specified in
Planning Code PC.A 2.2.4, PC.A 2.2.5, PC.A 2.2.6, PC.A 2.3, PC.A 2.4 which
may apply on that operational day.
OC 4.9 INSUFFICIENT POWER OPERATING MARGIN
OC 4.9.1. Annually, the System Operator shall calculate the required Active Power
Operating Margin required to support the forecasted Demand. The System
Operator shall advise Generators in writing of any periods when there is
likelihood of having insufficient power operating margin.
OC 4.9.2. Generator, Interconnectors, Generator Aggregators and Demand Side Unit
Operator and the System Operator shall review proposed outages at times
of inadequate Active Power Operating Margins to ensure that the required
Active Power Operating Margin can be achieved.
OC 4.9.3. Outage adjustments required to avoid inadequate Active Power Operating
Margin shall be given by the System Operator in writing to Generator,
Interconnectors, Generator Aggregators and Demand Side Unit Operator
with power adjustment capability.
OC-5 171
End of OC 4
OC-5 172
SYSTEM SERVICES
CONTENTS
OC 5.1. INTRODUCTION, OBJECTIVES & SCOPE........................... Error! Bookmark not defined.
OC 5.2. FREQUENCY CONTROL.................................................. Error! Bookmark not defined.
OC 5.3. FREQUENCY RESPONSE................................................................................. 176
OC 5.4. CONTROL OF POWER SYSTEM VOLTAGE......................................................... 183
OC 5.5. NETWORK CONTROL..................................................................................... 187
OC-5 173
SYSTEM SERVICES
OC 5.1 INTRODUCTION, OBJECTIVES, SCOPE
System Services refers to the services essential to the proper functioning of the
Power System which electricity utilities collectively provide for their customers in
addition to the provision of electrical power, the supply of electric energy, and the
transmission and distribution of this energy, and which thus determine Power
Quality:
(a) Frequency Control;

(b) Voltage Control;
(c) Network Control;
(d) Operating Margin; and
(e) Black Start
In order to ensure secure operation, the SO shall have control over all System
Services; i.e. the SO shall specify what System Services are to be provided
when and by whom.
OC 5.1.1. OC.5 applies to the SO and to the following, each of which is a User under
this 5OC.4:
(f) Grid Connected Generators with Registered Capacity greater than 5MW;
(g) Demand Customers
(h) The Distribution System Operators (DISCOs);
(i) Provincial and SPTLs Companies
(j) Demand Side Unit Operators and
(k) Interconnector Operators.
OC 5.2 FREQUENCY CONTROL
OC 5.2.1. Introduction & objectives

OC 5.2.1.1. In order to maintain the security and integrity of the Transmission
System it is necessary that the SO operates the Transmission
System and Dispatches in such a manner as to provide adequate
Frequency Control so as to achieve operation within applicable
Frequency limits at all times.
OC 5.2.1.2. The objectives of OC.5.3 are:
(a) to set out the procedures required to ensure that

adequate Frequency Control capability is provided on
the Transmission System to enable operational
Frequency Control by the SO so as to achieve the
applicable limits; and
(b) to set out the procedures required to enable the SO to
control the Transmission System Frequency and
(insofar as possible) to maintain Frequency within the
limits set out in CC.8.2.1.
OC-5 174
OC 5.2.2. Description of Frequency Control
OC 5.2.2.1. Frequency Control occurs in two time scales, namely:
(a) Primary Frequency Control; and
(b) Secondary Frequency Control.
OC 5.2.3. Primary Frequency Control

OC 5.2.3.1. Primary Frequency Control takes place in the period of up to 30
seconds after a change in Frequency and is achieved by automatic
corrective responses to Frequency deviations occurring on the
Transmission System. This automatic correction arises from:
(a) natural frequency demand relief of motor load;

(b) automatic MW output adjustment of Synchronised Generation Units
initiated by Governor Droop or other responses including peaking of
Combustion Turbine Units, condensate stop or frequency triggered
response of pumped storage units;
(c) automatic MW output adjustment of NON-Synchronised Generating
Units technically possible and
(d) automatic load shedding (see OC.3: Demand Management).
OC 5.2.3.2. Automatic Primary Frequency Control actions in response to
normal Frequency fluctuations, within the levels specified in CC
XXXX on the Transmission System can be termed as "Frequency
Regulation". Inadequate Frequency Regulation can result in:
(a) unscheduled operation because Generating Units are moving away

from their Dispatched MW levels due to Frequency drift;
(b) poor External Interconnection tie-line control; and
(c) failure to meet the applicable Frequency limits.
OC 5.2.3.3. Frequency deviations, outside the levels specified in CC xxx such
as those that may occur on the loss of Generation Unit(s),
Interconnectors, Demand Consumers or other MW input into, the
Transmission System or the Distribution System are corrected
through the use of Operating Reserve.
OC 5.2.4. Secondary Frequency Control

OC 5.2.4.1. Secondary Frequency Control takes place in the time scale from 5
seconds up to 10 minutes after the change in Frequency. It is
provided by a combination of automatic and manual actions.
OC 5.2.4.2. Improved Secondary Frequency Control can be achieved by use of
a Secondary Frequency Regulation System which acts directly on
the MW Outputs of participating Generation Units, on the Active
Power transfer to or from External Systems by Interconnectors and
on the MW input of Demand Side Units. This automatic action
facilitates more frequent MW output adjustments than is
practicable by means of Dispatch Instructions and manual setpoint
adjustment, thus allowing more frequent and rapid Frequency
correction.
OC-5 175
OC 5.3 FREQUENCY RESPONSE
OC 5.3.1. Requirements of Generation Unit Governor Systems

OC 5.3.1.1. In order that adequate Frequency Regulation is maintained on the
Transmission System at all times, Generators are required to
comply with the provisions of OC.5.4.1.
OC 5.3.1.2. Other than as permitted in accordance with OC5.3.1.3:
All Generating Units and Reservoir-based Hydro, CDGU type, when
Synchronised to the Transmission System shall be able to provide:
a) free Governor Control Action (AGC control) through a Governor
Control System, to maintain system frequency within the
prescribed limits provided in this Grid Code and the NEPRA
Transmission Performance Standards Rules. In the operation
state enough AGC shall be activated.
b) Also, other stakeholders shall be able to provide frequency

response AGC taken technological and economical
consideration into account. unless otherwise specified by the SO,
with characteristics within the appropriate ranges as specified in
Connection Conditions;
c) no time delays other than those necessarily inherent in the design of

the Governor Control System shall be introduced;
OC 5.3.1.3. The Generator may only restrict governor action in such a manner
as to contravene the terms of OC.5.3.1.2 where:
a) the action is essential for the safety of personnel and/or to
avoid damage to Plant, in which case the Generator shall
inform the SO of the restriction without delay; or
b) in order to (acting in accordance with Good Industry Practice)

secure the reliability of the Generating Unit; or
c) the restriction is agreed between the SO and the Generator in

advance; or
d) the restriction is in accordance with a Dispatch Instruction

given by the SO.
OC 5.3.1.4. In the event that the SO in accordance with OC.5.4.1.3 either

agrees to a restriction on governor action or instructs such a
restriction, the SO shall record the nature of the restriction, the
reasons, and the time of occurrence and duration of the restriction.
OC 5.3.1.5. Frequency Sensitive Mode
A Frequency Deadband of no greater than +/- 15mHz may be
applied to the operation of the Governor Control System. The
design, implementation and operation of the Frequency Deadband
shall be agreed with the SO prior to the Commissioning. From 2 to
6 weeks ahead of the operational day, the System Operator shall
assess whether there will be sufficient plant mix to operate in
"Frequency Sensitive Mode".
OC-6 176
Figure 6.1 Frequency sensitivity Mode
OC 5.3.1.6. If the System Operator foresees that there will be insufficient
generation operating in Frequency Sensitive Mode, it shall discuss
this problem with the Generator, Interconnectors, Demand Side
Units Operator and ESU and seek to change the plant mix to
ensure there shall be sufficient generation operating in Frequency
Sensitive Mode at the forecasted time.
OC 5.3.1.7. Action required by Generators, Interconnectors, in response to low
Frequency:
(a) If System Frequency falls to below 49.80 Hz each

Generator, Demand Side Units Operator and ESU will be
required to check that each of its CDGUs is achieving the
required level of response including that required from the
Governor Control System, where applicable in order to
contribute to containing and correcting the low System
Frequency.
(b) Generator, Demand Side Units Operator and ESU shall be

capable of providing a power increase up to Registered
Capacity.
(c) Generators Demand Side Units Operator and ESU

capable of acting as a load, including Pumped Storage
Plants, shall be capable of disconnecting their load. This
requirement does not extend to auxiliary supplies.
(d) Where the required level of response is not being achieved,
appropriate actions shall be taken by Interconnectors
Operators, according the Interconnection Agreement
(e) Where the required level of response is not being achieved
OC-6 177
appropriate action should be taken by the Generator,
Demand Side Units Operator and ESU without delay and
without receipt of instruction from the SO to achieve the
required levels of response, provided the Generator,
Demand Side Units Operator and ESU’s local security and
safety conditions permit.
(f) The Active Power Frequency Response shall be capable

of having a Governor Droop between 2% and 12%. The
default Governor Droop setting shall be 4%.
(g) Generators, Demand Side Units Operator and ESU shall

take into account the;
• ambient conditions when the response is triggered;
• operating conditions of each Generating Unit; and
• availability of the Primary Fuel in case of thermal

units.
49.8
Figure 7.1 Under-frequency sensitive mode
OC 5.3.1.8. Action required by Generator, Interconnectors, Demand Side Units

Operator and ESU in response to High Frequency Events:
If System Frequency rises to or above 50.2 Hz, each Generator,

Interconnectors, Demand Side Units Operator and ESU will be
required to ensure that its CDGUs have responded in order to
contribute to containing and correcting the high System Frequency
by automatically or manually:
a) reducing MW Output without delay and without receipt of

instruction from the SO to achieve the required levels of
OC-6 178
response, provided the Generator’s, Interconnector’s,
Demand Side Unit’s Operator and ESU’s local security and
safety conditions permit.
b) The Active Power Frequency Response shall be capable of

having a Governor Droop between 2% and 12%. The default
Governor Droop setting shall be 4%.
c) Where the required level of response is not being achieved appropriate
action should be taken by the Generator without delay and without
receipt of instruction from the SO to achieve the required levels of
response, provided the Generator’s local security and safety conditions
permit.
(c) Generators shall be capable of providing a power decrease down to
Minimum Load. Stable operation shall be ensured.
(d) Generating Units shall be capable of continuous stable operation

when MW Output is reduced to Minimum Load. This response
will prevail over any other Active Power control mode.
Figure 8.1 Over-frequency sensitive mode response
OC 5.3.1.9. Operating System Frequency Criteria

The System Operator shall co-ordinate with all the Generators
connected to its Transmission Grid system in order to maintain the
declared system frequency at 50 Hz (Cycles/sec) with the following
allowance excursions:
(i) Declared or Target System Frequency shall be 50Hz.
OC-6 179
(ii) Frequency Sensitive Mode shall be 49.8 Hz----50.2 Hz.
Such a variation is permissible to allow frequency
variations while ramping up generation and load pick-up.
(iii) Protected periods of operation of the system at the

frequency in the range of 49.5 Hz----- 50.5 Hz (Tolerance
Frequency Band).
(iv) Minimum/Maximum Acceptable Frequency Band shall be

49.4 Hz-----50.5 Hz (Load Shedding Threshold or
Contingency Frequency Band), which is well within the
applicable IEC Standards.
(v) Instantaneous frequency excursions are to be handled in

the following manner:
 In the event of a single contingency, the power

system frequency must be maintained within
"Tolerance Frequency Band" within 5 minutes of the
excursion, and to within the "Frequency Sensitive
Mode" within 10 minutes of the contingency.
 Instantaneous frequency excursions outside the

"Contingency Frequency Band" shall be handled in
such a manner that:
• System frequency returns to "Contingency

Frequency Band" within 60 seconds.
• System frequency returns to "Tolerance

Frequency Band" within 5 minutes, and within
the "Frequency Sensitive Mode" within 30
minutes.
OC 5.3.1.10. If the System Operator determines that the procedures of OC 4.8

and OC 5.4 are required for the same operating period, then the
order shall normally be OC 4.8 first followed by OC 5.4. For the
avoidance of doubt, there is nothing in this paragraph which shall
prevent either procedure following the other or operating
independently.
OC 5.3.2. Requirement of Interconnector Frequency Response Systems

In order that adequate Frequency Control is maintained on the Transmission
System at all times, Interconnectors are required to comply with the provisions
of OC.5.3.2.
a) Standard Frequency Range (CASA-1000 technical Code)
NES
Frequency (Hz) Nominal Minimum Maximum
(Hz) (Hz) (Hz)
Standard 49.80 50.20
Frequency
Range
Max 49.4 50.5
Instantaneous
50
Frequency
Deviation
Max Steady 49.5 50.5
State Frequency
OC-6 180
NES
Frequency (Hz) Nominal Minimum Maximum
(Hz) (Hz) (Hz)
Deviation
OC 5.3.2.1. Other than as permitted in accordance with OC. 5.3.2.3:
(a) Interconnectors when Energised shall operate at all times in

Frequency Control mode, unless otherwise specified by the
Reference SO, with characteristics within the appropriate
ranges as specified in Connection Conditions;
(b) The Interconnector Frequency Droop shall normally be 4%
and shall be settable between 2% and 7%;
(c) No intentional time delays other than those agreed with the
Reference SO shall be introduced into the frequency response
system;
(d) The Frequency Deadband shall normally be zero. Any non-zero
deadband must be agreed in advance with the SO and shall not
exceed +/-15mHz.
(e) Interconnectors shall not act to control the frequency in an Other
System
unless agreed in advance with the Reference SO and the Other

System Operator.
OC 5.3.2.2. OC. 5.4.2.3 The Interconnector Operator may only restrict

the action of the Frequency Control mode in such as a manner as
to contravene the terms of OC. 5.3.2.2 where:
(a) The action is essential for the safety of personnel and/or to
avoid damage to Plant, in which case the Interconnector
Operator shall inform the Reference SO of the restriction
without undue delay; or
(b) in order to (acting in accordance with Good Industry
Practice) secure the reliability of the Interconnector, in
which case the Interconnector Operator shall inform the
Reference SO of the restriction without undue delay; or
(c) the restriction is agreed between the Reference SO and the
Interconnector Operator in advance; or
(d) the restriction is in accordance with a Dispatch Instruction given

by the Reference SO.
OC 5.3.2.3. In the event that the Reference SO in accordance with OC. 5.4.2.3
either agrees to a restriction on the control action or instructs such
a restriction, the Reference SO shall record the nature of the
restriction, the reasons, and the time of occurrence and duration of
the restriction.
OC 5.3.2.4. Action required by Interconnector Operators in response to low
Frequency:
(a) If System Frequency falls to below 49.80 Hz each
Interconnector Operator will be required to ensure that it has
responded in order to contribute to containing and correcting the
low System Frequency by automatic or manually increasing
OC-6 181
the Active Power transfer from an External System or
decreasing the Active Power transfer from the Transmission
System without delay and without receipt of instruction from the
Reference SO to achieve the required levels of response,
provided the Interconnector’s local security and safety
conditions permit;
(b) Any such action shall be in accordance with the Interconnector
Operating Protocol agreed between the Interconnector
Operator, the Reference SO and the Other System
Operator.
OC 5.3.2.5. Action required by Interconnector Operators in response to high

Frequency:
(a) If System Frequency rises above 50.2 Hz each
Interconnector Operator will be required to ensure that it has
responded in order to contribute to containing and correction of
the high System Frequency by automatic or manually
decreasing the Active Power transfer from an External
System or increasing the Active Power transfer from the
Transmission System without delay and without receipt of
instruction from the Reference SO to achieve the required
levels of response, provided the Interconnector’s local
security and safety conditions permit.
(b) Any such action shall be in accordance with the
Interconnector Operating Protocol agreed between the
Interconnector Operator, the SO and the Other System
Operator.
OC 5.3.2.6. Action required by Interconnector Operators in response to
External System Frequency Events:
Automatic MW setpoint changes of Interconnectors triggered by
Frequency Events on the External System shall be agreed between the
Interconnector Operator, the SO, and the External System Operator in
accordance with the Interconnector Operating Protocol.
OC 5.3.2.7. The Reference SO having due regard to system security may
instruct the Interconnector Operator to disable the Frequency
Control mode of an Interconnector at any time, and this instruction
must be carried out without delay.
OC 5.3.3. Dispatch Instructions
When the Reference SO determines it is necessary, by having monitored the

System Frequency, it may, as part of the procedure set out in SDC, issue a
Dispatch Instruction (including Target Frequency where applicable) in
order to seek to regulate Frequency to meet the requirements for
Frequency Control. The Reference SO will give, where applicable, 15
minutes notice to each relevant User of variation in Target Frequency.
OC 5.3.4. Automatic Generator Control (AGC)

OC 5.3.4.1. The secondary Frequency regulation system operational on the
Transmission System is known as the "Automatic Generator
Control" (AGC).
OC 5.3.4.2. Generating Units and Interconnectors with a Registered Capacity of
xxMW or greater are, under Connection Conditions, required to be
connected to AGC, the AGC Control Range being a Registered
Operating Characteristic.
OC-6 182
OC 5.3.4.3. Other than as provided for in OC.5.4.6.4 and OC.5.4.6.5 all
Generation Units and Interconnectors fitted with AGC shall operate
under the control of AGC when within their AGC Control Range.
OC 5.3.4.4. In the event that the Generator or Interconnector Operator (acting
in accordance with Good Industry Practice) considers that it is
necessary to secure the reliability of a Generation Unit or
Interconnector, or for the safety of personnel and/or Plant, to
prevent a Generation Unit or Interconnector from operating under
AGC and commences to control the MW output manually, then the
Generator or Interconnector Operator shall inform the SO of this
without delay. Generators and Interconnector Operators shall also
inform the SO of the reasons for not operating the Generating Unit
or Interconnector under AGC, and the course of action being taken
to rectify the problem forthwith. When the problem has been
rectified, the Generator or Interconnector Operator shall contact
the SO to arrange for the Generation Unit or Interconnector to
return to operation under the control of AGC.
OC 5.3.4.5. The SO may issue a Dispatch Instruction to a Generator or
Interconnector Operator to prevent a Generation Unit or
Interconnector (fitted with AGC) from operating under AGC, in
accordance with SDC2.
OC 5.3.4.6. Generation Units or Interconnectors not operating under AGC for
reasons set out in OC.5.4.6.4 and OC.5.4.6.5 shall nevertheless
continue to follow MW Dispatch Instructions as required by
Schedule.
OC 5.4 CONTROL OF POWER SYSTEM VOLTAGE
OC 5.4.1. Introduction
OC 5.4.1.1. In order to maintain security and integrity of the Transmission
System, to avoid damage to the Transmission System and to User
Plant, and to maintain Voltages at User Connection Points within
the limits specified in the Connection Conditions, it is necessary for
the SO to control Transmission System Voltages.
OC 5.4.1.2. Voltage control of power systems requires that a Mvar demand is
met and that sufficient dynamic Voltage control capability is
available on the Transmission System to cover changes in the Mvar
demand such as result from Demand variations, to facilitate
controlled Voltage adjustment and to limit the duration and extent
of Voltage fluctuations under fault conditions. In order to do this,
static and dynamic reactive reserve capability is required. To
control Transmission System Voltages, the SO will utilise a variety
of methods of dynamic and static control.
OC 5.4.1.3. Voltage control strategies used by the SO include:
a) transformer tap-changing, cable switching, reactor and

capacitor switching, and other control methods which
involve utilisation of Transmission System Plant
only;
b) tap-changing on Generator Transformers;
c) Demand power factor correction;
d) utilisation of Generating Unit Reactive Power

capability, both by means of AVR control and also
Mvar Dispatch Instructions issued by the SO to
Generators;
e) utilisation of Interconnector Reactive Power
OC-6 183
capability by means of suitably acting AVR control
and/or Mvar Dispatch Instructions issued by the SO
to Interconnector Operators.
OC 5.4.2. Objectives
OC 5.4.2.1. The objective of OC.5.4 is to set out the control strategies used by
the SO, in conjunction with Users where appropriate, in controlling
Transmission System Voltages.
OC 5.4.2.2. OC.5.4 sets out the procedures required (in conjunction with those
in Schedule to enable the SO to:
a) maintain voltage stability of the Transmission System;
b) maintain Transmission System Voltages at User

Connection Points within operational limits as specified
in the Connection Conditions.
OC 5.4.2.3. OC.5.5 sets out the procedures for the utilisation of User Plant or
facilities by the SO for the purposes of Transmission System
Voltage control, where appropriate.
OC 5.4.2.4. Some procedures for implementation of Voltage control strategies
(e.g. Generating Unit Mvar Dispatch, Interconnector Mvar Dispatch)
are addressed under the provisions of Schedule and therefore this
OC.5.4 shall be read in conjunction with these provisions.
OC 5.4.3. Description of Voltage Control

OC 5.4.3.1. Voltage Control is achieved by ensuring sufficient availability of
dynamic and static reactive power from contributions listed in
OC.5.4.3.2. The factors, which are obviously most readily subject to
control by the SO, are the Mvar produced/absorbed by Generation
Units, Interconnectors and installed dedicated Voltage Control
facilities.
OC 5.4.3.2. The SO shall endeavour to maintain sufficient availability of
dynamic and static reactive power in order to operate Transmission
System Voltages at Connection Points within the levels specified in
Connection Code, at all times. Factors, which will influence the
required Mvar capacity, include the following:
a) The charging capacitance of the Transmission System,
b) Customer Mvar Demand.
c) Transmission System Mvar losses.
d) Generating Unit Mvar production or absorption.
e) Interconnector Mvar production or absorption.
f) Voltage Control facilities, such as capacitor banks and

reactors.
g) The charging capacitance of DISCOS, Provincial and

Special Transmission Licensee Companies at
connection point with the Transmission system.
OC 5.4.3.3. The effects of Transmission System capacitance can be controlled
and to some extent utilised by controlled variation of the
Transmission System Voltage. Thus at times of high Mvar Demand
(normally times of high MW Demand), the Transmission System
OC-6 184
Voltage may be operated towards the upper portion of the
allowable control range, and at times of low Mvar Demand
(normally times of low MW Demand), the Transmission System
Voltage may be operated towards the lower portion of the
allowable control range. This daily variation is typically required for
operation of the Transmission System.
OC 5.4.3.4. Due to the physics of the Transmission System, the Voltage (for
Plant operated at the same nominal Voltage) will not be the same
at all points on the Transmission System.
OC 5.4.4. Voltage Control Policy

OC 5.4.4.1. The SO shall control system voltage in order to minimise system
losses and cost of use of Ancillary Services. The SO shall determine
and modify as appropriate general procedures for its use in
controlling Voltage on the Transmission System. The procedures
shall be formulated having due regard to relevant economics of
Transmission System operation and Power System reliability. In
particular, the Voltage Control shall take cognisance of daily,
weekly and seasonal factors and the SO shall determine:
(a) suitable target Voltages in order to limit/control the effect of

transmission capacitance;
(b) best utilisation of dedicated Voltage Control facilities; and
(c) Mvar dynamic reserve requirements.
OC 5.4.5. Methods Utilised in Exercising Voltage Control

OC 5.4.5.1. Transmission System Voltages shall be continuously monitored by
the SO. Appropriate Voltage operating points shall be determined
by the SO, taking account of OC.5.5.4 and in particular of System
conditions pertaining at the time of operation.
OC 5.4.5.2. The SO shall adjust System Voltages, using control facilities that
are available so as to achieve the Mvar capacity necessary in order
to operate Transmission System Voltages at Connection Points
within the levels specified in Connection Code and retain a
dynamic Mvar capability to deal with changing System conditions
which result from changes in Demand or changes in transmission
or generation configuration, whether as a result of control actions
or faults. This may necessitate the modification of Generating Unit
MW output or Interconnector(s) Active Power transfer from an
External System or Active Power transfer to the Transmission
System.
OC 5.4.5.3. The excitation system of each Synchronous Generating Unit shall
normally be operated under the control of a continuously acting
AVR, which shall be set so as to maintain a constant terminal
voltage. The Generator may not disable or restrict the operation of
the AVR except in accordance with OC.5.5.5.5, in which event the
Synchronous Generator shall notify the SO without delay.
OC 5.4.5.4. Each NON-Synchronous Generating Units shall control the voltage
at the Grid Connection Point by means of a suitable continuously
acting AVR system. The voltage control mode shall be agreed
under the Connection Agreement and in any case within the
capability limits set out by Addendum 1, 2 or 3 as the case may be.
OC 5.4.5.5. Each Interconnector shall control the voltage at the Grid
Connection Point by means of a suitable continuously acting AVR.
The voltage control mode shall be as agreed under the
OC-6 185
Interconnector Operating Protocol. The Interconnector Operator
may not disable or restrict the operating of the AVR except in
accordance with OC.5.5.5.6, in which event the Interconnector
Operator shall notify the Reference SO without undue delay.
OC 5.4.5.6. The Generator or Interconnector Operator may only disable or
restrict AVR action where:
(a) the action is essential for the safety of personnel and/or Plant;
or
(b) in order to (acting in accordance with Good Industry Practice),

secure the reliability of the Generating Unit or Interconnector;
or
(c) the restriction is agreed between the SO and the Generator or
(d) Interconnector Operator in advance.
OC 5.4.5.7. In the event of a Generating Unit not operating under AVR, the SO
may impose restrictions on the operation of the Generating Unit in
accordance with Prudent Utility Practice, to the extent necessary to
provide for safe and secure operation of the Transmission System
and operation within prescribed standards, including where
necessary instructing the Generator to De- Energise the Generating
Unit. Where the SO takes such action, the SO shall consult with
the Generator as soon as practicable in order to determine a safe
operating regime, which causes minimum restriction on the
operation of the Generating Unit.
OC 5.4.5.8. In the event of an Interconnector not operating under AVR, the
reference SO may impose restrictions on the operation of the
Interconnector in accordance with Prudent Utility Practice, to the
extent necessary to provide for safe and secure operation of the
Transmission System and operation within prescribed standards,
including where necessary instructing the Interconnector Owner
to De-Energise the Interconnector.
OC 5.4.5.9. The SO shall, by means of Dispatch Instructions (as provided in
Schedule), instruct Generators and Interconnectors to adjust the
Reactive Power output of Generation Units and Interconnectors,
and the relevant provisions of Schedule shall apply.
OC 5.4.5.10. Other facilities which shall be utilised by the SO, where
appropriate, in order to exercise Voltage Control shall include:
(a) switching in or out of dedicated Voltage Control
facilities, such as capacitor banks and reactors;
(b) tap-changing on 400/220kV and 220/110kV Transmission System
transformers;
(c) switching out of transmission HV cables (and

occasionally transmission lines) in order to reduce the
capacitive contribution of the Transmission System.
OC 5.4.5.11. The extent to which Voltage Control mechanisms can be utilised

may be limited by System conditions and other limitations of Plant
and Apparatus.
OC 5.4.5.12. On some occasions it shall be necessary to reschedule Generation
Units or Interconnectors away from their desired output in order to
OC-6 186
achieve Transmission System Voltages at Connection Points within
the levels specified in Connection Code.
OC 5.4.6. Emergency or Exceptional Voltage Control

OC 5.4.6.1. Additional Voltage Control mechanisms may be utilised in the
event of System Emergency Conditions. These shall include the
following:
OC 5.4.6.2. Generators may be requested to operate Generating Units at Mvar
production or absorption levels outside their currently declared
Technical Parameters. This will be done by agreement between the
Generator and the SO and Generators will not be penalised for non-
compliance with this clause.
OC 5.4.6.3. Changes in System Voltage can be achieved by instructing, as a
form of Dispatch Instruction under OC.5.5, Generators to carry out
a Simultaneous Tap Change. In the event that the SO considers it
necessary to carry out a Simultaneous Tap Change, Generators
shall comply with the SO's instructions.
OC 5.4.6.4. Demand shedding may be used to prevent Voltage from
contravening low
Voltage limits (as further provided in OC.5) at Connection Points.
OC 5.4.6.5. Interconnector Operators may be requested to operate
Interconnectors at Mvar production or absorption levels outside
their currently declared Technical Parameters. This will be done by
agreement between the Interconnector Operator and the
Reference SO and Interconnector Operators will not be penalised
for non-compliance with this clause.
OC 5.5 NETWORK CONTROL
OC 5.5.1.1. In implementing the Transmission Outage Programme, in routine
operation of the Transmission System and in responding to
emergency and fault situations on the Transmission System, the
SO needs to carry out network switching and Control Actions which
may from time to time affect the operations of Users or security of
supply to Users.
OC 5.5.1.2. The purpose of this OC.5.6 is to set out the actions which may be
taken by the SO in controlling the Transmission System, to set out
the procedures whereby the SO shall inform Users, where
practicable, as to network Control Actions which will or may be
likely to significantly affect a User's operations and to identify
where the SO shall, insofar as reasonably practicable, consult with
Users and take into consideration Users’ reasonable requirements.
OC 5.5.2. Objective
OC 5.5.2.1. The objective of OC.5.5 is to:
a) identify the Control Actions that may be taken by the SO, in
order that the SO may carry out maintenance and operation of the
Transmission System and respond to Transmission System
faults and emergencies.
b) to establish procedures whereby the SO will:
i. where practicable, inform Users who will be or are

likely to be significantly affected by network Control
Actions of relevant details of intended Control Actions
and the effect of those Control Actions;
OC-6 187
ii. consult with Users as appropriate in order to find out
and take into consideration reasonable objections raised
by Users so affected.
OC 5.5.3. Network Control Actions

OC 5.5.3.1. The SO needs to carry out operational network switching for a
number of purposes, which will include:
(a) Outages of transmission Plant and Apparatus for

the purposes of maintenance, new works, System
Tests, protection testing and work by Users;
(b) Outages of transmission Plant due to suspected or
potential faults and emergency repairs;
(c) Voltage Control;
(d) limiting power flows on the Transmission System to

levels consistent with the capabilities of the
transmission Plant and system security.
OC 5.5.3.2. Additionally, network switching may occur automatically and
without advance warning due to operation of protection equipment
in isolating or clearing faults on transmission Plant or on User's
Plant which is connected to the Transmission System.
OC 5.5.3.3. Automatic switching sequences may also be established to limit
power flows or Voltage or Frequency deviations in the event of
faults elsewhere on the System.
OC 5.5.4. Notification to Users of Network Control

OC 5.5.4.1. All network Control Actions carried out on the Transmission System
have the potential in a given set of circumstances to affect Users.
To attempt to inform Users of every Control Action is not
practicable and in most cases the information will not be of value
to the User as the User will not invoke any specific action as a
result of receipt of the information.
OC 5.5.4.2. Where it is identified and agreed, in accordance with the terms of
the Connection Agreements and/ or Operating Agreements,
between the SO and a User that a specific Control Action (usually
an action affecting the Transmission System configuration) has an
Operational Effect on a User and that there is merit in notifying the
User in advance of the Control Action, then the SO will notify the
User of the Control Action (if planned and where time permits), in
accordance with any standing agreement that may be agreed with
the User.
OC 5.5.4.3. For avoidance of doubts, typical examples of actions notified in
accordance with OC. 5.5.4.2 may include:
(a) notification to the DISCOS, Provincial and Special
Transmission Licensee Companies of a significant
reduction in supply security to a Grid Supply Point,
where the DISCOS, Provincial and Special
Transmission Licensee Companies may arrange
standby feeding arrangements at lower Voltages
and/or activate embedded Generating units and/or
connect Reactive Compensation Equipment;
(b) notification to a Demand Customer of a significant
reduction in supply security to a Grid Supply Point
(such as the Outage of one of two transmission
OC-6 188
connections) where the Demand Customer may
arrange standby supply or run in-house Generating
Units.
OC 5.5.4.4. Where it is necessary to carry out urgent switching or other
network Control Actions resulting from a System condition or fault,
then it may not be possible for the SO to inform Users in advance
of the switching or other Control Actions. The SO shall endeavour
to inform Users where time permits, but this shall not delay timely
implementation of Control Actions as required. Where the SO is
unable to inform Users prior to the Control Actions, then the
provisions of OC. 5.6.5 shall apply.
OC 5.5.5. Control Under Fault or Emergency Conditions

OC 5.5.5.1. In the event of a System fault or protection operation or other
automatic operation, it will not be possible to invoke standing
procedures in accordance with OC. 5.6.4 prior to the occurrence of
the Control Action.
OC 5.5.5.2. In the circumstances referred to in OC. 5.6.5.1 or in the event that
the SO needs to implement Control Actions urgently and without
informing Users, then unless the situation is of a temporary nature
and has been rectified to normal, the SO shall inform Users of the
occurrence of the actions.
OC 5.5.5.3. The SO shall also inform Users as to the likely duration of the
condition and shall update this prognosis as appropriate. The SO
shall additionally inform Users when the condition has ended.
OC 5.5.5.4. Emergency Assistance to and from External Systems will be
detailed in the Interconnector Operating Protocol agreed between
the Interconnector Operator, the SO and the External System
Operator, and shall include the following actions:
(a) An External System Operator may request that the

SO take any available action to increase the Active
Power transferred into its External System, or reduce
the Active Power transferred into the Transmission
System. Such request must be met by the SO providing
this does not require a reduction of Demand on the
Transmission System, or lead to a reduction in security
on the Transmission System.
(b) An External System Operator may request that the
SO take any available action to increase the Active
Power transferred into its External System, or reduce
the Active Power transferred into the Transmission
System. Such request must be met by the SO providing
this does not require a reduction of Demand on the
Transmission System, or lead to a reduction in security
on the Transmission System.
OC 5.5.6. De-Energisation of Users by the SO
OC 5.5.6.1. De-Energisation of a User's Plant and Apparatus may be effected at

any time and from time to time if and to the extent that the SO
reasonably considers it necessary in order to provide for safe and
secure operation of the Transmission System within prescribed
standards, including in circumstances which otherwise cause or in
the SO's view are likely to cause one or more of the following:
(a) risk to the safety of personnel;
(b) risk to the stability of the Transmission System;
OC-6 189
(c) risk to the Transmission System or any User's Plant or
Apparatus;
(d) Transmission System elements to become

loaded beyond their emergency limits;
(e) Voltage excursions on the Transmission
System outside the ranges specified in CC.8.3;
(f) any behaviour causing sustained operation outside the
normal
Transmission System operating Frequency range;
(g) any material breach of a Connection Condition; and
(h) any action or inaction which places the SO in breach of

any legal or statutory or regulatory obligation.
End of OC 5
OC-6 190
OPERATING MARGINS
CONTENTS
OC 6.1. INTRODUCTION............................................................................................. 192
OC 6.2. OBJECTIVE.................................................................................................... 192
OC 6.3. OPERATING PROCEDURES............................................................................. 192
OC 6.4. CONSTITUENTS OF OPERATING MARGIN......................................................... 193
OC 6.5. TIME SCALES AND PLANNING........................................................................ 197
OC 6.7. POWER SYSTEM STABILITY CO-ORDINATION................................................... 200
OC 6 APPENDIX 1 (OC 6.4.1.2)- Short Term Planning Timetable for Generation

Outages (Year 0).......................................................................................... 201
OC 6 APPENDIX 2 (OC 6.4.2.1)- Medium Term Planning Timetable for Generation

Outages (Year 1-.......................................................................................... 202
OC 6 APPENDIX 3 (OC 6.4.3.2)- Long Term Planning Timetable for Generation

Outages (Year 3-5)....................................................................................... 203
OC 6 APPENDIX 4, 5, 6- (OC 6.5.1, OC 6.5.2, OC 6.5.3) NTDC Transmission Outages

(Year 0-5).................................................................................................... 204
OC 6 APPENDIX 7 (OC 4.6.1)- Generator Performance Chart, Example.........................205
OC-6 191
OPERATING MARGINS
OC 6.1 INTRODUCTION
OC 6.1.1. In order to cater for Demand forecast variations and to cover against a
sudden loss of generation from the Transmission System, it is necessary
that an Operating Margin is maintained through the Operational Control
Phase.
OC 6.1.2. The Operating Margin is the amount of reserve (provided by additional
Generation or Demand reduction measures) available above that required
to meet the expected System Demand. Prudent Utility Practice requires
that a continuum of Operating Margin is provided to adequately limit, and
then correct, the potential Frequency deviation which may occur due to a
Generation/Demand imbalance.
OC 6.1.3. OC.6 sets out the types and amounts of Reserve, as provided in a number
of reserve time scales, which make up the Operating Margin that the SO
may make use of under certain operating conditions to cover for the
uncertainties in Demand Forecasting and power plant
availability/unavailability or sudden outages of generation and transmission
facilities. Which the SO expect to utilise in the provision of the Operating
Margin.
OC 6.1.4. OC.6 applies to the System Operator, the transmission Network Operator
and to Code Participants which in OC 6 means:
(i) Generating Units under Central Dispatch.
(j) Demand Customers
(k) The Distribution System Operators (DISCOs);
(l) Provincial and SPTLs Companies
(m) Demand Side Unit Operators and
(n) Interconnector Operators.
OC 6.1.5. Minimum connection and operating requirements for Generators and

Interconnectors are outlined in the Connection Conditions.
OC 6.1.6. Procedures for the Monitoring and Testing of Operating Reserve are
outlined under OC.xx.
OC 6.2 OBJECTIVE
OC 6.2.1. The objective of OC.6 is to describe the various time scales for which
reserves are required, to describe the policy which will govern the dispatch
of the reserves, and to describe the procedures for monitoring the
performance of Generation Units, participating Interconnectors and other
reserve providers.
OC 6.3 OPERATING PROCEDURES
The System Operation shall be divided into two states as follows:
OC 6.3.1. Base Operating Case

Each day the System Operator shall establish a generation schedule and shall
dispatch generating units and transmission resources on an hour by hour basis
as per the provisions of Scheduling and Dispatch sub-code. Dispatch Schedule
OC-6 192
shall provide adequate generation capacity to meet expected load, total
operating reserves as per OC 4 and ancillary services requirements;
The Transmission system shall not result:
a) in transmission congestion or voltage violations during the normal (N-0)

state, and in the contingency (N-1) state; and
b) shall not violate voltage level criteria or contingency loading limits on
transmission lines or transformers or manifest stability problems.
c) Shall not violated voltage level criteria or contingency loading limits on
transmission lines or transformers or manifest stability problems during
maintenance periods when one component is not available (N-1-1)
OC 6.3.2. Contingency & Emergency Operating Cases
The System Operator shall have available and shall implement when required,
generation re-dispatch plans and schedules for likely (N-1-1) contingency
events so that, if the system moves to an expected contingency (N-1) state,
the System Operator can follow the re-dispatch and return the system to a
Normal State.
The System Operator shall have available and shall implement; contingency
operating procedures to deal with system contingencies.
The System Operator shall have available and shall implement; defense plan
to deal with unexpected & extreme sever contingencies.
The System Operator shall have available at all times and be in a position to
implement, system restoration plans for the situation in which the system
moves to an islanded state or suffers a cascading break up resulting in a Black
Out condition.
OC 6.3.3. Underground Conductors/Transformers Loading Criteria
The transmission Network Operator shall establish loading limits for each 1100
kV, 765 kV, 500 kV and 220 kV transmission circuit and selected 132 kV
circuits that are operated in parallel with the National Electricity Transmission
System 1100KV, 750KV, 500 kV and 220 kV lines for reliability reasons..
Loading limits shall be established according to normal (N-0) and contingency

(N-1) states as well as for Summer and Winter.
SO shall draft Transmission Security and Planning Standards, approved by

NEPRA, where criteria are described. These shall take into account the
followings:
a) List of climatic conditions parameters, i.e. winter/summer

b) Clearance of the installation site for Overhead conductors
c) Laying conditions and grounding thermal parameters for Underground
conductors
d) The static and dynamic rating based on operational procedure and
reaction time of SO
OC 6.4 CONSTITUENTS OF OPERATING MARGIN
OC 6.4.1. The Operating Margin consist of all reserves Operating Reserve (which is
further broken down into 4 time-scales), Replacement Reserve, Substitute
Reserve and Contingency Reserve, available in the Grid, to ensure reliable
grid system operation. Enough back-up power should be made available
without delay, at all times, to maintain the system frequency within the
specified ranges as provided in this Grid Code and NEPRA Rules on
Transmission Performance Standards. In case of sudden increase in
demand or loss of generation, which cannot be absorbed by the Operating
OC-6 193
Reserve, the Contingency Reserve equal to the shortfall shall be brought in
service within 30 minutes.
OC 6.4.2. Operating Reserve
OC 6.4.2.1. Reserve is:
a. the additional MW output provided from Generator,
Interconnectors, Generator Aggregators, or reduction of Active
Power transfer to an External System or increase of Active Power
transfer to the Transmission System by Interconnectors, or
reduction in Customer Demand, or Demand Side Unit which shall
be available within 10 minutes following the contingency event of
loss of generation or loss of an external interconnection or load
demand or mismatch between generation and load demand
resulting in a change of Transmission System frequency. This is
equal to the largest Generator in the System. Slower reserves shall
be available to replace the activated spinning reserve after 15
minutes (Replacement Reserve)
b. The amount of Operating Reserve required in real time shall be
pre-determined by the SO. Any shortfalls in power plant
availability, demand level, and the loss of the largest Generator in
a power plant and the effect of the loss of or the increase in load
demand on an external interconnection are to be taken into
account when determining the total amount of Operating Reserve.
OC 6.4.2.2. Operating Reserve definitions relate to the time elapsed from the
occurrence of an event which has initiated a Frequency
disturbance. The definition of the time at which the event is
deemed to have occurred and other associated definitions are
addressed in OC.6.4. Operating Reserve consists of the following:
a. Primary Operating Reserve
b. Secondary Operating Reserve
c. Tertiary Operating Reserve
OC 6.4.3. Primary Operating Reserve (POR)

OC 6.4.3.1. Primary Operating Reserve (POR) is the additional MW output
(and/or reduction in Demand) required at the Frequency nadir
(minimum), compared to the pre-incident output (or Demand),
which is fully available and sustainable between 5 seconds and 15
seconds after the Event and where the nadir occurs between 5 and
15 seconds after the Event.
OC 6.4.3.2. If the actual Frequency nadir occurs less than 5 seconds or more
than 15 seconds after the Event, then for the purpose of POR
monitoring (in accordance with OC.monitoring) the nadir is deemed
to be the lowest Frequency which did occur between 5 and 15 seconds
after the Event.
OC 6.4.4. Secondary Operating Reserve (SOR)

OC 6.4.4.1. Secondary Operating Reserve (SOR) is the additional MW output
(and/or reduction in Demand) required compared to the pre-
incident output (or Demand), which is fully available and
sustainable over the period from 15 to 90 seconds following an
Event.
OC 6.4.5. Tertiary Operating Reserve

OC 6.4.5.1. Tertiary Operating Reserve band 1 (TOR1) is the additional MW
output (and/or reduction in Demand) required compared to the
OC-6 194
pre-incident output (or Demand) which is fully available and
sustainable over the period from 90 seconds to 5 minutes following
an Event.
OC 6.4.5.2. Tertiary Operating Reserve band 2 (TOR2) is the additional MW
output (and/or reduction in Demand) required compared to the
pre-incident output (or Demand) which is fully available and
sustainable over the period from 5 minutes to 20 minutes following
an Event.
OC 6.4.5.3. Replacement Reserve is the additional MW output (and/or
reduction in Demand) required compared to the pre-incident
output (or Demand) which is fully available and sustainable over
the period from 20 minutes to 4 hours following an Event.
OC 6.4.5.4. Substitute Reserve is the additional MW output (and/or
reduction in Demand) required compared to the pre-incident
output (or Demand) which is fully available and sustainable over
the period from 4 hours to 24 hours following an Event.
OC 6.4.5.5. Contingency Reserve

a. Contingency Reserve is the level of generating units margin of
Availability over the forecasted Demand which is required in the
time scale from real time to real time plus 24 hours so as to cover
for uncertainties in Power plant availability and variations in load
Demand forecast and Demand forecast errors. Contingency
Reserve is provided by Generator, Interconnectors, Generator
Aggregators, Externally Connected Parties and Demand Side
Units which are not required to be synchronized, but they can be
synchronized within 30 Minutes of the initiation of the Contingency
and the fall in frequency. This is equal to at least the capacity of
largest thermal Generator in the system.
b. The amount of Contingency Reserve that is required at the day
ahead stage is determined by the SO. Time scales may be
increased by SO in the light of historical data available as to
changes in power plant availability and changes in load demand up
to real time. The SO shall agree time scales with the Generator,
Interconnectors Operators, Generator Aggregators, Externally
Connected Parties and Demand Side Units Operators, where
Contingency Reserve is held on thermal Generators to reach
synchronous speed.
OC 6.4.6. Definitions Associated with an Operating Reserve Incident

OC 6.4.6.1. Following the occurrence of a significant Frequency
disturbance, the SO shall monitor, in accordance with OC.xxxx,
and analyse the adequacy of the provision of Operating Reserve.
For the purposes of this performance analysis, the following criteria
have been defined.
OC 6.4.6.2. A significant Frequency disturbance event is deemed to have
occurred if the Frequency falls below 49.40 Hz.
OC 6.4.6.3. The pre-incident Frequency value is the average Transmission
System Frequency between 60 and 30 seconds prior to the Event.
OC 6.4.6.4. The pre-incident value of MW output of a Generating Unit, MW
Demand of a Customer, is the appropriate MW value averaged
over the period between 60 and 30 seconds prior to the Event.
OC 6.4.7. Operating Margin Policy

OC 6.4.7.1. Contingency Reserve
OC-6 195
OC 6.4.7.1.1 The SO shall determine the amount of Contingency Reserve
required for each time scale up to 24 hours ahead, taking due
consideration of relevant factors, including but not limited to the
following:
(a) historically Availability Factor and reliability performance of

individual Generating Units;
(b) notified risk to the reliability of individual Generating Units; and
(c) Demand forecasting uncertainties;
(d) Status and availability of Demand Side Units and
(e) status and availability of Interconnectors.
OC 6.4.7.2. Operating Reserve

OC 6.4.7.2.1 The SO shall determine the amount of Primary Operating
Reserve, Secondary Operating Reserve, Tertiary Operating
Reserve and Replacement Reserve to be carried at any time to
ensure system security. This will not be constrained by the
Trading and Settlement Rules. Due consideration will be taken of
relevant factors, including but not limited to the following:
(a) the relevant SO operating policy in existence at that time;
(b) the extent to which Customer disconnections allowed under the

relevant standard have already occurred within the then relevant
period;
(c) the elapsed time since the last Customer disconnection incident;
(d) particular events of national or widespread significance, which

may justify provision of additional Operating Reserve;
(e) the cost of providing Operating Reserve at any point in time;
(f) the magnitude and number of the largest generation infeed’s to

the Transmission System at that time, including infeed’s over
External Connected Parties and External Interconnections and also
over single transmission feeders within the Transmission System
and also the amount of Generation that could be lost following a
single Contingency;
(g) ambient weather conditions, insofar as they may affect (directly or

indirectly) Generating Unit and/or Transmission System reliability;
(h) the predicted Frequency drop on loss of the largest infeed as may
be determined through simulation using a dynamic model of the
Power System;
(i) constraints imposed by agreements in place with Externally

Interconnected Parties;
(j) uncertainty in future Generation output.
OC 6.4.7.3. SO shall keep records of significant alterations to the Operating

Reserve policy so determined under OC. 6.4.8.2.
OC-6 196
OC 6.4.8. Responsibilities of the SO in Respect of Operating Reserve
OC 6.4.8.1. The SO shall in accordance with Prudent Utility Practice make
reasonable endeavours to Dispatch generation and otherwise
operate the system in compliance with the SO's determinations as
to Operating Margin policies made from time to time.
OC 6.4.8.2. The SO's sole responsibility, having met its obligations under the
preceding provisions of OC.4.6, shall be to, acting in accordance
with Prudent Utility Practice, Dispatch such Generation Units as are
available required to meet:
(a) System Demand; and
(b) the level of Operating Reserve required by the SO's then

Operating Reserve policies.
OC 6.5 TIME SCALES AND PLANNING
OC 6.5.1. By 1500 hours (3 p.m.) each Wednesday the SO/MO shall issue each
Generator, Interconnectors Operators , Generator Aggregators, Externally
Connected Parties and Demand Side Units Operators in respect of its
Generating Unit or Demand Side Unit, a Weekly Operational Policy for the
week commencing 10.00 a.m. for the following Monday. The Weekly
Operational Policy shall cover Generating and Demand Side Units that are
available from standstill to start by low frequency relay settings of which
will be determined from time to time by the SO/MO. The Weekly
Operational Policy shall specify the location of the Generating Unit or
Demand Side and take into account the low frequency setting of these
Generating Unit or Demand Side. By 10.00 a.m. on the Friday following the
receipt of the document, the Generating Unit or Demand Side shall confirm
as appropriate, its availability, and seek any changes it wishes to instigate
in the document. The System Operator shall update availability in real time
in respect of notifications received.
OC 6.5.2. The Weekly Operational Policy shall include an indication of the level of
Operational Reserve to be used in connection with operation of the
Balancing Mechanism (to be notified by the Authority) in the times scale
defined in OC 5.5.1. The document shall also include details of Operational
Reserve that may be provided by Externally-connected systems
(Interconnector) and also indicate the possible level of High Frequency
Response to be utilised by the SO in connection with the operation of the
Balancing Mechanism.
OC 6.6 BLACK START
OC 6.6.1.1. In order to recover the Transmission System from a Partial
Shutdown or Total Shutdown, it is necessary to have certain Power
Stations ("Black Start Stations") available which have the ability for
at least one of its Generation Units to Start-Up from Shutdown and
to energise a part of the Total System, or be Synchronised to the
System, upon instruction from the SO, without an external electrical
power supply as detailed in the Interconnector Operating Protocol
agreed between the Interconnector Operator, the SO and the
External System Operator.
OC 6.6.2. Objective
OC-6 197
OC 6.6.2.1. The objectives of OC.6.6 is to set out the requirements of Black
Start Stations to enable recovery of the Transmission System from
a Partial Shutdown or Total Shutdown.
OC 6.6.3. Requirements of Black Start Stations

OC 6.6.3.1. In order that adequate security is maintained on the Transmission
System at all times, Black Start Stations are required to comply
with the provisions of OC. 6.6.3.
OC 6.6.3.2. Other than as permitted in accordance with OC. 6.6.3.3:
During a Black Start situation, instructions in relation to Black

Start Stations will be in the format required for instructions to
Units in Schedule A&B, and will recognise any differing Black
Start operational capabilities (however termed) set out in the
relevant Ancillary Services Agreement in preference to the
declared operational capability as registered pursuant to Schedule
(or as amended from time to time in accordance with Schedule and
Schedule). For the purposes of these instructions the Black Start
will be an emergency circumstance. For Power Stations or
Interconnectors or External Connected Parties which are not
Black Start Stations, Dispatch instructions will recognise each
Unit's declared operational capability as registered pursuant to
Schedule (or as amended from time to time in accordance with
Schedule and Schedule).
OC 6.6.3.3. If during the Demand restoration process any Generating Unit or
Interconnector or External Connected Parties that is part of a Black
Start Station cannot, because of the Demand being experienced,
keep within its safe operating parameters, the Generator or
Interconnector Operator or External Connected Parties shall inform
the SO. The SO will, where possible, either instruct Demand to be
altered or will re-configure the Transmission System or will instruct
a User to re-configure its System in order to alleviate the problem
being experienced by the Generator or Interconnector Operator or
External Connected Parties. However, the SO accepts that any
decision to keep a Unit operating, if outside its safe operating
parameters, is one for the Generator or Interconnector Operator or
External Connected Parties concerned alone and accepts that the
Generator or Interconnector Operator or External Connected
Parties may change generation on that Unit if it believes it is
necessary for safety reasons (whether relating to personnel or
Plant and/or Apparatus). If such a change is made without prior
notice, then the Generator or Interconnector Operator or External
Connected Parties shall inform the SO as soon as reasonably
practical.
For Wind : addendum 1
For Solar : Addendum 2
For BESU : Addendum 3
For Interconnectors: Technical Code and Interconnection

Agreement
TABLE 4-2
Rating Parameters for Overhead
Conductors
OC-6 198
Summer Winter Rating
Rating Bases Bases
Maximum Conductor Temp. 90° c 90° c
Outdoor Ambient Temp.
40° C (d)
(avg.)
Conductor Temp. Rise * *
Max. Emergency Conductor None Allowed None Allowed
Temp.
Wind Velocity 3 Feet/Second 3 Feet/Second
Age of the Transmission I
Circuit
Transmission Line Sag
Design
* ”Conductor Temperature Rise” shall be calculated based on the Outdoor Ambient
Temperature (average/ used for each respective Province. Lower or higher Outdoor
Ambient Temperature (average) within a Province. different from the values staled
in (d/ above. may be considered if the variation in such temperature is significant,
depending upon the location.
Criteria stated in the table above apply to National transmission line conductors
designed for operation at 1100KV, 750KV, 500KV, 220KV and 132kV voltage levels.
Notes to Table:
(a) Summer Months = April through October
(b) Winter Months = November through March
(c) Emergency ratings are limited to (8) hours of continuous operation.

Conductors shall not be operated above 100° C conductor temperature for
more than 960 cumulative hours.
(d) The following average temperature of Winter shall be used for the respective
provinces:
1. Lahore (Punjab) 6.5° C

2. Peshawar (NWFP) 5° C
3. Quella (Balochistan) -7° C
4. Karachi (Sindh) +5° C
OC 6.6.4. Transformer Loading Criteria
Grid station transformers including three phase and single-phase banks that
are normally operated at the voltage levels of 220/132kV and 500/220kV shall
be loaded under normal and contingency conditions according to applicable
IEC, ANSI/IEEE standards and as specified by the respective manufacturers.
Also, pre-load conditions to be taken into account.
Other future voltages levels shall be included, 765kV, 1100kV HVAC, 800kV and
1100kV HVDC.
OC 6.6.5. Transmission System Components Loading Criteria
Transmission system components listed below, that are normally operated at

the voltage levels of 220/132kV and 500/220kV, shall be loaded under normal
and contingency conditions according to applicable IEC, ANSI/IEEE standards
and as specified by the respective manufacturers.
Circuit breakers Current Transformers
OC-6 199
Circuit switchers3 Potential transformers
Capacitors Wave traps
Shunt reactors Substation power buses
Disconnect switches Substation power cables
OC 6.7 POWER SYSTEM STABILITY CO-ORDINATION
Each year, the System Operator shall prepare transient stability studies for expected
system event scenarios that could lead to unsatisfactory system dynamic performance
and loss of power angle stability (transient instability), voltage instability and lack of
power system oscillation damping. The System Operator shall maintain and be able and
ready to implement, when required, emergency operating procedures designed to
mitigate the extent of disturbance resulting from a system event. The criteria for
acceptance should be described in separate document to make it flexible for the
future.
The System Operator shall make stability studies lo develop emergency operating
plans to deal with the consequences of the occurrence of the most probable faults
including the following:
(a) Permanent three-phase fault on any primary transmission

(b) Failure of a circuit breaker to clear a fault ("Stuck Breaker" condition) in 5 cycles,
with back up clearing in 9 cycles after fault initiation.
(c) Busbar section fault
(d) Permanent line fault with automatic reclosing to the fault
(e) Double circuit fault on both branches of a double circuit line
(f) Generator trip
(g) Interconnector trip
End of OC 6
3
Circuit Switchers are disconnect switches with capability to interrupt load current under nonfault conditions
OC-6 200
OC 6 APPENDIX 1 (OC 6.4.1.2)- Short Term Planning Timetable for Generation Outages
(Year 0)
This appendix should be completed by the System Operator in consultation with the Generators and
other relevant stakeholders.
OC-7
OC 6 APPENDIX 2 (OC 6.4.2.1)- Medium Term Planning Timetable for Generation Outages
(Year 1-2)
This appendix should be completed by the System Operator in consultation with the Generators and
other relevant stakeholders.
OC-7
OC 6 APPENDIX 3 (OC 6.4.3.2)- Long Term Planning Timetable for Generation Outages
(Year 3-5)
This appendix should be completed by System Operator in consultation with the Generators and other
relevant stakeholders.
OC-7
OC 6 APPENDIX 4, 5, 6- (OC 6.5.1, OC 6.5.2, OC 6.5.3) NTDC Transmission Outages
(Year 0-5)
This appendix should be completed by System Operator in consultation with the generators and other
relevant stakeholders.
OC-7
OC 6 APPENDIX 7 (OC 4.6.1)- Generator Performance Chart, Example
Rated Apparent Power SNMVA Rated Frequency fN = 50 Hz

Rated Active Power PN MW Power Factor P.F. = 0.85
Rated Armature Voltage VN kV Speed nN =50 s01
Rated Armature Current IN kA Cold Air Temperature TK = 41 °C
160
Cold gas temperature 11  C
140
120
100
Overexcited
80
60
40
20
MW
0
40 60 80 100 120 140 160 180 200 220
20
Underexcited
40
60
80
Mvar
100
120
OC-7
SMALL SCALE GENERATOR CONDITIONS
CONTENTS
OC 7.1. INTRODUCTION............................................................................................. 207
OC 7.2. OBJECTIVE.................................................................................................... 207
OC 7.3. SCOPE.......................................................................................................... 207
OC 7.4. OUTAGE SCHEDULING................................................................................... 208
OC 7.5. CHANGES TO THE COMMITTED OUTAGE PROGRAMME WITHIN THE

IMPLEMENTATION YEAR................................................................................ 208
OC 7.6. OTHER INFORMATION TO BE NOTIFIED........................................................... 209
OC 7.7. NETWORK CONTROL..................................................................................... 209
OC-7
SMALL SCALE GENERATOR CONDITIONS
OC 7.1 INTRODUCTION
OC 7.1.1. Secure operation of an electricity system requires that maintenance of

production facilities (Generating Units) should be carried out in a timely and
orderly fashion. This is essential in order to enable the SO to fulfil its
obligations relating to operation of the Transmission System, and to enable
Generators to plan their Outages in an orderly way with due regard to Plant
requirements and resource limitations.
OC 7.1.2. OC7 formalises the mechanism for scheduling outages of Users specified in
OC.7.3.
OC 7.1.3. In implementing the Transmission Outage Programme (TOP), in routine
operation of the Transmission System and in responding to emergency and
fault situations on the Transmission System, the SO needs to carry out
network switching and Control Actions which may from time to time affect
the operations of Users or security of supply to Users.
OC 7.1.4. OC6 sets out the actions which may be taken by the SO in controlling the
Transmission System, to set out the procedures whereby the SO shall
inform Users, where practicable, as to network Control Actions which will or
may be likely to significantly affect a User's operations and to identify
where the SO shall, as reasonably practicable, consult with Users and take
into consideration Users’ reasonable requirements.
OC 7.1.5. In addition to OC.7, the Users specified in OC.7.3 are required to comply
with:
 Planning Code
 General Conditions
 Connection Conditions (TBD)

 OC.XXXXXXX (TBD)
OC 7.2 OBJECTIVE
OC 7.2.1. OC.7 ensures the development and implementation of a Generation Outage

Programme, consistent with security of supply and requirements for the
secure and economic operation of the Transmission System, and with the
needs of Small Scale Generators in respect of Plant maintenance
requirements and resource limitations.
OC 7.2.2. In order to achieve this objective, OC.7 defines the procedure for formal
notification of Outages by Generators to the SO.
OC 7.2.3. OC.7 identifies the Control Actions that may be taken by the SO, in order
that the SO may carry out maintenance and operation of the Transmission
System and respond to Transmission System faults and emergencies.
OC 7.2.4. OC.7 establishes procedures whereby the SO will:
(a) where practicable, inform Users, who will be or are likely to be

significantly affected by network Control Actions, of relevant
details of intended Control Actions and the effect of those
Control Actions;
(b) consult with Users, as appropriate, in order to find out and take
into consideration reasonable objections raised by Users so
affected.
OC 7.3 SCOPE
OC.7 applies to the SO, and to the following Users:
OC-7
(a) Generators with Registered Capacity of 10MW or less (on a single Site)
as the case may be according to OC.2.2.1;
(b) Generators with Registered Capacity less than 10MW (on a
single Site) and greater than 5MW (on a single Site) where the SO
consider that the Generator is in a location that does not make its
operation particularly critical to the operation of the transmission
system.
OC 7.4 OUTAGE SCHEDULING
OC 7.4.1. The current year shall be defined as year 0, the following year as year 1,
and so on.
OC 7.4.2. By the end of March in year 0, Small Scale Generators shall submit to the
SO, for each Generation Site, plant Capacity Available for each week for
year 1 for inclusion in the Medium Outage Programme (MOP) for year 1 and
estimated weekly Load Factors for year 1. Generators shall specify the start
date and time and the duration of each Outage. This information shall be
supplied on a Unit basis if so, requested by the SO.
OC 7.4.3. In scheduling Outages, the Generator must act reasonably and in good
faith. Without limitation to such obligation, each Generator should act in
accordance with Good Industry Practice in planning their Outages and, in
particular, so as to avoid a situation arising in which a Generator is obliged
to schedule an Outage by reason of obligations imposed upon the
Generator by statute as a consequence of the Generator not having
planned in accordance with Good Industry Practice, for example, by not
having planned sufficiently in advance its Outages for any statutory time
limit.
OC 7.4.4. Any concerns which the SO may have with the Generation Outage
Programme
must be notified to all Generators by the end of June in year 0.
OC 7.4.5. Between the end of June in year 0 and the end of September in year 0 any
concerns raised by the SO shall be notified to Generators. The SO will
facilitate discussions by Generators to find a resolution.
OC 7.5 CHANGES TO THE COMMITTED OUTAGE PROGRAMME WITHIN THE

IMPLEMENTATION YEAR
A request for a change to an Outage included in the Short Term Outage

Programme or an additional Outage may be initiated either by the SO or by a
Generator at any time.
OC 7.5.1. Request Initiated by the SO
OC 7.5.1.1. The SO may at any time request from a Generator a change in the
timing or duration of any Outage of one of the Generator's
Generating units in the Short Term Outage Programme.
OC 7.5.1.2. A Generator may respond by either declining the request, or by

agreeing to the request (in which case the COP shall be deemed to be
amended accordingly). Generators shall make every reasonable effort
to co-operate with changes requested by the SO.
OC 7.5.1.3. If a Generator responds by agreeing to the request subject to specific
conditions, the SO may respond by either confirming agreement to
those conditions, in which case the conditions specified by the
Generator shall be deemed to have been accepted, or by declining
agreement. Where the SO agrees to the conditions the STOP shall be
deemed to be amended accordingly. Where the SO declines to agree
OC-7
to the conditions, then the SO may negotiate with the Generator as to
revised or alternative conditions, which would be acceptable.
OC 7.5.2. Outage change Initiated by a Generator

OC 7.5.2.1. Generators may at any time request the SO for a change in the timing
or duration of any Outage of one of the Generator's Generating units
in the Short Term Outage Programme.
OC 7.5.2.2. Where a change to the STOP is proposed by a Generator, the SO shall
evaluate whether the change is likely to have a detrimental effect on
the secure operation of the Transmission System. This shall be done
within a reasonable time frame, taking into consideration the extent of
the change and the timing of the Outage. The Generator shall be
advised by the SO whether or not the change has been accepted.
OC 7.5.2.3. Where, in accordance with OC6.5, the request is not likely to have a
detrimental effect on the secure operation of the Transmission System
then the SO shall amend the STOP accordingly.
OC 7.5.2.4. Where, in accordance with OC.7.5, the Outage change is likely to have
a detrimental effect on requirements for the secure operation of the
Transmission System then the SO shall not amend the STOP. The SO
shall contact the Generator requesting the change to establish that it
is still required.
OC 7.6 OTHER INFORMATION TO BE NOTIFIED
OC 7.6.1. Generators will inform the SO of any proposed maintenance, in addition to

Outages, which will, or is likely to, affect the capability of the Generating
unit to provide Ancillary Services.
OC 7.6.2. The SO may, where security of supply or the secure operation of the
Transmission System would be at risk, request alterations to maintenance
notified under Section OC.7.6.1. The SO shall make reasonable endeavours
to give as much notice as possible for such requests for alterations. Where
the SO makes such a request, the Generator shall use reasonable
endeavours to comply with the request in arriving at the Generator's final
programme for such maintenance.
OC 7.7 NETWORK CONTROL
OC 7.7.1. Network Control Actions

OC 7.7.1.1. The SO needs to carry out operational network switching for a
number of purposes, which will include:
(a) Outages of transmission Plant and Apparatus for the
purposes of maintenance, new works, System Tests, protection
testing and work by Users;
(b) Outages of transmission Plant due to suspected or potential
faults and emergency repairs;
(c) Voltage Control;
(d) limiting power flows on the Transmission System to levels

consistent with the capabilities of the transmission Plant and
system security;
(e) High Speed reclosing is a feature of the network.
OC 7.7.1.2. Additionally, network switching may occur automatically and

without advance warning due to operation of protection equipment
OC-7
in isolating or clearing faults on transmission Plant or on User's
Plant which is connected to the Transmission System.
OC 7.7.1.3. Automatic switching sequences may also be established to limit
power flows or Voltage or Frequency deviations in the event of
faults elsewhere on the System.
OC 7.7.2. Notification to Users of Network Control

OC 7.7.2.1. All network Control Actions carried out on the Transmission
System have the potential in a given set of circumstances to
affect Users. To attempt to inform Users of every Control Action is
not practicable and in most cases the information will not be of
value to the User as the User will not invoke any specific action as
a result of receipt of the information.
OC 7.7.2.2. Where it is identified and agreed, in accordance with the terms of
the Connection Agreements and/ or Operating Agreements,
between the SO and a User that a specific Control Action (usually
an action affecting the Transmission System configuration) has an
Operational Effect on a User and that there is merit in notifying the
User in advance of the Control Action, then the SO will notify the
User of the Control Action (if planned and where time permits), in
accordance with any standing agreement that may be agreed with
the User.
OC 7.7.2.3. Where it is necessary to carry out urgent switching or other
network Control Actions resulting from a System condition or fault,
then it may not be possible for the SO to inform Users in advance
of the switching or other Control Actions. The SO shall endeavour
to inform Users where time permits, but this shall not delay timely
implementation of Control Actions as required. Where the SO is
unable to inform Users prior to the Control Actions, then the
provisions of OC.7.7.3 shall apply.
OC 7.7.3. Control Under Fault or Emergency Conditions

OC 7.7.3.1. In the event of a System fault or protection operation or other
automatic operation, it will not be possible to invoke standing
procedures in accordance with OC.7.7.2 prior to the occurrence of
the Control Action.
OC 7.7.3.2. In the circumstances referred to in OC.7.7.3.1 or in the event that
the SO needs to implement Control Actions urgently and without
informing Users, then unless the situation is of a temporary nature
and has been rectified to normal, the SO shall inform Users of the
occurrence of the actions.
OC 7.7.3.3. The SO shall also inform Users as to the likely duration of the
condition and shall update this prognosis as appropriate. The SO
shall additionally inform Users when the condition has ended.
OC 7.7.4. De-Energisation of Users by the SO

OC 7.7.4.1. De-Energisation of a User's Plant and Apparatus may be
effected at any time and from time to time if and to the extent
that the SO reasonably considers it necessary in order to provide
for safe and secure operation of the Transmission System within
prescribed standards, including in circumstances which otherwise
cause or in the SO's view are likely to cause one or more of the
following:
(a) risk to the safety of personnel;
OC-7
(b) risk to the stability of the Transmission System;
(c) risk to the Transmission System or any User's Plant or

Apparatus;
(d) Transmission System elements to become loaded beyond

their emergency limits;
(e) Voltage excursions on the Transmission System
outside the ranges specified in CC.8.3;
(f) any behaviour causing sustained operation outside the
normal Transmission System operating Frequency
range;
(g) any material breach of a Connection Condition; and
(h) any action or inaction which places the SO in breach of

any legal or statutory or regulatory obligation.
OC 7.7.4.2. Instructions to De-energise a User connected to the distribution
system under the terms of OC.7.7.4.1 may be issued by the SO to
the DISCOs, Demand Customers, External connected Consumers &
Parties who shall act on the instruction without undue delay.
End of OC 7
OC-7
OPERATIONAL LIAISON
CONTENTS
OC 8.1 INTRODUCTION, OBJECTIVE & SCOPE............................................................. 213
OC 8.2 OPERATIONS AND EVENTS............................................................................ 213
OC 8.3 NOTIFICATION OF EVENTS AND OPERATIONS................................................. 214
OC 8.4 SYSTEM OPERATOR WARNINGS..................................................................... 218
OC 8.5 OPERATIONAL COMMUNICATION AND DATA RETENTION.................................. 219
OC-8
OPERATIONAL LIAISON
OC 8.1.1. Operating Code No. 6 sets out the requirements for the exchange of
information relating to Operations and Events on the Total System that
may have, or have had, an operational effect on the National Power System
, Generators, Interconnector Operators, External Connected Parties,
Generator Aggregators, or Demand Side Operators, transmission-connected
Consumers, Discos.
OC 8.1.2. Exchange of information also includes the requirement to advise on
equipment, plant, and apparatus tests. The System Warnings shall be
issued relating to inadequate plant availability, subsequent load demand
control, and to advise of a risk of major system disturbance.
OC 8.2 OPERATIONS AND EVENTS
OC 8.2.1. Information regarding "Operations" and "Events", that have taken place or
about to take place or are being planned to take place are to be assessed
by the System Operator to identify appropriate and necessary actions to be
taken by the owner or respective Operator of a part of the sub-system or
the System Operator to eliminate or to minimize their adverse effects, if
any. The reason for the Operation or the Cause of an Event need not be
communicated to the Parties or Code Participants or Users.
OC 8.2.2. Operation is a planned or unplanned action; by the System Operator; and
Operational Effect is the effect that an Operation or an Event, on one part
of the System, may have on the Total System or on another part of the
System.
OC 8.2.3. Some of the Operations and Events that are required to be reported under
this sub-code are:
OC 8.2.3.1. (a) Operations that form part of a planned outage which has been
arranged in accordance with OC 4.
OC 8.2.3.2. (b) Events which cause plant or apparatus to operate beyond its
rated design capability and present a hazard to personnel.
OC 8.2.3.3. (c) Adverse weather conditions being experienced.
OC 8.2.3.4. (d) Failures of protection, control or communication equipment.
OC 8.2.3.5. (e) Risk of trip on apparatus or plant.
This list is not exhaustive.
OC 8.2.4. Notification of an Operation or Event shall be sufficient for the recipient to

assess the effect on its individual System. When it is necessary for the
System Operator to pass on to other Users the information it has received
from a particular User relating to an Operation or Event; it shall only pass
on the information that it has received, and the name of the source of the
information. The Giver of the original information may receive request
clarification.
OC 8.2.5. Notification of Operations and Events may be passed on to the Operators of
Embedded Generation subject to Central Dispatch when the Operation or
Event may have an effect on their System.
OC 8.2.6. Notification of the details of an Event, Major Event and Operation, must be
restricted to Parties governed by the Grid Code. Details shall not be passed
on to any other third party.
OC-8
OC 8.2.7. OC 8 deals with the upgrading of an "Event" to a "Major Event' and the
subsequent exchange of information.
OC 8.3 NOTIFICATION OF EVENTS AND OPERATIONS
OC 8.3.1.1. OC.8.3 sets out the requirements for the exchange of information
of written reports in relation to Operations and/or Events on the
Power System which have had (or may have had) or will have (or
may have) an Operational Effect, and thereby have become a
Significant System Incident. Declaration of Significant System
incident may be as follows as follows:
OC 8.3.1.1.1 Significant System Incidents on the Transmission

System in the case of an Operation and/or Event
occurring on a User System; and
OC 8.3.1.1.2 Significant System Incidents on a User System in the

case of an Operation and/or Event occurring on the
OC 8.3.1.1.3 significant system incidents on the Other

Transmission System in the case of an Operation
and/or Event occurring on the Transmission
System.
OC 8.3.1.1.4 significant system incidents on the Externally

Connected Parties in the case of an Operation
and/or Event occurring on the DISCOs, Provincial
Companies, Interconnectors and SPTLs.
OC 8.3.1.2. The requirement to notify in OC.8.1 relates generally to
notification of what is expected to happen or what has happened.
However, as OC.8.1 provides, when an Event or Operation has
occurred on the Transmission System which itself has been caused
by (or exacerbated by) an Operation or Event on a User System,
the SO in reporting the Event or Operation on the Transmission
System to another User or External System Operator as the case
may be, can pass on what it has been told by the User under
OC.8.1 in relation to the Operation or Event on the first User
System.
OC 8.3.1.3. Much of the information that the SO will require to analyse
Significant System Incidents may be available by means of:
OC 8.3.1.3.1 The SO’s SCADA system(s) and other data collection

systems; and
OC 8.3.1.3.2 Information provided to the SO by Users under other

codes of the Grid Code.
OC 8.3.1.3.3 Information provided to the SO by Other SOs based on

Interconnectors Contract Agreement
OC 8.3.1.4. In order to ensure that the SO receives as rapidly as practicable
the information it needs to operate the Transmission System,
and to ensure that no information is missed, this OC.8.1 sets out
a comprehensive set of requirements. It also provides for
information to be submitted to Users, in order to assist Users.
Where an obligation exists elsewhere to provide data to the SO the
User is not required also to provide data under OC.8.1.
OC-8
OC 8.3.2. Objective
OC 8.3.2.1.1 The objective of OC.8.1 is to provide for the exchange

of information so that the implications of an
Operation and/or Event can be considered, possible
risks arising from it can be assessed and appropriate
action taken by the relevant party in order to assist in
maintaining the integrity of the Power System.
OC 8.3.3. Scope
OC 8.3.3.1. OC.8.1 applies to the SO and to Users, which term in OC.8.1
means:
 Generators;
 Interconnector Operators;
 Dispatchable NSYGs;
 Distribution System Operator;
 Demand Customers; and
 Demand Side Unit Operators.
OC 8.3.3.2. It is required that as part of the fulfilment of obligations under this

OC.8.1, both the SO and Users will take into account information
they have received from third parties in determining whether an
Operation or an Event is to occur, or has, occurred.
OC 8.3.4. Requirement to Notify

OC 8.3.4.1. Notwithstanding the general requirements to notify set out in this
OC.8.1, the SO and Users shall agree to review from time to time
which Operations and Events are required to be notified.
OC 8.3.5. Notification of an Operation

OC 8.3.5.1. The SO will notify the User, (save in circumstances as provided for
under OC.8.1.5.2), of Operations on the Transmission System,
which will have (or may have), in the reasonable opinion of the SO,
an Operational Effect on the User. Except as agreed with the SO,
the User shall not pass on the information contained in a
notification to it from the SO under this OC.8.1 to any other person.
OC 8.3.5.2. In circumstances where it is not possible to invoke standing

procedures prior to the occurrence of an Operation or in the event
that the SO needs to implement Operations urgently and without
informing the User then, unless the situation is of a temporary
nature, i.e. less than 15 minutes, and has been rectified to normal,
the SO shall inform the User of the occurrence of the Operations,
without undue delay. The SO shall also inform the User as to the
likely duration of the condition and shall update this prognosis as
appropriate. The SO shall additionally inform the User as soon as
reasonably possible when the condition has ended.
OC 8.3.5.3. The User will notify the SO of Operations on the User's System
which will have (or may have) an Operational Effect on the
Transmission System. The SO may use this information in notifying
any other User(s) on whose System(s) the operation will have, or
OC-8
may have, in the reasonable opinion of the SO, an Operational
Effect, in accordance with this OC.8.1.
OC 8.3.6. Form of Notification of an Operation
OC 8.3.6.1. A notification (and any response to any questions asked under

OC.8.1.6.3), of an Operation shall be of sufficient detail to describe
the Operation (although it need not state the cause) and to enable
the recipient of the notification reasonably to consider and assess
the implications and risks arising.
OC 8.3.6.2. A notification will include the name (and job title) of the individual
reporting the Operation on behalf of the SO or the User, as the
case may be.
OC 8.3.6.3. The recipient of the notification may ask questions to clarify the
notification and the giver of the notification will, insofar as he is
able, answer any questions raised.
OC 8.3.7. Recording of an Operation
OC 8.3.7.1. The notification shall be given In Writing whenever possible before

carrying out an Operation. If there is insufficient time before the
Operation is scheduled to take place for notification to be given In
Writing, then the notification shall be given orally and if either the
User or the SO requests, it shall be submitted In Writing.
OC 8.3.8. Timing in Respect of an Operation

OC 8.3.8.1. A notification under Section OC.8.1.5 will be given as far in
advance as possible and in any event shall be given in sufficient
time as will reasonably allow the recipient to consider and assess
the implications and risks arising.
OC 8.3.9. Notification of Events

OC 8.3.9.1. The SO will notify the User of Events which in the reasonable
opinion of the SO are Significant System Incidents having an
Operational Effect on the User. Except as agreed with the SO, the
User may not pass on the information contained in a notification to
it from the SO to any other person.
OC 8.3.9.2. The User will notify the SO of Events which may be Significant
System Incidents affecting the Transmission System. The SO may
use this information in notifying any other Users on whose
System(s) the Significant System Event will have, or may have, in
the reasonable opinion of the SO, an Operational Effect.
OC 8.3.9.3. The SO will notify the Other SO of Events which in the reasonable
opinion of the SO are Significant System Incidents having an
Operational Effect on the Other SO. Except as agreed with the SO,
the Other SO may not pass on the information contained in a
notification to it from the SO to any other person.
OC 8.3.10. Form of Notification of an Event
OC 8.3.10.1. A notification (and any response to any questions asked under

Section OC.8.1.10.3) of an Event, will describe the Event,
OC-8
pursuant to Section OC.8.1.9 although it need not state the cause
of the Event, and, subject to that, will be of sufficient detail to
enable the recipient of the notification reasonably to consider and
assess the implications and risks arising.
OC 8.3.10.2. A notification will include the name (and job title) of the
individual reporting the Event on behalf of the SO or the User, as
the case may be.
OC 8.3.10.3. The recipient of the notification may ask questions to clarify the
notification and the giver of the notification will, insofar as he is
able (although he need not state the cause of the Event) answer
any questions raised.
OC 8.3.10.4. The owner of the system on which the Significant System Incident
occurred is required to provide a written report to the requesting
party confirming information given orally under Operation Code No
8.
OC 8.3.10.5. The report shall contain as a minimum the information detailed in
Appendix 1 of this sub-code. The report shall also include any
additional information that has come to light following the initial
verbal report of the Event.
OC 8.3.10.6. The recipient of the report shall not pass it on to a third party. The
recipient may, however, use the information to prepare a report for
another party.
OC 8.3.11. Provision of Further Information

OC 8.3.11.1. When an Event has been reported to the SO by a Generator,
Interconnector Operators, External Connected Parties, Generator
Aggregators, or Demand Side Operators, under OC.7.1 and it is
necessary in order for the Generators, Interconnector Operators,
External Connected Parties, Generator Aggregators, or Demand
Side Operators, to assess the implications of the Event on their
system more accurately, Generators, Interconnector Operators,
External Connected Parties, Generator Aggregators, or Demand
Side Operators, may ask the SO for details of the fault levels from
the Transmission System to their Generating Unit or Interconnector
or the to their Connection Point as the case may be, at the time of
the Event, and the SO will, as soon as reasonably practicable, give
the Generators, Interconnector Operators, External Connected
Parties, Generator Aggregators, or Demand Side Operators that
information provided that the SO has that information.
OC 8.3.12. Recording of an Event

OC 8.3.12.1. Notification of an Event pursuant to Section OC.8.1.9 shall be given
orally in the first instance. Significant System Incidents must be
reported In Writing if requested by either the User or the SO.
OC 8.3.13. Timing in Respect of an Event

OC 8.3.13.1. A notification of an Event under section OC8.1.9 shall be given as
soon as practicable after the occurrence of the Event, or time that
the Event is known of or anticipated by the giver of the notification
under OC.8.1, and in any event, except in an emergency ,within
fifteen minutes of such time.
OC-8
OC 8.4 SYSTEM OPERATOR WARNINGS
OC 8.4.1. The System Operator System Warnings are required to give information
relating to System conditions and Events. They are intended to alert
Operators of Power Plants, transmission-connected Consumers, distribution
companies and the Operators of Interconnectors of possible or actual
shortages of power generation, and the likely duration to enable these
Entities to prepare for subsequent instructions that may be issued by the
System Operator.
OC 8.4.2. A Warning relating to Demand reduction shall only be issued to Entities that
shall receive subsequent Load Demand reduction instructions. If the
System Operator considers that the reason for issuance of a System
Operator's System Warning shall be restricted to a geographic area or a
part of the sub-system, the circulation of the Warning may be appropriately
limited.
OC 8.4.3. The warning to Code Participant that include many Generating Units and/or
Demand reduction shall be issued to a single centralised control facility as
stated in OC.8.5.5 & OC.8.5.9.
OC 8.4.4. The System Operators System Warnings shall be issued in the form of:
OC 8.4.4.1. Inadequate system power Operating Margin Warnings which shall

detail the period of the warning, the shortfall and the foreseen
consequences.
OC 8.4.4.2. High risk of Load Demand reduction Warnings shall be issued
following the issuance of an inadequate system Power Operating
Margin Warnings when the need to actually reduce load demand is
foreseen. The possible level of load demand reduction shall be
indicated.
OC 8.4.4.3. Load Demand control imminent warnings (and may be issued when
no other warnings have been issued) shall be issued when Load
Demand reduction is expected within next 30 minutes. A Load
Demand control imminent Warning is valid for two hours unless
rescinded or re-issued.
OC 8.4.4.4. Risk of system disturbance warning shall be issued when there is a
widespread risk of system disturbance. On receipt of such a
warning, the recipients shall lake action to ensure a rapid response
to any problems.
OC 8.4.5. All Parties shall agree on the office locations to which Notices shall be
issued and the means of transmission of the System Warning as stated in
OC.8.5.4.
OC 8.4.5.1. The System Warning procedure is reflected in Appendix 1 of this
sub-code.
OC 8.5 OPERATIONAL COMMUNICATION AND DATA RETENTION
OC 8.5.1.1. It is necessary that adequate communication facilities and
procedures are established between the SO and Users to allow the
timely transfer of information, in order that the SO may fulfil its
obligations with regard to the operation of the Transmission
System.
OC 8.5.2. Objective
The objectives of OC.8.5 are:
OC-8
OC 8.5.2.1. to establish contact locations for the SO and each class of User;
OC 8.5.2.2. to detail the communication facilities required between the SO and
each class of User;
OC 8.5.2.3. to establish the general procedures (notwithstanding any specific
procedures which may be established in other sections of this Grid
Code) for communication of information between the SO and
Users; and
Code) for the authorisation of the SO personnel to act on behalf of
the SO and User personnel to act on behalf of the ser in the
communication of information between the SO and Users.
Code) for the retention of data.
OC 8.5.2.6. Pursuant to this OC.8.5 both the SO and Users will be obliged to
adopt the use of new technologies and methodologies for
communication of information, where there is a recognisable
benefit from doing so, and to do so would be reasonable in the
circumstances.
OC 8.5.2.7. This OC.8.5 covers the general procedures for all forms of
communication of operational information between the SO and
Users, other than the pre-connection communication that is dealt
with in the Connection Conditions. Data relating to Commercial
(Energy) Metering is specifically not covered by this OC.8.5.
OC 8.5.3. Scope
OC 8.5.3.1. OC.8.5 applies to the SO and to Users, which term in OC.8.5
means:
 Generators;
 Interconnector Operators;
 Dispatchable NON-Synchronous Generators;
 Distribution System Operator;
 Demand Customers; and
 Demand Side Unit Operator
 Provincial Companies and
 SPTL Companies.
OC 8.5.4. Contact Locations

OC 8.5.4.1. The System Operator
OC 8.5.4.1.1 Other than where specifically provided for under

Section OC.8.5.4.1.2 or in other sections of the Grid
Code, the contact location within the SO for
communication on matters pertaining to the real time
operation of the Transmission System shall be the
National Control Centre (NCC) or if designated
under Section OC.8.5.6.2 the Emergency Control
Centre (ECC).
OC-8
OC 8.5.4.1.2 The SO will, from time to time, notify to Users the
relevant points of contact in the SO (and their contact
details) and any changes to such points of contact
and/or details for the purposes of each section of this
Grid Code (including, where appropriate, for specific
purposes under each section), and the User shall, as
required, contact the relevant notified points of
contact.
OC 8.5.4.1.3 The SO shall from time to time distribute to each User an

organisational chart and list of personnel and contact
numbers (consistent with the notification given under
Section OC.8.5.4.1.2) in order to assist the User in
communicating with the SO.
OC 8.5.5. Generators & Generator Aggregators (G&GA)
OC 8.5.5.1. Unless otherwise specify anything in this sub-code addresses both

Generators and Generator Aggregators
OC 8.5.5.1.1 The G&GA contact locations and personnel referred to in

this Section OC.8.5.5.1 shall be notified by the G&GA to
the SO prior to connection and thereafter updated as
appropriate. For GA a single contact location and personnel
is required
OC 8.5.5.1.2 Each G&GA is required to provide a single Control Facility.

The G&GA shall ensure acting in accordance with Good
Industry Practice that the Control Facility is staffed at
appropriate staffing levels at all times.
OC 8.5.5.1.3 The Control Facility shall be staffed by a Responsible

Operator(s) who shall respond to communications from
the SO without undue delay (except where otherwise
provided for by agreement between the G&GA and the
SO, such agreement not to be unreasonably withheld) and
are of suitable experience and training and are authorised
to perform the following functions on behalf of the G&GA:
 to accept and execute Dispatch Instructions;

 to receive and acknowledge receipt of requests, for
amongst other matters, operation outside the Declared
values of Availability, Ancillary Service capability, or
Operating Characteristics of the Generating Units
during System Emergency Conditions.
OC 8.5.5.2. At any point in time, a single person shall be designated by the

G&GA and notified to the SO as the Responsible Manager. The
Responsible Manager shall be responsible for dealing with the SO
on matters relating to the Grid Code other than as provided for in
OC.8.5.5.1.2 and OC.8.5.5.1.3. In the event that the Responsible
Manager is not a person on duty at the Control Facility, then the
Responsible Manager must be capable of being contacted from the
Control Facility at all times, and in the event that the SO issues a
request to the Control Facility requiring the Responsible Manager
OC-8
to contact the NCC, the Responsible Manager shall comply with the
request without undue delay and in any case within 15 minutes of
the request.
OC 8.5.5.3. The Responsible Manager shall be authorised by the G&GA to

perform the following functions on behalf of the G&GA:
 to make estimates in accordance with Good Industry

Practice as to the available Availability, Ancillary
Service capability and Operating Characteristics of
each Generating Unit;
 to make Declarations for each Generating Unit;
 to communicate with respect to issues regarding

Outages of each Generating Unit.
OC 8.5.5.4. The G&GA may, from time to time, notify a replacement contact
location and personnel which meets the foregoing requirements.
OC 8.5.6. Demand Customers
OC 8.5.6.1. The Demand Customers contact locations and personnel referred

to in this Section OC.8.5.6 shall be notified by the Demand
Customer to the SO prior to connection and thereafter updated as
appropriate.
OC 8.5.6.2. The Demand Customer is required to provide the SO with the

contact information of a Responsible Operator(s) who shall respond
to communications from the SO without undue delay (except where
otherwise provided for by agreement between the Demand
Customer and the SO, such agreement not to be unreasonably
withheld) and are of suitable experience and training and are
authorised to perform functions on behalf of the Demand Customer.
OC 8.5.6.3. The Responsible Operator shall have the ability to attend the Site
of the Demand Customer within 60 minutes of an instruction to do
so being issued by the SO.

Demand Customer and notified to the SO as the Responsible
Manager. The Responsible Manager shall be responsible for dealing
with the SO on matters relating to the Grid Code other than as
provided for in OC.8.5.6.2 and OC.8.5.6.3. In the event that the
Responsible Manager is not a person on duty at the Site of the
Demand Customer , then the Responsible Manager must be
capable of being contacted from the Site of the Demand Customer
at all times, and in the event that the SO issues a request to the
Site of the Demand Customer requiring the Responsible Manager
to contact the NCC, the Responsible Manager shall comply with the
request without unreasonable delay and in any case within 15
minutes of the request.
OC 8.5.7. DISCO, Provincial and SPTL Companies
OC 8.5.7.1. The DISCO, Provincial and SPTL Companies contact locations

and personnel referred to in this Section OC.8.5.7 shall be notified by
OC-8
the DISCO, Provincial and SPTL Companies to the SO prior to
connection and thereafter updated as appropriate.
OC 8.5.7.2. The DISCO, Provincial and SPTL Companies is required to
provide a Control Facility. The DISCO, Provincial and SPTL
Companies shall ensure acting in accordance with Good Industry
Practice that the Control Facility is staffed at appropriate staffing
levels at all times.
OC 8.5.7.3. The DISCO, Provincial and SPTL Companies shall operate its
Control Facility according to the provisions agreed with the SO in any
agreements between the DISCO, Provincial and SPTL
Companies and the SO, such agreement not to be unreasonably
withheld.
OC 8.5.8. Dispatchable NON-synchronous generators (NSYG)
OC 8.5.8.1. he Dispatchable NSYG’s contact locations and personnel referred to

in this Section OC.8.5.8 shall be notified by the Dispatchable NSYG
to the SO prior to connection and thereafter updated as appropriate.
OC 8.5.8.2. The Dispatchable NSYG is required to provide a Control Facility. The
Dispatchable NSYG shall ensure acting in accordance with Good
Industry Practice that the Control Facility is staffed at appropriate
staffing levels at all times.
OC 8.5.8.3. The Control Facility shall be staffed by a Responsible Operator(s)
who shall respond to communications from the SO without undue
delay (except where otherwise provided for by agreement between
the Dispatchable NSYG and the SO, such agreement not to be
unreasonably withheld) and are of suitable experience and training
and are authorised to perform the following functions on behalf of
the Dispatchable NSYG:
OC 8.5.8.3.1 to accept and execute Dispatch Instructions as per

Schedule; and
OC 8.5.8.3.2 to receive and acknowledge receipt of requests, for
operation of the Dispatchable NSYG during System
Emergency Conditions.

Dispatchable NSYG and notified to the SO as the Responsible
provided for in OC.8.5.8.2 and OC.8.5.8.3. In the event that the
Responsible Manager is not a person on duty at the Control
Facility, then the Responsible Manager must be capable of being
contacted from the Control Facility at all times, and in the event
that the SO issues a request to the Control Facility requiring the
Responsible Manager to contact the NCC, the Responsible Manager
shall comply with the request without undue delay and in any case
within 15 minutes of the request.
OC 8.5.8.5. The Responsible Manager shall be authorised by the Dispatchable

NSYG to perform the following functions on behalf of the
Dispatchable NSYG:
OC-8
OC 8.5.8.5.1 to submit and revise an Availability Notice and other data
under SDC1 for the Dispatchable NSYG.
OC 8.5.8.5.2 to communicate with respect to issues regarding Outages
of the Dispatchable NSYG.
OC 8.5.8.6. The Dispatchable NSYG may, from time to time, notify a replacement
contact location and personnel which meets the foregoing
requirements.
OC 8.5.9. Interconnector Operators
OC 8.5.9.1. The Interconnector Operator contact locations and personnel

referred to in this section OC.8.5.9 shall be notified by the SO prior
to connection and thereafter updated as appropriate.
OC 8.5.9.2. The Interconnector Operator is required to provide a Control
Facility. The Interconnector Operator shall ensure acting in
accordance with Good Industry Practice that the Control Facility is
staffed at appropriate levels at all times.
OC 8.5.9.3. The Control Facility shall be staffed by a Responsible Operator(s)
who shall respond to communications from the SO without undue
delay (except, where otherwise provided for by agreement
between the Interconnector Operator and the SO, such agreement
not to be unreasonably withheld) and are of suitable experience
and training and are authorised to perform the following functions
on behalf on the Interconnector Operator:
OC 8.5.9.3.1 to accept and execute Dispatch Instructions;
Operating Characteristics of the Interconnectors during
System Emergency Conditions.

Interconnector Operator and notified to the SO as the Responsible
provided in OC.8.5.9.2 and OC. 8.5.9.3. In the event that the
Responsible Manager is not the person on duty at the Control
Facility, then the Responsible Manager must be capable of being
contactable from the Control Facility at all times, and in the event
that the SO issues a request to the Control Facility requiring the
Responsible Manager to contact the NCC, the Responsible Manager
will comply without undue delay and in any case within 15 minutes
of the request.
OC 8.5.9.5. The Responsible Manager shall be authorised by the Interconnector
Operator to perform the following functions on behalf of the
Interconnector Operator:
OC 8.5.9.5.1 to make estimates in accordance with Good Industry

Practice as to the Availability, Ancillary Service capability
and Operating Characteristics of the Interconnector;
OC 8.5.9.5.2 to make Declarations for the Interconnector;
of the Dispatchable NSYG.
OC-8
The Interconnector Operator may, from time to time, notify a replacement contact location
and personnel which meets the foregoing requirements.
OC 8.5.10. Demand Side Operator

OC 8.5.10.1. Demand Side Unit Operators are required to provide a Control
Facility. The Demand Side Unit Operator shall ensure acting in
accordance with Good Industry Practice that the Control Facility is
staffed with appropriate staffing levels at all times.
OC 8.5.10.2. For Demand Side Unit Operator, the Control Facility shall be
staffed by a Responsible Operator(s) who shall respond to
communications from the SO without undue delay (except where
otherwise provided for by agreement between the Demand Side
Unit Operator and the SO, such agreement not to be unreasonably
withheld) and are of suitable experience and training and are
authorised to perform functions on behalf of the Demand Side Unit
Operator as follows:
OC 8.5.10.2.1 to accept and execute Dispatch Instructions;
values of Demand Side Unit MW Availability.

Demand Side Unit Operator and notified to the SO as the
Responsible Manager. The Responsible Manager shall be
responsible for dealing with the SO on matters relating to the Grid
Code. In the event that the Responsible Manager is not a person on
duty at the Control Facility of the Demand Side Unit Operator, then
the Responsible Manager must be capable of being contacted from
the Control Facility of the Demand Side Unit Operator at all times,
and in the event that the SO issues a request to the Control Facility
of the Demand Side Unit Operator requiring the Responsible
Manager to contact the NCC, the Responsible Manager shall
comply with the request without unreasonable delay and in any
case within 15 minutes of the request.
OC 8.5.10.4. The Responsible Manager shall be authorised by the Demand Side

Unit Operator to perform the following functions on behalf of the
Demand Side Unit Operator:
OC 8.5.10.4.1 to make estimates in accordance with Good Industry
Practice as to the
OC 8.5.10.4.2 to make Declarations of the Demand Side Unit MW
Availability for Demand Side Unit Operator; and
of each Individual Demand Site within the Demand Side
Unit.
The Demand Side Unit Operator may, from time to time, notify a replacement contact location
and personnel which meets the foregoing requirements.
OC 8.5.10.5. Unless otherwise agreed with the SO, each Individual Demand Site
comprising a Demand Side Unit shall have a Responsible Operator
that must be capable of being contacted from the Control Facility
of the Demand Side Unit Operator at all times and is capable of
being at the Individual Demand Site within 1 hour of request to
respond to any query or issue from the Responsible Operator at the
Control Facility of the Demand Side Unit Operator or the SO.
OC-8
OC-8
OC 8 APPENDIX 1
Report of a Significant System Incident
Information (where relevant) to be given
1. Time and date of Significant System Incident
2. Location
3. Plant/Apparatus involved
4. Description of the Significant System Incident
5. Demand/Generation lost
6. Generating Unit Frequency
7. Generating Unit MVAr performance
8. Estimated duration of non-availability of Power Plant or that of Demand interruption.
OC-8
COMMUNICATION SYSTEM
CONTENTS
OC 9.1 COMMUNICATION SYSTEM............................................................................. 228
OC 9.2 SUPERVISORY CONTROL AND DATA ACQUISITION (SCADA).............................. 228
OC 9.3 Communications........................................................................................... 229
OC 9.4 Communication Between the SO and External SO........................................... 230
OC 9.5 Data Retention............................................................................................. 230
OC-9
COMMUNICATION SYSTEM
OC 9.1 COMMUNICATION SYSTEM
OC 9.1.1. The minimum communications facilities which are to be installed and

maintained between the SO and the User are defined in this Section
OC.9.1.
The Transmission Network Operator shall provide at least dual high-speed network-wide
communication system, to provide for the communications facilities, installed on its system,
and the Code Participants facilities.
Communication systems shall provide channels for direct telephone, facsimile and SCADA
links (Remote Terminal Unit) between the SO and Code Participants. The communication
facility shall be used for communicating with Transmission Network Operator work crew and
grid substation personnel. An electronic recording device shall be provided at the SO to record
all dispatch transactions and communication with the work crews.
The Transmission Network Operator shall provide the communication system and extend the
facility to the Connection Point with the Code Participants for the network under its
jurisdiction.
The Transmission Network Operator shall operate, maintain, expand and upgrade from time to
time, this Supervisory Control and Data Acquisition (SCADA) system and a supporting
dedicated communication system.
The Transmission Network Operator shall provide all Code Participants specifications for RTU's,
communications system requirements and protocols, and technical assistance required to
connect and functionally integrate Code Participants' facilities into the SCADA system.
OC 9.1.2. All equipment to be provided by Users under this Section OC.9.1 shall
comply with the applicable International Telecommunications Union (ITU)
and International Electrotechnical Commission (IEC) standards for SCADA
and communications equipment and shall meet such standards as notified
by the SO, acting reasonably, in advance of their design or procurement
(whichever is later) and shall be provided at the cost of the User, except
where otherwise specified
The SCADA and SCADA Communication System shall be used by The Transmission Network
Operator and Code Participants to monitor and control the National transmission network,
including 1100 kV, 765 kV, 500 kV and 220 kV grid stations, and to dispatch Generators
connected to the transmission network. The SCADA system shall also include data from
Generators and other Code Participant facilities as required by NTDC.
OC 9.2 SUPERVISORY CONTROL AND DATA ACQUISITION (SCADA)
OC 9.2.1. SCADA remote terminal equipment shall be required in the control room of
the Transmission Station at the User Site for the transmission of signals and
indications to and from the NCC. The signals and indications which must be
provided by Users for transmission by SCADA equipment to the NCC are the
signals and indications referred to under Connection Conditions together
with such other information as the SO may from time to time by notice to
Users reasonably require.
OC 9.2.2. For Demand Side Unit Operators & Generator Aggregators, SCADA remote
terminal equipment shall also be required at the Control Facility for the
transmission of signals and indications to and from the NCC. The signals
and indications which must be provided by Demand Side Unit Operators &
Generator Aggregators for transmission by SCADA equipment to the NCC
are the signals and indications referred to under Connection Conditions
OC-10
together with such other information as the SO may from time to time, by
notice to Demand Side Unit Operators & Generator Aggregators,
reasonably require.
OC 9.2.3. Interface cabinets shall be installed in the control room of the Transmission
Station at the User Site and also on the User's Site or, in the case of a
Demand Side Unit Operator, in the User’s Control Facility. Provision and
maintenance of wiring and signalling from the User's Plant and Apparatus
to the User's interface cabinet shall be the responsibility of the User. The
SO shall provide the cables to interconnect these interface cabinets
OC 9.2.4. Computer Equipment

OC 9.2.4.1. Each User shall comply with the SO requirements and provide
appropriate computer and data networking equipment to allow
data exchange such as electronic mail, dispatch instructions etc
between the SO and the User. The equipment shall only be used by
the User for operational communications with the SO.
OC 9.2.4.2. Each User shall be responsible for optimising the reliability and
security of the computer equipment, referred to in OC.9.2.4,
including the provision, at no charge, of an uninterruptible power
supply
OC 9.2.5. Telephone/Fascimile
OC 9.2.5.1. Each User shall be responsible for the provision and maintenance
(at the cost of the User) of telephone and facsimile equipment as
required by this Section OC.9.2.5.
OC 9.2.5.2. The SO may arrange for the provision of one or more telephone
extensions to be connected to the OPTEL system. This facility shall
be reserved for operational purposes only, and shall be
continuously attended by a person meeting the requirements of
OC.7.2.4.2.3, OC.7.2.4.3.3, or OC.7.2.4.4.3 (as appropriate) and
answered without undue delay. Users shall be responsible for the
provision at no charge of an uninterruptible power supply.
OC 9.2.5.3. Users shall provide a Public Switched Telephone Network circuit to
the Communications and Control Room.
OC 9.2.5.4. Users shall provide no fewer than two separate Public Switched
Telephone Network circuits to the Control Facility.
OC 9.2.5.5. Users shall provide no fewer than one telefacsimile unit, connected
to a dedicated Public Switched Telephone Network circuit at the
Control Facility
OC 9.2.6. All SCADA, metering equipment, computer and communications equipment
that interfaces with the SO and the information carried by it must be secure
from unauthorised access. Procedures governing security and access shall
be agreed with Users pursuant to the Operation Instructions, but shall allow
for adequate access to the equipment and information by the SO or its
service providers for the purposes of maintenance, repair, testing and the
taking of readings.
OC 9.2.7. Time Standards

OC 9.2.7.1. Time will be set by a standard determined by the SO. The time
standard will be broadcast to relevant telecommunications devices
in order to maintain time coherence.
OC 9.3 Communications
OC 9.3.1. Communication Between the SO and the User

OC 9.3.1.1. Other than where specifically provided for in other sections of the
Grid Code, communication between the SO and Users on matters
OC-10
pertaining to the real time operation of the Transmission System
shall take place between the NCC and the User's Control Facility.
OC 9.3.1.2. If the NCC is to be moved to a different location the SO shall
ordinarily notify Users not more than one Business Day after the
move, but in the event of an emergency it may instead notify Users
as soon as practicable after the move
OC 9.3.1.3. Unless otherwise specified in the Grid Code, all instructions given
by NCC and communications between NCC and the User's Control
Facility shall be given by means of the facilities described in
OC.7.2.5.
OC 9.3.1.4. Any automatic recording (by whatever means) of communications
given by means of telephony, electronic means, facsimile transfer
or telex will be accepted by the SO and Users as evidence of those
instructions or communications.
OC 9.4 Communication Between the SO and External SO
OC 9.4.1. For Interconnectors, the procedure for operational liaison by the SO with the External
SO is set out in the Interconnector Technical Code and Contract Agreement
OC 9.4.2. Communication between the SO and External SO on the real time operation of the
Transmission System regarding Interconnectors shall take place between the NCC
and the External System’s Control Facility
OC 9.4.3. Data and Notices

OC 9.4.3.1. Data and notices to be submitted to the SO or to Users under the
Grid Code (other than data and notices which are the subject of a
specific requirement of the Grid Code as to the manner of their
delivery) shall be In Writing and shall be delivered by hand or sent
by pre-paid post, by telex, receipted email or telefacsimile transfer.
OC 9.4.3.2. Data and notices to be submitted to the SO under the Grid Code
shall be addressed to the person, and at the address, notified by
the SO to Users for such purpose, following entry into the
Connection Agreement or for a Demand Side Unit & Generators
Aggregators prior to issuance of the Operational Certificate, or to
such other person or address, as the SO may notify to Users from
time to time.
OC 9.4.3.3. Data and notices to be submitted to Users under the Grid Code
shall be addressed to the User's nominated representative (at the
address notified by Users to the SO following entry into the
Connection Agreement or for a Demand Side Unit prior to issuance
of the Operational Certificate for such purpose (and failing such
notification to the principal office of the addressee)), or to such
other person or address as Users may notify to the SO from time to
time.
OC 9.4.3.4. All data items, where applicable, will be referenced to nominal
Voltage and Frequency unless otherwise stated.
OC 9.4.3.5. All Operational Data is to be supplied in accordance with the
timetables set out in the Grid Code.
OC 9.5 Data Retention
OC 9.5.1. Operational Data is all data required to be supplied by either the SO or

Users under the Grid Code any other data expressly provided to be
Operational Data under the Grid Code. Operational Data to be supplied by
OC-10
the User must be submitted to the department or address as the SO may
from time to time advise.
OC 9.5.2. The SO and Users will keep all Operational Data confidential
OC 9.5.3. The SO shall maintain a complete and accurate record of all Operational
Data supplied or maintained under the Grid Code. The format for the
retention of records shall be as the SO may reasonably determine
(provided such format shall not prejudice its accessibility and
comprehension by the User under OC.7.2.8.4). All Operational Data shall be
so maintained for a period of not less than six (6) years commencing from
the date the Operational Data was first supplied (or first created, if earlier).
OC 9.5.4. The SO shall afford Users access to its records (and copies thereof) of
Operational Data and/or data required to be maintained under OC.7.2.8.3
on reasonable notice.
End of OC 9
OC-10
Operational Testing
CONTENTS
OC 10.1 INTRODUCTION............................................................................................. 233
OC 10.2 OBJECTIVE.................................................................................................... 233
OC 10.3 SCOPE.......................................................................................................... 233
OC 10.4 TESTS REQUIRED BY THE SO.......................................................................... 234
OC 10.5 TESTS REQUIRED BY THE USERS.................................................................... 234
OC 10.6 PROCEDURE FOR REQUESTING OPERATIONAL TESTS....................................... 234
OC 10.7 EVALUATION OF PROPOSED OPERATIONAL TESTS.......................................... 235
OC 10.8 APPROVAL FOR OPERATIONAL TESTING......................................................... 236
OC 10.9 SCHEDULING OF OPERATIONAL TESTS........................................................... 237
OC 10.10 DISPATCHING OF OPERATIONAL TESTS...................................................... 237
OC 10.11 TEST REPORTING...................................................................................... 238
OC 10.12 DISPUTES................................................................................................. 238
OC-10
OPERATIONAL TESTING
OC 10.1 INTRODUCTION
OC 10.1.1. OC.10 deals with the responsibilities and procedures for arranging and
carrying out Operational Tests which may have an effect on the Systems of
the SO and Users.
OC 10.1.2. By their nature, Operational Tests may impinge on either or both of:
 the SO's responsibilities in respect of the Transmission System, including
Dispatch of generation, Interconnectors and Demand Side Unit MW
Availability; and
 the operations of Users and the quality and continuity of supply of electricity
to Users.
OC 10.1.3. To minimise disruption to the operation of the Transmission System and to
the Systems of other Users, it is necessary that tests which affect the
operation of the Transmission System or Users’ Systems as under OC.10.1.2,
are subject to central coordination and control.
OC 10.1.4. To achieve the primary objective as outlined in OC.10.2.1, OC.10 sets out
procedures for establishing and reporting Operational Tests.
OC 10.2 OBJECTIVE
OC 10.2.1. The primary objective of OC.10 is to establish procedures for central co-
ordination and control of an Operational Test required by the SO or a User,
where such test will or may:
 affect the secure operation of the Transmission System; or

 have a significant effect on the operation of the Transmission System, the
Other Transmission System or a User's System; or
 affect the economic operation of the Transmission System or a User's System;
or
 affect the quality or continuity of supply of electricity to Users.
OC 10.2.2. By way of example, tests that are typical of those which may be expected to
be covered by OC.10 are listed in OC.10.4 to OC.10.5. This list is not
intended to be exhaustive and other tests which fall within the definition of
Operational Tests shall also be covered by the procedures outlined in this
OC.10.
OC 10.2.3. OC.10 is not intended to deal with tests which may be called routinely by
the SO in order to assess compliance of Users with their design, operating
and connection requirements as specified in the Grid Code and in each
User's Connection Agreement, Ancillary Services Agreements and System
Support Agreement, or to assess that Generators or Interconnector
Operators are in compliance with their Registered Data as notified by
Declarations, where appropriate, or to determine that Generation Units or
Interconnectors are in compliance with Dispatch Instructions. These issues
are covered under OC.XX (Monitoring, Testing and Investigation).
OC 10.3 SCOPE
OC 10.3.1. Generators which includes all Generators with units with Registered
Capacity greater than 5 MW and Generator Aggregators;
OC 10.3.2. Interconnectors;
OC-11
OC 10.3.3. Demand Side Unit Operators;
OC 10.3.4. The Distribution System Operator; and
OC 10.3.5. Demand Customers.
OC 10.4 TESTS REQUIRED BY THE SO
OC 10.4.1. The SO as operator of the Transmission System will in accordance with

Prudent Utility Practice, needs to carry out Operational Tests in order to
maintain and develop operational procedures, to train staff, and to acquire
information in respect of Power System behaviour under abnormal system
conditions. The SO will endeavour to limit the frequency of occurrence,
scope, extent of effects and type of Operational Tests to those that are
required by Prudent Utility Practice
OC 10.4.2. Operational Tests required by the SO from time to time shall include, but
shall not be limited to the following:
(i) Tests involving the controlled application of Frequency and/or Voltage

variations aimed at gathering information on Power System behaviour;
(ii) Power System Restoration Tests;
(iii) Testing of standing procedures for System Emergency Conditions and Alert
conditions
(iv) Testing or monitoring of Power Quality under various Power System

conditions and Dispatch configurations.
OC 10.4.3. The provisions of OC.10.6, OC.10.7, OC 10.8, OC.10,10.4 and OC.10.11
shall not apply to Operational Tests required by the SO under this OC.10.4.
OC 10.4.4. Where the SO intends to carry out an Operational Test in accordance with
this OC.10.4 and, in the SO's reasonable opinion, such an Operational Test
will or may have an Operational Effect on a User’s System, the SO shall, in
accordance with OC.XXX (Information Exchange) provide such notice to the
User of the scheduled time and effect of the Operational Test as is
reasonable in all the circumstances and shall keep the User informed as to
any changes to the scheduled time and nature of the Operational Test.
OC 10.4.5. Where a User, having been informed about an Operational Test under
OC.10.4.4 may, acting reasonably, contact the SO to request additional
time to consider the impact of the test on the User. The SO shall co-operate
with the User to assess the risks. The test shall not proceed until all Users
are satisfied unless, in the SO’s view, a User is acting unreasonably.
OC 10.5 TESTS REQUIRED BY THE USERS
OC 10.5.1. Operation of Users’ Plant in accordance with Good Industry Practice

requires Operational Testing in order to maintain and develop operational
procedures, develop and measure Plant performance, comply with
statutory or other industry obligations and to train staff.
OC 10.5.2. In accordance with Good Industry Practice each User shall endeavour to
limit the frequency of occurrence of Operational Tests and to limit the
effects of such Operational Tests on the Transmission System.
OC 10.5.3. Operational Tests can comprise of a Significant Test and/or a Minor Test.
OC 10.6 PROCEDURE FOR REQUESTING OPERATIONAL TESTS
OC 10.6.1. Users shall submit proposals for an Operational Test in a timely fashion in
accordance with OC7 (Information Exchange) or alternative procedures
agreed with the SO. Notwithstanding the other requirements in OCXX, in
OC-11
the case of a Significant Test, Users shall submit proposals to the SO at
least five Business Days before the test start date or, with the agreement
of the SO, no later than 09:00 two Business Days before the test start date.
OC 10.6.2. As part of the proposal Users, when requesting an Operational Test, shall
supply sufficient detail to the SO to allow any operational consequences of
the test to be adequately assessed. This shall include the following
information:
OC 10.6.2.1. the reason for the proposed test indicating whether the
Operational Test is a test required by statute, required for
compliance with licence conditions, statutory regulations, or safety
codes, which may require that execution of the Operational Test be
expedited and given priority over other Operational Tests.
OC 10.6.2.2. The preferred time or times for the test;
OC 10.6.2.3. The milestones for individual stages of the Operational Test (if any)
which can be completed separately, and/or do not require to be
repeated if the Operational Test is interrupted by the SO after
completion of each stage;
OC 10.6.2.4. Whether there may be an adverse material impact on the User if
the Operational Test is cancelled at short notice or delayed
(reasonable detail being given by the User to the SO of the
impact).
OC 10.6.2.5. Where the User is a Generator, Interconnector Operator, Generator
Aggregator or Demand Side Unit Operator, the Dispatch or
Dispatches required by the Generator, Interconnector Operator,
Generator Aggregator or Demand Side Unit Operator for
completion of the test, if any, including the duration of Dispatch
shall be supplied to the SO as part of the proposal.
OC 10.6.2.6. Where the Generator, Interconnector Operator, Generator
Aggregator or Demand Side Unit Operator may not know the entire
Dispatches required for completion of the test until part of the test
is completed then the Generator, Interconnector Operator,
Generator Aggregator or Demand Side Unit Operator when
proposing the test shall:
• divide the test into sections as appropriate;
• indicate and discuss with the SO which sections of the test

can be completed in stages and which cannot; and
• indicate possible variations of the test for the sections that

can be completed in stages.
Additionally, the factors that influence the completion of the stages should be outlined to the
SO, namely, if the procedure to be followed for a certain stage depends on the outcome of a
previous stage.
OC 10.6.3. A request by the Generator, Interconnector Operator, Generator Aggregator

or Demand Side Unit Operator for an Operational Test requiring a
Generation Unit, Interconnector or Demand Side Unit to be Dispatched to a
particular MW Output or operating condition shall not be considered a Re-
declaration of Availability, Ancillary Service capability or Operating
Characteristics.
OC 10.7 EVALUATION OF PROPOSED OPERATIONAL TESTS
OC 10.7.1. The SO shall, on receipt of an Operational Test request from the User,
assess the impact of the proposed test on the operation of the Power
OC-11
System. The SO may request additional information from the User required
to evaluate the impact or impacts of the test.
OC 10.7.2. The SO will evaluate the impact (in terms of continuity and quality of
supply only) of the Operational Test with significantly affected Users. Any
reasonable objections from any such Operationally Affected Users shall be
considered. When discussing the Operational Test with any affected User,
the SO shall not disclose what it reasonably believes to be commercially
sensitive or otherwise potentially sensitive information to Users without the
consent of the User requesting the test
OC 10.7.3. Where an Operational Test proposed by a Generator, Interconnector
Operator, Generator Aggregator or Demand Side Unit Operator in respect of
one of its Generation Units, Interconnector or Demand Side Units requires a
Dispatch that exceeds the currently declared values of Availability,
Ancillary Service capability where applicable, or Operating Characteristics
of the Generation Unit, Interconnector or Demand Side Units, then the SO
may so Dispatch the Generation Unit, Interconnector or Demand Side Units
for the period required for the Operational Test, in accordance with the
relevant provisions of the Grid Code.
OC 10.8 APPROVAL FOR OPERATIONAL TESTING
OC 10.8.1. Following receipt of an Operational Test proposal and evaluation of the

Operational Test’s likely impact, including discussions of test requirements
with the User requesting the Operational Test and with Operationally
Affected Users as appropriate, the SO will decide if approval for the
requested Operational Test is granted.
OC 10.8.2. The criteria for approving Operational Test include:

OC 10.8.2.1. The impact of the Operational Test on Transmission System
operation security;
OC 10.8.2.2. The impact of the Operational Test on Transmission System
operation economics or on the economics of the operation of the
Other Transmission System;
OC 10.8.2.3. The impact of the Operational Test on other Users’ Systems;
OC 10.8.2.4. The effect of the Operational Test on continuity and quality of
electricity supply.
OC 10.8.3. On approval by the SO of an Operational Test proposed by a User, the SO

shall contact the User outlining the proposed Dispatch procedure and
schedule.
OC 10.8.3.1. On receipt of the proposed Dispatch procedure and schedule of

the Operational Test, the Test Proposer shall notify the SO without
undue delay, of the Test Proposer's acceptance or rejection of the
proposed Dispatch procedure and schedule for the test.
OC 10.8.3.2. On notification of rejection of the proposed Dispatch procedure
and schedule for the Operational Test by the Test Proposer, then
the Operational Test shall not take place. The Test Proposer may
enter into discussions with the SO as to an alternative schedule for
the Operational Test, or may request a different Operational Test
or may request the Operational Test at an alternative time.
OC 10.8.3.3. On notification of acceptance of the proposed Dispatch procedure

and schedule for the Operational Test by the Test Proposer, the SO
shall inform other Users as to the scheduled time and nature of the
test, if in the opinion of the SO those Users will or may be
OC-11
significantly affected by the test, or otherwise as dictated by
standing arrangements
OC 10.8.3.4. If Operationally Affected Users are not satisfied with the proposed
Operational Test, they shall advise the SO of their concerns. The
SO shall not cancel proposed Operational Test unless these
objections are reasonable. If Operationally Affected Users are still
not satisfied with the Operational Test being approved, then they
may appeal the decision to the NEPRA in accordance with 0.
OC 10.8.3.5. Notification by the SO to the Test Proposer of the proposed

Dispatch procedure and schedule for an Operational Test, or
notification by the Test Proposer to the SO of acceptance of the
proposed Dispatch procedure and schedule, does not constitute a
Dispatch Instruction from the SO to the Test Proposer.
OC 10.8.4. On rejection of the proposed Operational Test by the SO, the Test Proposer
may enter into discussions with the SO as to an alternative schedule for the
Operational Test, or may request a different Operational Test or may
request the Operational Test at an alternative time. If the amended
proposal for an Operational Test is approved by the SO, and the User
requesting the Operational Test is a Generator, then OC.10.8.3 shall apply.
If the Test Proposer is not satisfied that there are reasonable grounds for rejecting the
proposed Operational Test, then they may appeal to the NEPRA according to 0.
OC 10.9 SCHEDULING OF OPERATIONAL TESTS
OC 10.9.1. Operational Tests will usually, but not necessarily, be scheduled by the SO
in accordance with Schedule 1 .
OC 10.9.2. Where an Operational Test is requested by a User, the User shall submit
Physical Notifications consistent with planned Operational Tests in
accordance with Schedule and the Trading and Settlement Code consistent
with planned Operational Tests. The User shall also submit all other data as
normal as required under the Schedule.
OC 10.9.3. The SO shall use reasonable endeavours to prioritise Operational Tests
where the Test Proposer has notified the SO that Operational Tests are
required in accordance with licence conditions, statutory regulations or
safety codes or a delay in the execution of the tests may have an adverse
material impact on a User.
OC 10.10 DISPATCHING OF OPERATIONAL TESTS
OC 10.10.1. Dispatch Instructions for Operational Tests shall be issued by the SO in the
normal manner for issuing Dispatch Instructions in accordance with SDC2.
OC 10.10.2. The SO shall use reasonable endeavours to ensure that scheduled
Operational Tests are dispatched in accordance with the agreed Dispatch
procedures.
OC 10.10.3. Where the SO foresees a requirement or likely requirement to cancel,
postpone or otherwise significantly alter an agreed Dispatch procedure and
schedule, then the SO shall inform the Test Proposer as soon as reasonably
possible. In this case the provisions of OC.10.10.4 and OC.10.10.5 apply.
OC 10.10.4. Where the SO assesses that the impact of an Operational Test on
Transmission System security or on the continuity and quality of supply or
operation of a User may or is likely to be significantly greater than
OC-11
originally estimated, the SO may contact the Test Proposer to discuss a
revised test procedure or schedule
OC 10.10.5. The SO may where it considers it necessary cancel, interrupt or postpone
an Operational Test at any time, but shall where possible utilise the
procedures outlined under OC.8.10.4 prior to taking such action where the
cancellation, interruption or postponement is for other than technical
reasons.
OC 10.10.6. If the Test Proposer wishes to cancel an Operational Test either before
commencement of the test or during the test, the SO must be notified by
the Test Proposer, in accordance with OCXXX.
OC 10.11 TEST REPORTING
OC 10.11.1. Upon conclusion of the scheduled time for an Operational Test the Test
Proposer shall notify the SO as to whether the test has been completed, or
sections of the test if divided into sections under OC.10.6.2.3 have been
completed.
OC 10.11.2. At the conclusion of the Operational Test, the Test Proposer shall be
responsible for preparing a written report on the Operational Test (the
"Final Report") which shall be available within three months of the
conclusion of the Operational Test to the SO, Operationally Effected Users
and the NEPRA on request.
OC 10.11.3. The Final Report shall not be submitted to any person who is not a
representative of the SO or the Test Proposer unless the SO and the Test
Proposer having reasonably considered the confidentiality issues arising,
shall have unanimously approved such submission.
OC 10.11.4. The Final Report shall include a description of the Plant and/or Apparatus
tested and a description of the System Test carried out together with the
results, conclusions and recommendations as they relate to the SO and
Operationally Effected Users.
OC 10.12 DISPUTES
OC 10.12.1. Operationally Affected Users who consider that the implementation of the
proposed Operational Test will have a significant negative impact on them
may appeal to the NEPRA providing details of their objections.
OC 10.12.2. The Test Proposer has right of appeal to the NEPRA if it considers that
rejection of the proposed Operational Test is unreasonable.
End of OC 10
OC-11
Testing & Monitoring
CONTENTS
OC 11.2 OBJECTIVE.................................................................................................... 240
OC 11.3 MONITORING................................................................................................ 241
OC 11.4 PROCEDURE FOR TESTING............................................................................. 243
OC 11.5 INVESTIGATION............................................................................................ 245
OC 11.6 CONSEQUENCES OF MONITORING, TESTING AND INVESTIGATION....................246
OC 11.7 DISPUTATION OF ASSESSMENT OF NON-COMPLIANCE BY A USER....................251
OC 11.8 DISPUTE RESOLUTION PROCEDURE................................................................ 251
OC 11.9 BLACK START (BS) TESTING.......................................................................... 254
OC-11
TESTING & MONITORING
[All the references in this sub-code to Balancing Code, and Balancing Mechanism shall be
interpreted later when the Balancing Mechanism is Notified by the Authority]
OC 11.1.1. In order to discharge its responsibilities in respect of the safe, secure and
economic operation of the Transmission System and in respect of
generation Dispatch, the SO will need to carry out certain Monitoring,
Testing and Investigation in respect of the performance of Users’ Plant.
OC 11.1.2. This sub-code details the procedures to be followed by the System

Operator to monitor and assess the validity of any Generator,
Interconnector Operator, Generator Aggregator or Demand Side Unit
Operator, generation capability performances, and frequency declarations.
The System Operator is also required to monitor ancillary services which
Users have agreed to provide under their Agreement with the system
operator as and when requested by the System Operator.
OC 11.1.3. OC.XX does not apply to Operational Tests, which may be required by the
SO or by Users. The procedures by which Operational Tests are notified,
and approved, executed and reported, are covered under Operational
Testing (OCXX)
OC 11.1.4. The System Operator is required, subject to system conditions prevailing on

a given day to test any generator to ensure that it complies with the
requirements, specifications and obligations of the Connection Code (CC),
Power Purchase Agreement (PPA) and/or Power Station Operation &
Dispatch Agreement (PSODA) as applicable, to ensure that they are
available and comply with their notified procedures and related provisions.
The System Operator shall also undertake Black Start Test procedures to
ensure satisfactory operation in the event of an Emergency.
OC 11.2 OBJECTIVE
OC 11.2.1. The primary objectives of OC.11 are to establish procedures for Testing that
Users are operating within their design, operating and connection
requirements, as specified in the Grid Code, Connection Agreements,
Ancillary Services Agreements and System Support Agreements between
Users and the SO.
OC 11.2.2. OC 11 applies to the system operator and to Users:
 Generators, which, for the purposes of OC.11, include all Generators

with Generation Unit(s) subject to Central Dispatch or with
Generation Unit(s) that have a total Registered Capacity greater than
4 MW on a single Site;
 Distribution, Provincial & SPTLs Companies with Non-Embedded and
Embedded Generations;
 The system operator in relation to Consumers directly connected to the
National Transmission System;
 Other distribution licensees having Embedded Generation;
OC-11
 Generators Aggregators, in respect of the Generation Units which they
represent Demand Side Units Operators, in respect of their Demand Side
Units;
 Interconnectors Operators;
 Suppliers;
 Demand Customers.
OC 11.2.3. In order to achieve the primary objective set out in OC.11.2.1, OC.11
establishes procedures for Monitoring, Testing and Investigation. In
particular, this facilitates adequate assessment of each of the following:
OC 11.2.3.1. Whether Centrally Dispatched Generating Units (CDGU),
Interconnectors and Demand Side Units comply with Dispatch
Instructions;
OC 11.2.3.2. Whether Generators, Interconnectors, Demand Side Unit Operators,
DISCOS, Provincial and SPTL Companies and Generator Aggregators
are in compliance with Declarations of Availability, Ancillary Services
capabilities, Operating Characteristics and any other data required to
be registered by those Generators, Interconnectors and Demand
Side Unit Operators, DISCOS, Provincial and SPTL Companies and
Generator Aggregators under the Grid Code;
OC 11.2.3.3. Whether Power Quality of Users conforms with CC.11.13.1;
OC 11.2.3.4. Whether Users are in compliance with protection requirements and
protection settings under the Grid Code, Users' Connection
Agreements, Ancillary Service Agreements and System Support
Agreements between Users and the SO;
OC 11.2.3.5. Whether Fossil Fuel Generators have the ability to generate on
Primary Fuel and Secondary Fuel (where applicable) and have the
ability to carry out on on-line fuel changeover ; and
OC 11.2.3.6. Whether Generators have the required Secondary Fuel stock levels
at the Generator Site and Off-Site Storage Location.
OC 11.3 MONITORING
OC 11.3.1. The System operator is required to monitor the performance of:

 Users compliance with the Scheduling and Dispatch Code;
 Users providing the ancillary services they have agreed to provide; and
 Evaluate Generators against their expected input or output obtained from
the final notification
OC 11.3.2. Monitoring is normally continuous or continuous for periods of time, and is

carried out by monitoring, data recording and analysis or by such other
methods as the SO shall reasonably determine are appropriate in the
circumstances. It does not require advance notification from the SO to
Users.
Where a data recording and analysis system is used for Monitoring, the SO shall inform the
User that such data recording and analysis system is being used and, on request from the
User, shall make available to the User reasonable information in respect of the data recording
and analysis system.
OC 11.3.3. Monitoring may be carried out at any time by the SO and may result,
without the application of further Testing, in the evaluation by the SO of
User non-compliance. Where the User disputes a finding of non-compliance,
the SO shall provide the User with any data collected during Monitoring
over the period of alleged non- compliance and such other documentation
as is reasonably necessary to show evidence of non-compliance.
OC-11
OC 11.3.4. Performance parameters that the SO Monitor shall include, but are not
limited to, the following:
OC 11.3.4.1. Compliance with Dispatch Instructions;

OC 11.3.4.2. Compliance with Declarations including, without limitation, in
respect of:
 Primary, Secondary and Tertiary Operating
Reserve provided by each of a Generator’s
Generation Units, following a Low
Frequency Event on the Transmission
System;
 Frequency Regulation provided by each
Generation Unit (to confirm that it is
consistent with the Declared Governor
Droop); and
 Tertiary Operating Reserve 2 and
Replacement Reserve provided by each of a
Generator's Generation Units.
OC 11.3.4.3. Compliance with IEC Power Quality standards; and
OC 11.3.4.4. Provision of static and dynamic Reactive Power; and
OC 11.3.4.5. Monitoring of Primary Fuel and Secondary Fuel capability, on-line
changeover capability and fuel storage levels.
OC 11.3.5. Monitoring systems and procedures

OC 11.3.5.1. Procedures and systems used for assessment of compliance will be
either generic procedures (which will be provided by the SO) or
otherwise agreed between the SO and the User, such agreement
not to be unreasonably withheld.
OC 11.3.5.2. Compliance of Demand Side Units with Dispatch Instructions
A Demand Side Unit shall be deemed compliant with a Dispatch Instruction if:
 the Demand Side Unit MW Response of the Dispatch Instruction is achieved
in the Demand Side Unit MW Response Time and maintained until the
subsequent Dispatch Instruction or until the Maximum Down-Time of the
Demand Side Unit has elapsed; and
 the Demand Side Unit Performance Monitoring Percentage Error is less than
5% for each full quarter-hour Meter period of the Demand Side Unit MW
Response for 90% of the last ten Dispatches or 90% of the Dispatches in a
three-hundred and sixty-five day period.
or
 the Demand Side Unit Performance Monitoring Error is less than 0.250 MWh
for each full quarter-hour Meter period of the Demand Side Unit MW
Response in 90% of the last ten Dispatches or 90% of the Dispatches in a
three-hundred and sixty-five day period; and
 the Demand Side Unit Performance Monitoring Percentage Error is less than
10% for each full quarter-hour Meter period of the Demand Side Unit MW
Response.
or
OC-11
 the Demand Side Unit Performance Monitoring Error is less than 0.250 MWh
for each full quarter-hour Meter period of the Demand Side Unit MW
Response; and
 the Demand Side Unit Performance Monitoring Percentage Error is on

average less than 5% for each full quarter-hour Meter period of the Demand
Side Unit MW Response
or
 the Demand Side Unit Performance Monitoring Error is on average less than
0.250 MWh for each full quarter-hour Meter period of the Demand Side Unit
MW Response; and
 the Demand Side Unit SCADA Percentage Error is less than 5% or the
Demand Side Unit SCADA Error is less than 0.250 MWh.
OC 11.3.6. If there are any persistent failures of OC 11.2.1, (a), (b) & (c) by Users the
System Operator shall notify the User in writing requesting an explanation
of the action, the User shall have to comply with their obligations.
OC 11.3.7. The System Operator and the User shall discuss the proposed action and
endeavour to reach an agreement on the proposed action. If agreement
cannot be reached within 10 working days of notification of the failure by
the System Operator to the User, the System Operator or the User shall be
entitled to require a test as detailed in OC 11.3.
OC 11.4 PROCEDURE FOR TESTING
The SO may, from time to time, carry out Tests in order to determine that a User is complying with its
Connection Conditions, Registered Operating Characteristics and Declarations.
The SO may:
(a) from time to time and for the purposes of Testing, issue a Dispatch
Instruction;
(b) induce controlled Power System Frequency or Voltage conditions or variations
for the purpose of determining that the Generating Unit’s response is in
accordance with its Declared Availability, Ancillary Service capabilities and
Operating Characteristics; and
(c) having given three Business Days’ notice, or less where agreed, (identifying the
Ancillary Service and/or Operating Characteristic to be tested), send a
representative to the Generator's Site to verify by Testing in accordance with
the Test procedures specified in OC.10.5.8, that the Generator is in compliance
with its Declared values;
(d) request Start-Up on Secondary Fuel, or on-line changeover at Primary Fuel
Switchover Output from Primary Fuel to Secondary Fuel or from Secondary
Fuel to Primary Fuel at Secondary Fuel Switchover Output; and
(e) having given the Generator two Business Days’ notice send a representative to
the Generator’s Site to verify the Secondary Fuel stock levels both at the
onsite Secondary Fuel storage location and if required at the Off-Site Storage
Location.
OC 11.4.2. The System operator may issue an instruction requiring the User to test
any one or more of the User's Generators to demonstrate its performance
OC-11
subject to the notification giving the User not less than 48 hours’ notice lo
conduct the test if any of the following apply:
 If the Generator, Interconnector, Generator Aggregator, Demand Side Unit,
is unable to operate within the given parameters stated in its Power
Purchase Agreement (PPA) and/or Power Station Operation & Dispatch
Agreement (PSODA), as applicable and GSDP Notice such as Input/output
performance;
 Meet the requirements to operate in the Frequency Sensitive Mode; and
 Meet the reactive power or fast start capability as registered with the
System Operator under Scheduling and Dispatch Code and Operating Code
and relevant Addenda.
OC 11.4.3. The System Operator instruction detailed in OC 11.3.1 can only be issued if
the User has submitted import and export limits for the relevant Generator,
Interconnector, Generator Aggregator, Demand Side Unit, for the
operational day current at the lime the System Operator notification is
issued. The User is then obliged to submit to the System Operator import
and export limits with a magnitude greater than zero for that Generator,
Interconnector, Generator Aggregator, Demand Side Unit, for the time and
duration for the requested test.
OC 11.4.4. Testing may involve attendance by the SO or the SO representative at User
Sites in order to carry out Tests in accordance with the testing procedures
set out in OC.11.5.7.
OC 11.4.5. For the purposes of this OC11 a Test shall be carried out pursuant to a
Dispatch Instruction from the SO or by such alternative procedure as is
required or permitted by this OC11. The test shall be initiated by the issue
of instructions under Scheduled for the Generators, Interconnectors,
Demand Side Unit Operators and Generator Aggregators submitted by the
User for the day of the test.
OC 11.4.6. A Test may require the User to carry out specific actions in response to a
Dispatch Instruction.
OC 11.4.7. The results of a Test may be derived from the Monitoring of performance
during the Test.
OC 11.4.8. The results of the performance of the User's Generators,
Interconnectors, Demand Side Unit Operators and Generator
Aggregators under test shall be recorded at NPCC Control Centre using
voltage and current signals provided to the System Operator by the User.
OC 11.4.9. If the results are recorded on Site chart recorders are to be used and
representatives appointed and authorised by the System Operator shall
witness the test.
OC 11.4.10. Black Start Testing

OC 11.4.10.1. The SO may require a Generator with a Black Start Station to carry
out a test (a "Black Start Test") on a CDGU in a Black Start
Station either while the Black Start Station remains connected to
an external alternating current electrical supply (a "Black Start Unit
Test") or while the Black Start Station is disconnected from all
external alternating current electrical supplies (a "Black Start
Station Test"), in order to demonstrate that a Black Start Station
has a Black Start Capability.
OC 11.4.10.2. Where the SO requires a Generator with a Black Start Station to
carry out a Black Start Unit Test, the SO shall not require the Black
Start Test to be carried out on more than one CDGU at that Black
Start Station at the same time, and would not, in the absence of
exceptional circumstances, expect any other CDGU at the Black
Start Station to be directly affected by the Black Start Unit Test.
OC-11
OC 11.4.10.3. The SO may require a Generator or Interconnector Operator with a
Black Start Station to carry out a Black Start Unit Test at any time
(but will not require a Black Start Unit Test to be carried out more
than once in each calendar year in respect of any particular CDGU
or Interconnector unless it can justify on reasonable grounds the
necessity for further tests or unless the further test is a re-test, and
will not require a Black Start Station Test to be carried out more
than once in every two calendar years in respect of any particular
CDGU unless it can justify on reasonable grounds the necessity for
further tests or unless the further test is a re-test).
OC 11.4.10.4. When the SO wishes a Generator or Interconnector Operator with a
Black Start Station to carry out a Black Start Test, it shall notify the
relevant Generator or Interconnector Operator at least 7 Business
Days prior to the time of the Black Start Test with details of the
proposed Black Start Test.
OC 11.4.10.5. All Black Start Tests shall be carried out at the time specified by
the SO in the notice given under OC.10.5.7.4 and shall be
undertaken in the presence of a reasonable number of
representatives appointed and authorised by the SO, who shall be
given access to all information relevant to the Black Start Test.
OC 11.4.11. Test Procedures

The proposed procedure for a Test will be notified to the User by the SO in advance of the
Test. For an existing procedure, three Business Days notice shall be given.
For a new procedure, seven days notice shall be given and following receipt of such
notification the User, acting in good faith, may, by five days notice to the SO, reasonably
object to the proposed procedure on the grounds that there will be a material risk to the
safety of the User's Plant or personnel, or that the proposed procedure is technically infeasible
or inappropriate to the purpose (in accordance with Good Industry Practice), giving full details
of its concerns. In the event that the User so objects, the SO shall, as it considers necessary,
modify the procedure and re-notify the User.
The SO shall treat information collected from Users during monitoring and testing as
confidential.
OC 11.4.12. Results of Testing shall be dealt with in accordance with
OC 11.5 INVESTIGATION
OC 11.5.1. At its discretion, OC.11.6.1 The SO may, if it reasonably that there may be
an issue of non- compliance by the User, considers carrying out an
Investigation to acquire or verify information relevant to Users' Plant and/or
Apparatus design, operation or connection requirements under the Grid
Code, Connection Agreements, Ancillary Service Agreements and System
Support Agreements between Users and the SO.
OC 11.5.2. Investigation by the SO usually applies to information not collected on a
regular basis by means of Monitoring and Testing. The SO may, having
given reasonable notice, send a representative or subcontractor to a User’s
Site in order to Investigate any equipment or operational procedure on or
applicable to the User Site insofar as the condition of that equipment or
operational procedure is relevant to compliance with the Grid Code,
Connection Agreements, and/or other agreements between Users and the
SO.
OC 11.6 CONSEQUENCES OF MONITORING, TESTING AND INVESTIGATION
OC-11
OC 11.6.1. Non-compliance with a Dispatch Instruction issued by the SO to a
Generator, Interconnector Operator, Demand Side Unit Operator or
Generator Aggregator.
OC 11.6.1.1. When the SO considers that a Generator, Interconnector Operator,

a Demand Side Unit Operator or a Generator Aggregator is not in
compliance with a Dispatch Instruction then the SO shall inform the
Generator, the Interconnector Operator, the Demand Side Unit
Operator or the Generator Aggregator by agreed methods,
identifying the relevant Generation Unit, Interconnector or Demand
Side Unit, and identifying the Dispatch Instruction and the time of
issue of the Dispatch Instruction with which the SO considers the
Generator, the Interconnector Operator, the Demand Side Unit
Operator or the Generator Aggregator is not in compliance. This
shall be known as a "Warning for non-compliance with a Dispatch
Instruction". The Warning is to contain a Dispatch Instruction which
may be identical to the original Dispatch Instruction or which may
differ from it. The occurrence of the Warning shall be logged by the
SO and by the Generator, the Interconnector Operator, the
Demand Side Unit Operator or the Generator Aggregator.
OC 11.6.1.2. OOn receipt of a Warning for non-compliance with a Dispatch

Instruction, the Generator, the Interconnector Operator, the
Demand Side Unit Operator or the Generator Aggregator must as
soon as possible, and in any case within ten (10) minutes of the
receipt of the Warning:
(a) Commence to comply with the Dispatch Instruction included with the
Warning (this may be the original or a modified Dispatch Instruction
as outlined in OC.11.6.1.1); or
(b) Reply to the SO, disputing in good faith the validity of the original
Dispatch Instruction, detailing the grounds on which the validity is
being disputed; or
(c) Reply to the SO, disputing in good faith the validity of the assessment
of non-compliance. In this event the Generator, the Interconnector
Operator, the Demand Side Unit Operator or the Generator
Aggregator must as soon as is reasonably practicable, inform the SO
in detail of the grounds on which the assessment of non-compliance
is being disputed; or
(d) Reply to the SO, giving a reason for inability to comply with the
Dispatch Instruction, and making a revised Declaration in respect of
the Availability, Ancillary Service capabilities or Operating
Characteristics, as appropriate.
OC 11.6.1.3. If the Generator, Interconnector Operator, Demand Side Unit

Operator or Generator Aggregator complies in accordance with
OC.11.6.1.2 (a), no further action shall arise.
OC 11.6.1.4. In the event of the Generator, Interconnector Operator, Demand

Side Unit Operator or Generator Aggregator making a revised
Declaration under OC.11.6.1.2 (d), the SO shall then issue a new
Dispatch Instruction, consistent with the revised Declaration. The
revised Declaration will be backdated to the time of issue of the
relevant Dispatch Instruction. Notwithstanding the backdating of
the revised Declaration, the Generator, Interconnector Operator,
Demand Side Unit Operator or Generator Aggregator will still be
deemed under OC.11.6.1.1 as having failed to comply with a
OC-11
OC 11.6.1.5. In the event of OC.11.6.1.2 (b) or OC.11.6.1.2 (c) applying, the SO
shall consider the substance of the Generator's, Interconnector
Operator’s, Demand Side Unit Operator’s or Generator Aggregator’s
disputation. The SO shall, where the SO considers appropriate,
communicate with the Generator, Interconnector Operator,
Demand Side Unit Operator or Generator Aggregator to clarify
aspects relating to the issue and receiving of the Dispatch
Instruction, and the Generator's, Interconnector Operator’s,
Demand Side Unit Operator’s or Generator Aggregator’s actions.
The SO shall acting reasonably determine the validity of the
Generator’s, Interconnector Operator’s, Demand Side Unit
Operator’s or Generator Aggregator’s disputation, and shall inform
the Generator, Interconnector Operator’s, Demand Side Unit
Operator or Generator Aggregator as to its decision. The SO shall
record both its decision, and also all pertinent information relating
to the event, including the Generator's, Interconnector Operator’s,
Demand Side Unit Operator’s or Generator Aggregator’s
disputation and such information shall be deemed to be
Operational Data.
OC 11.6.1.6. Where the SO, acting reasonably, is of the view that a disputation
given by a Generator, Interconnector Operator, Demand Side Unit
Operator or Generator Aggregator is not valid or not wholly valid or
if the Generator, Interconnector Operator, Demand Side Unit
Operator or Generator Aggregator has not replied in accordance
with OC.11.6.1.2, the SO shall inform the Generator, Interconnector
Operator, Demand Side Unit Operator or Generator Aggregator that
it is overriding, by means of a Post Event Notice, the Generator's
Declaration or Interconnector’s Declaration in respect of the
Availability, Ancillary Service capabilities or Operating
Characteristics of the Generation Unit or Interconnector as
appropriate. The Post Event Notice shall govern until such times as
the Generator, Interconnector Operator, Demand Side Unit
Operator or Generator Aggregator submits a revised Availability
Notice.
OC 11.6.1.7. Where the SO gives a Post Event Notice under OC.11.6.1.6, the
Post Event Notice shall be backdated to the time of issue of the
relevant Dispatch Instruction, or the latest time for which there
exists compelling evidence that the Generation Unit,
Interconnector and Demand Side Unit was acting in compliance
with the Dispatch Instruction, whichever is the later. The Post
Event Notice shall set the level of Declared Availability, Declared
Ancillary Service capability or declared Technical Parameter, as the
case may be, at such level as the Monitoring, Testing or
Investigation indicates the Generation Unit or Interconnector
actually achieved.
OC 11.6.1.8. Notwithstanding the backdating of the Post Event Notice, the User
will still be deemed under OC.10.6.1.1 as having failed to comply
with a Dispatch Instruction.
OC 11.6.1.9. In the event that the Demand Side Unit Operator is deemed by the
SO in accordance with the provisions of this OC.11 to be in non-
compliance with its Dispatch Instructions, that is the Demand Side
OC-11
Unit failed to comply with three (3) Dispatch Instructions in a one
calendar month period then the SO shall notify the Demand Side
Unit Operator of the continued non-compliance. The Demand Side
Unit Operator shall take immediate action to remedy such non-
compliance. The terms of this OC.10.6.1.8 shall be without
prejudice to the rights of the SO to instruct the Market Operator
that the Demand Side Unit is in breach of the Grid Code. In such
cases the SO may set the Demand Side Unit’s Availability to zero or
to a level as deemed appropriate by the SO until Testing is
completed on compliance with Dispatch Instructions.
OC 11.6.2. Non-compliance by a Generator and Interconnector Operator with Declared

Operating Reserve
OC 11.6.2.1. In evaluating the adequacy of the performance of a Generation

Unit or Interconnector as the case may be, the SO shall compare
the actual performance as measured, with the expected
performance for that Generation Unit or Interconnector. The
expected performance from the Generation Unit or Interconnector
shall be calculated based on the Frequency deviation from the Pre-
Incident Frequency, and the Generation Unit's or Interconnector’s
then Declared values of Availability, POR, SOR, TOR1, TOR2 and
Governor Droop;
OC 11.6.2.2. Where the performance of a Generation Unit or Interconnector is

deemed by the SO to be in non-compliance with Declared
Operating Reserve, then the SO shall notify the Generator or
Interconnector Operator, of the non-compliance, identifying the
system or procedure by which non-compliance was measured. The
SO shall by means of a Post Event Notice override the Generator's
or Interconnector Operator’s Declaration in respect of Operating
Reserve. The revised Declaration shall be effective from the time of
commencement of the Test or Event on which the non-compliance
has been assessed, or such later time as may, in the opinion of the
SO acting reasonably, be appropriate if the non-compliance did not
apply to the full period of the Test or Event.
OC 11.6.2.3. Following the notification of non-compliance, the SO shall make

available to the Generator or Interconnector Operator within three
Business Days relevant data in relation to the system Frequency
and Generation Unit or Interconnector performance, that the
Generator or Interconnector may reasonably require substantiating
the assessment of non-compliance
OC 11.6.2.4. The consequences of non-compliance by a Generator or
Interconnector with Declared Operating Reserve will be addressed
in the Trading and Settlement Code and other agreements as
appropriate.
OC 11.6.3. Non-compliance by a Generator, Interconnector Operator, Demand Side

Unit Operator or Generator Aggregator with an Availability Notice
OC 11.6.3.1. In the event that the performance of a Generation Unit,

Interconnector, Demand Side Unit or Aggregated Generator is
deemed by the SO to be in non-compliance with its Declared
Availability, then the SO shall notify the Generator, Interconnector
OC-11
Operator, Demand Side Unit Operator or the Generator Aggregator
of the non-compliance.
OC 11.6.3.2. Having so informed the Generator, Interconnector Operator,

Demand Side Unit Operator or Generator Aggregator, the SO shall,
by means of a Post Event Notice, override the User's Availability
Notice, with a value as appropriate to the outcome of the Test or
Investigation. The revised Declaration shall be effective from the
time of commencement of the Test or Investigation on which the
non-compliance has been assessed, or such later time as may, in
the opinion of the SO acting reasonably, be appropriate if the non-
compliance did not apply to the full period of the Test or
Investigation.
OC 11.6.3.3. The economic consequence of non-compliance by a Generator,

Interconnector Operator, Demand Side Unit Operator or Generator
Aggregator with Declared Availability will be addressed in the SEM
Trading and Settlement Code and other agreements as
appropriate.
OC 11.6.4. Non-compliance by a Generator, Demand Side Unit Operator or

Interconnector Operator with Declared Ancillary Services or Declared
Technical Parameters
OC 11.6.4.1. In the event that the performance of a Generation Unit, Demand

Side Unit Operator or Interconnector is deemed by the SO to be in
non-compliance with its Declared Ancillary Services capability or
Operating Characteristics, then the SO shall notify the Generator,
Demand Side Unit Operator or Interconnector Operator of the non-
compliance, and having so informed the Generator, Demand Side
Unit Operator or Interconnector Operator then the SO shall by
means of a Post Event Notice override the Generator's Declaration,
Demand Side Unit Operator’s Declaration or Interconnector
Operator’s Declaration in respect of Ancillary Services or Operating
Characteristics as appropriate.
OC 11.6.4.2. The consequences of non-compliance by a Generator, Demand

Side Unit Operator or Interconnector Operator with Declared
Ancillary Services or Declared Technical Parameters will be
addressed in the SEM Trading and Settlement Code and other
agreements as appropriate.
OC 11.6.5. Non-compliance by a User with a Connection Condition or Registered

Operating Characteristics
OC 11.6.5.1. In the event that the performance of a Generation Unit is deemed

by the SO in accordance with the provisions of this OC.11 to be in
non compliance with its Operating Characteristics or with a
Connection Condition, then the SO shall notify the Generator of the
non-compliance and the Generator shall take immediate action to
remedy such non compliance. The terms of this OC.11.6.5 shall be
without prejudice to the rights of the SO to De-energise the
Generator's Plant and Apparatus in accordance with the terms of
OC.XXX.
OC 11.6.5.2. In the event that the performance of an Interconnector is deemed

by the SO in accordance with the provisions of this OC.11 to be in
OC-11
non-compliance with its Operating Characteristics, or with a
Connection Condition, then the SO shall notify the Interconnector
Operator of the non-compliance and the Interconnector Operator
shall take immediate action to remedy such non compliance. The
terms of this OC.11.6.5 shall be without prejudice to the rights of
the SO to De-energise the Interconnector and Apparatus in
accordance with the terms of OC.XX.
OC 11.6.5.3. In the event that the performance of a Demand Side Unit is

deemed by the SO in accordance with the provisions of this OC.11
to be in non-compliance with its Operating Characteristics or with a
Connection Condition, then the SO shall notify the Demand Side
Unit Operator of the non-compliance and the Demand Side Unit
Operator shall take immediate action to remedy such non
compliance. The terms of this OC.11.6.5 shall be without prejudice
to the rights of the SO to De-energise the Demand Site and
Apparatus in accordance with the terms of OCXXX.
OC 11.6.6. Failure of a Black Start Test
OC 11.6.6.1. A Black Start Station shall fail a Black Start Test if the Black Start
Test shows that it does not have a Black Start Capability (i.e. if the
relevant Generating Unit fails to be Synchronised to the System
within two hours of the Auxiliary Gas Turbine(s) or Auxiliary Diesel
Engine(s) being required to start).
OC 11.6.6.2. If a Black Start Station fails to pass a Black Start Test the
Generator or Interconnector Operator must provide the SO with a
written report specifying in reasonable detail the reasons for any
failure of the test so far as they are then known to the Generator or
Interconnector Operator after due and careful enquiry. This must
be provided within five Business Days of the test. If a dispute arises
relating to the failure, the SO and the relevant Generator or
Interconnector Operator shall seek to resolve the dispute by
discussion, and if they fail to reach agreement, the Generator or
Interconnector Operator may require the SO to carry out a further
Black Start Test on 48 hours notice which shall be carried out
following the agreed procedure as the case may be, as if the SO
had issued an instruction at the time of notice from the Generator
or Interconnector Operator.
OC 11.6.6.3. If the Black Start Station concerned fails to pass the re-test and a
dispute arises on that re-test, either party may use the Disputes
Resolution Procedure for a ruling in relation to the dispute, which
ruling shall be binding.
OC 11.6.6.4. If following the procedure in OC.11.6.6.2 and OC11.6.6.3 it is

accepted that the Black Start Station has failed the Black Start Test
(or a re-test carried out under OC.11.6.6.2), within 14 days, or such
longer period as the SO may reasonably agree, following such
failure, the relevant Generator or Interconnector Operator shall
submit to the SO in writing for approval, the date and time by
which that Generator or Interconnector Operator shall have
brought that Black Start Station to a condition where it has a Black
Start Capability and would pass the Black Start Test, and the SO
will not unreasonably withhold or delay its approval of the
Generator's or Interconnector Operator’s proposed date and time
OC-11
submitted. Should the SO not approve the Generator's or
Interconnector Operator’s proposed date and time (or any revised
proposal) the Generator or Interconnector Operator shall revise
such proposal having regard to any comments the SO may have
made and resubmit it for approval.
OC 11.6.6.5. Once the Generator or Interconnector Operator has indicated to

the SO that the Generating Station or Interconnector has a Black
Start Capability, the SO shall either accept this information or
require the Generator or Interconnector Operator to demonstrate
that the relevant Black Start Station has its Black Start Capability
restored, by means of a repetition of the Black Start Test referred
to in OC.11.6.7.4following the same procedure as for the initial
Black Start Test. The provisions of this OC.11.6.7 will apply to such
test.
OC 11.6.7. In the event that the Generators, Interconnectors, Demand Side Unit
Operators and Generator Aggregators fails to meet the test criteria specified
in the table given below, the User is required to provide the System
Operator with a written explanation of the reasons for failure. If the System
Operator and the User are unable to agree, the System Operator may
require the User to perform a re-test.
OC 11.6.8. If in the opinion of the System Operator the Generators, Interconnectors,

Demand Side Unit Operators and Generator Aggregators again fails the re-
test, every effort should be made to resolve the matter. In the event that a
dispute arises between the User and the System Operator, either Entity
may approach the Review Panel for a determination of the dispute which
shall be binding on both Entities.
OC 11.7 DISPUTATION OF ASSESSMENT OF NON-COMPLIANCE BY A USER
OC 11.7.1. In the event that a User has received notification from the SO of an
assessment of non-compliance and/or application of a Post Event Notice
under OCXXX then the User may reply to the SO disputing in good faith the
validity of either the assessment of non-compliance and/or the content of
the Post Event Notice, detailing the grounds on which the validity is being
disputed. Any disputation should be submitted within 12 hours although
additional information in support of the disputation may follow within two
Business Days.
OC 11.7.2. If a User submits a disputation to the SO under OC.11.7.1, then the SO shall
consider the substance of the User's disputation. The SO may, where the
SO considers appropriate, communicate with the User to clarify aspects of
the assessment of non-compliance or the User's disputation.
OC 11.7.3. The SO shall determine the validity of the User's disputation, and shall
inform the User within five Business Days as to its decision. The SO shall
alter or revise any assessment of non-compliance and/or Post Event Notices
as appropriate.
OC 11.7.4. In the event that there is still disagreement as to the outcome, the dispute
shall if requested by either the SO or the User, be referred to NEPRA .
OC-11
OC 11.8 DISPUTE RESOLUTION PROCEDURE
OC 11.8.1. If after the procedure described in OC 11.7 it is accepted that a Generators,

Interconnectors, Demand Side Unit Operators and Generator Aggregators has
failed the test or re-test, this Code Participant or the User shall within 10
working days submit to the System Operator a date with a proposal by
which the Generator shall be able to comply with the relevant requirements
and its obligations under its Purchase Agreement (PPA) and/or Power
Station Operation & Dispatch Agreement (PSODA) as applicable, and the
Grid Code. The System Operator should not withhold approval or
unreasonably delay in the approval of the proposal. If the System Operator
does not approve the date and time submitted by the User, the User shall
amend such proposal having regard to any comments given by the System
Operator and re-submit it for the System Operator's approval.
OC 11.8.2. If the Generator fails the test, the User shall submit revised limits and other
data as may be relevant in the case of a Generator as per Revised GSDP
Notice for the period of time until the Generator can achieve the
Parameters previously registered or demonstrated under SDC 1 (GSDPs).
OC 11.8.3. When the User advises the System Operator that the Generator is able to
achieve the previously Generation Scheduling and Dispatch Parameters
(GSDPs): the System Operator shall either accept this information or
require the User to re-test the Generator to confirm the stated capability.
The System Operator shall give 48 hours Notice to the User for a re-test.
The test shall be conducted in accordance with OC 11.3, and the provisions
of OC 11.4 shall apply to this further test.
OC-11
OC-11
The Generator will Pass the Test if the Following Criteria Below is Met
Parameter to Grid Code Pass Criteria

be tested Reference
Reactive CC Generating Unit will pass the test if it is within ±5% of the capability registered of the syste
Capability operator under OC 4.
The duration of the test will be 60 minutes with System voltage at the Transmission Connection
Point being maintained by the Generator by adjustment of Reactive Power on the remaining
Reactive
capability
Generating Units, if necessary.
Primary, ASA The measured response in MW/Hz is within ±5% of the level of response specified in the
Secondary and Ancillary Services Agreement for that Genset.
High
Frequency
Governor CC Measurements indicate that the Governor parameters are within the criteria set out in the
Compliance appropriate governor standard.
Limited High SDC 3 The measured response is within the requirements of SDC 3.
Frequency
Response
Governor System
Output CC For variations in System Frequency exceeding 0.1 Hz within a period of less than 10 Seconds,
Reduced SDC the Active Power output is within ±0.2% of the requirements of CC xxx when monitored at
System prevailing external air temperatures of up to 25°C.
Frequency
Fast Test ASA The Fast Start Capability requirements of the Ancillary Services Agreement for that Genset are
met.
Black Start OC 12.5.1 The relevant Generating Unit is Synchronised to the System within two hours of the Auxiliary
Supplies being required to start.
The Generator will Pass the Test if the Following Criteria Below is Met
OC-11
Parameter to Grid Code Pass Criteria
be tested Reference
Export and OC 12 The Export and Import, OPN, Joint BM Unit Data and Dynamic Parameters Under test are within 2½
Import Limits, % of the declared value being tested.
QPN, Joint
Generator data
and Dynamic
Parameters
Synchronisatio SDC Synchronisation takes place within minutes of the time it should have achieved Synchronisation.
n time
Run-up Rates OC 12 Achieves the instructed output and, where applicable, the first and or/second intermediate
breakpoints, each within ±3 minutes of the time it should have reached such output and
breakpoints from Synchronisation calculated from the run-up rates in its Dynamic Parameters.
Run-down OC 12 Achieves the instructed output within ±5 minutes of the time, calculated from the run-down rates in
Rates its Dynamic Parameters.
Dynamic Parameters
Output CC For variations in System Frequency exceeding 0.1 Hz within a period of less than 10 Seconds, the
Reduced SDC Active Power output is within ±0.2% of the requirements of CC xxx when monitored at prevailing
System external air temperatures of up to 25°C.
Frequency
The following conditions will apply to each of the above tests:
The duration of the test will be consistent with and sufficient to measure the relevant expected input or output derived from the Final
Physical Notification Date.
OC 11.9 BLACK START (BS) TESTING
OC 11.9.1. General Requirements
OC 11.9.1.1. The System Operator may request a Generator, HVDC System

or Converter connected generation with a Black Start Station to
perform a Black Start (BS) Test with the Black Start Station
remaining connected to an alternating current supply or whilst
disconnected from all external alternating current supplies, in
order to demonstrate that the Black Start Station has Black Start
Capability.
OC 11.9.1.2. If the System Operator requires a Generator, HVDC System or
Converter connected generation with a Black Start Station to
undertake a BS Unit Test, the System Operator shall not require
the test to be conducted on more than one Generating Unit at the
same time, and would not normally expect any other Generating
Unit at the Black Start Station to be directly affected by the Black
Start Unit Test.
OC 11.9.1.3. Normally any Generator, HVDC System or Converter
connected generation shall not be tested more than once in any
year and a Black Start Station test shall not be requested by the
System Operator more frequently than once every two years.
OC 11.9.1.4. When the System Operator requests a Generator, HVDC System
or Converter connected generation to perform a Black Start Test,
a minimum notice of seven days shall be given to the Generator.
OC 11.9.2. Procedure for a Black Start (BS) Test
OC 11.9.2.1. BS Unit Test

(a) The relevant Generator shall be synchronised and loaded
(b) All auxiliary supply sources in the Black Start plant where the
Generator is located shall be shut down.
(c) The Generator shall be de-Loaded and de-synchronised, and
all alternating current supplies to its auxiliaries shall be
disconnected.
(d) The auxiliary supplies in (b) shall be re-started and energise
the unit board of the relevant Generator, thereby enabling
the Generator to return to synchronous speed.
(e) The relevant Generator shall be synchronised to the system
but not loaded unless instructed to do so by the System
Operator.
OC 11.9.2.2. BS Station Test

(a) All Generators at the Black Start Station other than the
Generator on which the Black Start Test is to be undertaken,
and all auxiliary supplies to the Back Start Station shall be
shutdown.
(b) The relevant Generator shall be synchronised and loaded
(c) The relevant Generator shall be de-Loaded and de-
synchronised.
(d) All external alternating current electrical supplies to the
generator board of the relevant Generator, and to the station
board of the relevant Black Start station shall be
disconnected.
(e) The auxiliary supply generator at the Black Start Station shall
be started and shall re-energise either directly or via the
station board, the unit board of the relevant Generator.
OC-11
(f) The relevant Generator shall be synchronised to the System
but not loaded unless instructed to do so by the System
Operator.
OC 11.9.2.3. Black Start HVDC systems

(a) The HVDC link shall be de-Loaded.
(b) All external alternating current electrical supplies to HVDC
Converter stations shall be disconnected.
(c) The HVDC Converter station at the rectifying end is started
and energizing the DC transmission line
(d) The auxiliary supply generator at the inverter Black Start
HVDC Converter station shall be started at the delivering and
shall re-energise HVDC control system.
(e) The inverter end of the HVDC link is started and energizing a
dead AC busbar.
OC 11.9.3. Failure of a Black Start Test
OC 11.9.3.1. A failure shall be recorded if the Black Start plant fails to

demonstrate it has a Black Start Capability
OC 11.9.3.2. In the event of such failure, the Generator must provide the
System Operator with a written report detailing the reasons for the
failure within ten working days of the failed Black Start Test. If a
dispute arises between the System Operator and the Generator,
they shall seek to resolve their differences. In the event that there
is no resolution, the Generator may require the System Operator to
permit a further Black Start Test on 48 hours’ notice. The relevant
test procedures, as set out in OC 11.9.3.1 and OC 11.9.3.2 shall
apply to the re-test.
OC 11.9.3.3. If the Black Start plant fails the re-test and a dispute arises
between the Generator/HVDC Interconnector and the System
Operator, either Code Participant may use the disputes resolution
procedure as provided through the Review Panel. The findings of
the dispute resolution procedure shall be binding on both Code
Participants.
OC 11.9.3.4. If, a Black Start station fails the Black Start Test and subsequent
retest, the Generator shall, within fourteen working days, advise
the System Operator in writing of the date and time by which the
Generator/HVDC Interconnector shall restore the Black Start
Capability to that Black Start station. The System Operator shall
not unreasonably withhold approval to the Generator's proposal.
Should the System operator not approve the Generator's proposal,
the Generator shall re-submit the proposals by taking into account
the System Operator's comments.
OC 12.5.7 When the Generator/HVDC Interconnector advises the System Operator that
the Black Start station has been restored to Black Start Capability status, the System Operator
shall either accept this information or require a further Black Start Test to demonstrate the
validity of the Generator's information. Any further test shall be in accordance with test
procedures detailed in OC 11.9.3.1 and OC 11.9.3.2.
OC 11 Appendix 1
SYSTEM WARNINGS (TO BE IMPLEMENTED THROUGH FAX OR ANY OTHER

ELECTRONIC MEDIA)
WARNING TO: FOR ACTION CONSEQUENCE RESPONSE FROM

TYPE RECIPIENTS/
CODE PARTICIPANTS
OC-11
Inadequate Generators • Less Generation as • Increase of
(Centrally compared to Generation by
Dispatched) Demand of the the Generators.
Interconnectors system and
Operating Margin. • To initiate additional
Demand Management
• Instruction for if conditions are not
reducing the Demand improved.
DISCOs
Transmission
Connected
Consumer,
Externally-
connected
Consumers
High risk of Generators, ----do--- ----do---
Demand Interconnectors
Reduction DISCOs,
Transmission ----do--- ----do---
Connected
Consumers
Externally-
connected
Consumers.
Demand DISC0s, Possibility of reduction in ----do---
Control Transmission Demand within a
Imminent Connected specified time as per
Consumers instructions of the ----do---
Externally- system operator
connected
Consumers.
Risk of System Generators, Risk of possible Operational staff to be
Disturbance Interconnectors disturbance on whole or made alert to be able to
DISCOs. partially of the National withstand the
Transmission power system. disturbance.
Connected
Consumers,
Externally-
connected
Consumers.
End of OC 11
OC-11
System Recovery
CONTENTS
OC 12.2 OBJECTIVE.................................................................................................... 258
OC 12.3 SCOPE.......................................................................................................... 259
OC 12.4 SYSTEM ALERTS........................................................................................... 259
OC 12.5 TOTAL AND/OR PARTIAL SHUTDOWN OF SUPPLIES......................................... 260
OC 12.6 ISLANDED NETWORK.................................................................................... 263
OC 12.7 INCIDENTS................................................................................................... 263
OC-13 258
SYSTEM RECOVERY

OC 12.1.1. Normal operation of the Transmission System by the SO is in accordance
with the principles and procedures as set out in this Grid Code and
obligations under the Electricity Supply Act. There will be emergency
situations when security of the Transmission System is subject to abnormal
levels of risk (e.g. during major lightning storms) and this OC.9 provides for
specific requirements to address such situations.
OC 12.1.2. Experience has shown that electricity supply systems can suffer Partial
Shutdown or Total Shutdown. Collapses can result from a number of root
causes but might most typically be due to a high number of Plant failures
(Generation and/or transmission) resulting from severe weather conditions
and/or maloperation of protection systems.
OC 12.1.3. It is therefore necessary in the Grid Code to provide for how to deal with a
Partial Shutdown or Total Shutdown of the Transmission System, and to
ensure that the necessary procedures and facilities are in place to support
rapid re-establishment of the shutdown parts and restore supply to
Customers.
OC 12.1.4. A Partial Shutdown or Total Shutdown represents one of the most serious
fault situations liable to occur on the Transmission System, having a major
effect on both Users and Customers. Due to the significance of such an
incident and the urgency in restoring supply to all Customers, it is
imperative that all Users should maintain a high level of awareness and
training in respect of Power System Restoration.
OC 12.1.5. This sub-code deals with the procedures for the restoration of power
supplies following a Total Shutdown or a Partial Shutdown of the System
and the re-synchronisation of specific parts of the System that have been
Islanded.
OC 12.1.6. This sub-code requires that effective channels of communications must be

established between senior management of the System Operator and the
System Operator and the Generators, Distribution Companies,
Transmission-connected Consumers, Externally-connected Consumers,
which are additional to those used for day-to-day system opera lions.
OC 12.1.7. In order to mitigate the effects of any national emergency, the Federal
Government may require the System Operator, Operators of power plants
and distribution companies to take action to safeguard electric power
supplies. Such action may be contrary to the principles and procedures laid
down in the Grid Code, and as such, the appropriate section of the Grid
Code shall stand suspended.
OC 12.2 OBJECTIVE
OC 12.2.1. The objective of OC.9 is to ensure that in the event of a Partial Shutdown
or Total Shutdown of the Transmission System, normal supply is restored
to all Customers as quickly and as safely as practicable in accordance with
Prudent Utility Practice. This objective can be subdivided:
OC-13 259
 To outline the general restoration strategy which will be adopted by the SO in
the event of a Partial Shutdown or Total Shutdown of the Transmission
System;
 To establish the responsibility of the SO to produce and maintain a
comprehensive Power System Restoration Plan, covering both Partial
Shutdowns and Total Shutdowns;
 To establish the responsibility of Users to co-operate with the formation and
execution of the Power System Restoration Plan,
 To ensure that the SO and User personnel who will potentially be involved
with the Power System Restoration Plan, should be adequately trained
and fully familiar with the relevant details of the plan.
OC 12.3 SCOPE
(a) Generators which for the purposes of OC.12 includes all
Generators with
Registered Capacity greater than 5 MW;
(b) Interconnector Operators;
(c) Distribution System Operators;
(d) Provincial and SPTL Companies
(e) Demand Customers; and
(f) Demand Side Unit Operators
(g) Generator Aggregators.
OC 12.3.1. Contingency arrangements are required to be established by the System

Operator with each connected Party/Consumers.
OC 12.4 SYSTEM ALERTS

OC 12.4.1. In the event of a System Emergency Condition or imminent shortfall of MW
capacity, the SO may issue any of several Alerts to the Generator, key
Transmission Stations, Distribution Control Centres and Demand Side Unit
Operators. These Alerts may include an Colour1 Alert, Colour2 Alert or
Colour3 Alert, or other Alerts as may be agreed from time to time.
OC 12.4.2. Alerts will normally (except in the case of a failure of the Electronic Alert
System when it will be given verbally) be transmitted to the User via the
Electronic Alert System. The Alert shall cause an alarm in the receiving
location, which must be acknowledged by the User in accordance with their
Alert procedures.
OC 12.4.3. Amber Alerts
OC 12.4.3.1. An Amber Alert may be issued when a single Event would give rise
to a reasonable possibility of failure to meet the Power System
Demand, or of Frequency or Voltage departing significantly from
normal, as per CC.8.2.1(a) and CC.8.3.1(a), or if multiple Events
are probable due to prevailing weather conditions.
OC-13 260
OC 12.4.3.2. Standing procedures to be activated in response to an Amber Alert
will be developed by the SO, in consultation with Users, and
notified to each User as appropriate. These standing procedures
will not impose obligations on the User which are not already
implicit in the Grid Code.
OC 12.4.3.3. Each User is responsible for internal procedures necessary to
execute the standing procedures.
OC 12.4.4. Red Alerts
OC 12.4.4.1. OA Red Alert may be issued when, other than as provided for in
OC.10, the Frequency or Voltage has deviated significantly from
normal, or User's Demand has been disconnected, or, in the period
immediately ahead there is a high probability of failing to meet the
Power System Demand or to maintain normal Voltage.
OC 12.4.4.2. Standing procedures to be activated in response to a Red Alert will
be developed by the SO, in consultation with Users, and notified to
each User as appropriate.
OC 12.4.4.3. Standing procedures to be activated in response to a Red Alert will
each User as appropriate.
OC 12.4.5. Blue Alert

OC 12.4.5.1. The issuing of a Blue Alert other than as provided for in OC.12.4.5,
by the SO signifies that either a Partial Shutdown or a Total
Shutdown of the Power System has taken place.
OC 12.4.5.2. Standing procedures to be activated in response to a Blue Alert will
each User as appropriate. These standing procedures will not
impose obligations on the User which are not already implicit in the
Grid Code.
OC 12.4.5.3. Each User is responsible for internal procedures necessary to
execute the standing procedures. In developing internal
procedures to apply following the activation of Blue Alert standing
procedures, each User shall consult with the SO.
OC 12.5 TOTAL AND/OR PARTIAL SHUTDOWN OF SUPPLIES

OC 12.5.1. A Total Shutdown of the System is a situation when there is no internal
generation online and operating; and there is no power supply available
from external-connections. The restoration of power supply from such a
situation is a Black Start Recovery. A Partial Shutdown is when a there is no
on-line operating generation or External Connection to a part of the system
that has become shutdown; and it is necessary for the System Operator to
instruct Black Start Recovery procedures to restore supplies to that part of
the system.
OC 12.5.2. The Power System Restoration Plan will be developed and maintained by
the SO in consultation with the DSO and other Users as appropriate. The SO
will promulgate the Power System Restoration Plan in accordance with
Prudent Utility Practice.
OC 12.5.3. The procedure for Power System Restoration shall be that notified by the
SO to the User at the time of a Partial Shutdown or Total Shutdown. Each
User shall abide by the SO's instructions during the restoration process,
subject to safety of personnel and the SO's and the User's Plant and
Apparatus.
OC-13 261
OC 12.5.4. It shall be the responsibility of the User to ensure that any of its personnel
who may reasonably be expected to be involved in Power System
Restoration are familiar with, and are adequately trained and experienced
in their standing instructions and other obligations so as to be able to
implement the procedures and comply with any procedures notified by the
SO under OC.12.5.2.
OC 12.5.5. The SO shall in consultation with each User and on at least one occasion
each year, issue a Colour3 Alert to the User for the purposes of assisting
training. The content of the tests shall be notified in advance to the User,
and a date and time for execution of the tests shall be agreed. The User
must, acting in accordance with Good Industry Practice, co-operate with
any such testing.
OC 12.5.6. During the restoration of power supplies following a Total Shutdown or

Partial Shut Down of the System, it may be necessary to operate the
system outside normal frequency and voltage limits as stated in OC XX. It
may also be necessary for the System Operator to issue instructions that
are contrary to the Balancing Mechanism or Code, and also to normal
contractual obligations in order to ensure restoration of supplies.
OC 12.5.7. Following a Total Shutdown of the System designated power plants that
have the ability to Start Up without any External Connection to the system
shall be instructed to commence Black Start recovery procedures. These
procedures, which are to be agreed in advance, may include the restoration
of blocks of local load demand that can be restored in agreement with the
local distribution company. Local procedures may include the restoration of
power supplies via Embedded Generators. The System Operator has the
responsibility for the re-energisation of the interconnected transmission
system, and the re-synchronisation of the system blocks of islanded blocks
of locally restored supplies.
OC 12.5.8. Where system configuration prevents a Generator restoring blocks of Load

Demand without the use of the interconnectable transmission system,
adjacent distribution companies shall reconfigure their system(s) to provide
discrete blocks of local load demand, which shall then be restored on the
instruction of the System Operator in liaison with Generator, using
segregated parts of the interconnected transmission system.
OC 12.5.9. The complexities and uncertainties relating to the restoration of power

supplies following a Total Shutdown or Partial Shutdown of the System
dictate that any internal System Operator procedure and any local
procedure agreed between the System Operator, Distribution, Provincial &
SPTL companies, transmission-connected Consumers, Interconnector,
Generator Aggregators and Generators allows for a flexible approach to be
adopted in the light of actual circumstance rather than rigid procedure
involving prescribed actions.
OC 12.5.10. During the restoration of Load Demand, the System Operator may issue
instructions that conflict with a local procedure for the restoration of power
supplies. In such an event the System Operator instruction shall override
any agreed local procedure.
OC-13 262
OC 12.5.11. Procedures for the restoration of power supplies may include the
requirement for the Operators of Generators to communicate directly with
the distribution companies so that the restoration of blocks of local power
supplies can be carried out in a controlled manor to ensure the Generator's
stability.
OC 12.5.12. Frequency sensitive automatic load disconnection schemes may be taken

out of service during the restoration of Load Demand to prevent unwanted
disconnection of load demand.
OC 12.5.13. The System Operator shall instruct the interconnection of islanded

networks to form progressively larger and resilient sub-systems until the
complete System has been interconnected.
OC 12.5.14. During the restoration of supplies, the System Operator shall agree the
reconnection of the System to any Externally-connected Party with the
operations of those systems, as allowed for under the relevant licences.
OC 12.5.15. Black start service is provided by generators, HVDC interconnector and

converter connected generation having the capability to Start-up from
complete system shut down, energize part of the system, and synchronize
to the system upon instruction from System Operator.
OC 12.5.16. A restoration plan shall be produced jointly by System Operator and the
relevant Grid Code Users. It shall include responsibilities on Grid Code
Users during system total or partial shutdown. When the restoration plan
has been prepared, it shall be sent to the grid code users for approval.
OC 12.5.17. The System Operator, the relevant Special Purpose Transmission Licensees
(SPTLs), the distribution companies and black start generators shall
conduct regular exercises to test the restoration plan and train all parties to
raise awareness and identify improvement to the restoration plan.
OC 12.6 ISLANDED NETWORK

OC 12.6.1. In the event of a part of the System becoming disconnected from the
complete System {islanded), but there has been no resultant Total
Shutdown or Partial Shutdown of the system, the System Operator shall
instruct the regulation of generation and or Load Demand in the group to
enable it to be re-synchronised to the complete System
OC 12.6.2. In order to achieve conditions to permit the re-synchronisation of the
islanded network, the System Operator may adopt one of the following
approaches:
OC 12.6.2.1. The System Operator; the Operators of Generators, HVDC Systems
and DC converters in the islanded network that have Generators
that are connected to the System, or able to be synchronised and
connected to the System; and the distribution companies in whose
area the islanded network is located may exchange information to
enable the System Operator to issue emergency instructions until
the islanded network has been re-synchronised. Until the System is
re-synchronised, there can be no transfer of Load Demand
OC-13 263
between the synchronised and un-synchronised parts of the
System.
OC 12.6.2.2. The System Operator shall issue an emergency instruction to the
Operator (s) of power plants in the islanded network to float local
Load Demand to maintain Target System Frequency until the
islanded network has been re-synchronised. During this period, the
distribution company is required to advise the System Operator of
any anticipated changes in load demand. Transfers into or out of
the islanded system are impracticable.
OC 12.6.2.3. If the supply to a part of the System becomes de-synchronised,
then that part of the network may be shut down and power
supplies restored for the synchronised part of the System.
OC 12.6.3. Local procedures of the distribution companies may be agreed to for each
relevant part of the Total System between the System Operator; Operators
of Power Plants, in the relevant part of the network, and the relevant
distribution companies.
OC 12.6.4. Where the need for Islanded procedure is identified for the first time, and
there is no agreement in place, the System Operator, Operators of Power
Plants, and the local distribution companies shall agree on a procedure.
OC 12.7 INCIDENTS
OC 12.7.1. When an event occurs, that in the opinion of the System Operator or a
distribution company, may have, or have had, a widespread effect on the
System, which is outside the normal functions of system control, an
incident procedure shall be invoked.
OC 12.7.2. The incident procedure shall not take over any function of control of the
System. The procedure shall allow for communication between the
management bodies of various affected Code Participants, and the
distribution of information within their organisations.
End of OC 12
OC-13 264
Work Safety at the Interference
CONTENTS
OC 13.1 INTRODUCTION............................................................................................. 266
OC 13.2 OBJECTIVE.................................................................................................... 266
OC 13.3 SCOPE.......................................................................................................... 267
OC 13.4 SAFETY RULES.............................................................................................. 267
OC 13.5 SAFETY CO-ORDINATORS.............................................................................. 268
OC 13.6 PROCEDURE FOR SAFETY AT THE INTERFACE.................................................. 268
OC 13.7 UNFORESEEN CIRCUMSTANCES..................................................................... 269
OC-13 265
WORK SAFETY AT THE INTERFERENCE
OC 13.1 INTRODUCTION
OC 13.1.1. In order to adequately maintain and repair damage to Transmission System
Plant and/or Apparatus it will be necessary for the SO and/or its agents to
work on or in close proximity to Transmission System Plant and Apparatus,
or in close proximity to User's Plant and Apparatus.
OC 13.1.2. Users and/or their agents will similarly need to work on or in close proximity
to User's Plant and Apparatus which is connected to, or capable of being
connected to in an approved manner, the Transmission System, and from
time to time to work in close proximity to Transmission System Plant and
Apparatus.
OC 13.1.3. It will also be necessary to facilitate work by third parties in close proximity
to Transmission System Plant and Apparatus.
OC 13.1.4. In the event of a conflict between OC.xxx (Safety Co-ordination) and any
other section of the Grid Code, OC.xxx shall take precedence.
OC 13.1.5. The Operation Code 13 (OC-13) specifies the standard procedures, to be

used by the Transmission Network Operator and Users, for the co-
ordination, establishment, and maintenance of necessary Safety
Precautions, when work is to be carried out at or near the National
transmission system and/or a User/Code Participants. Moreover, it specifies
the standard procedures, when there is a need for Safety Precautions on
HV apparatus on the other User's System for the work to be carried out
safety. It does not apply at the interface points between the Code
Participants where Safety Precautions need to be agreed upon solely
between the Users or Code Participants. It does not replace the safety rules
of any Code participants or Users already approved by the Authority. OC-13
does not seek to impose a particular set of Safety Rules on the
Transmission Network Operator or Users or Code Participants. The Safety
Rules to be adopted by the Transmission Network Operator or Users shall
be developed by themselves and approved by the Authority.
OC 13.1.6. To ensure safe conditions for each and every foreseeable situation during
system operation, it is essential that the Transmission Network Operator
and the Code Participants operate in accordance with safety rules and
procedures as laid down in their approved Safety Codes, and other NEPRA
applicable documents. The Transmission Network Operator shall have a
comprehensive approved Power Safety Code in place and available at all
times.
OC 13.2 OBJECTIVE
OC 13.2.1. The objective of OC13 is to ensure that the SO, Users and their respective
agents operate in accordance with approved safety rules, which ensure the
safety of personnel working on or in close proximity to Transmission
System Plant and Apparatus or personnel who may have to work at or use
the equipment at the interface between the Transmission System and the
User System.
OC-13 266
OC 13.2.2. This will normally involve making electrical Plant dead and suitably
isolating / disconnecting (from all sources of Energy) and Earthing that
Plant such that it cannot be made live.
OC 13.2.3. The Safety Rules shall also cover work on live Transmission System Plant
and Apparatus.
OC 13.3 SCOPE
OC 13.3.1. OC13 applies to the SO and to the following Users:
(a) Generators;
(b) Interconnector Operators;
(c) the Distributor System Operator;
(d) Demand Customers;
(e) Demand Side Unit Operators;
(f) Provincial and SPTL Companies;
(g) Generator Aggregators
(h) the Distribution Companies; and
(i) agents of the SO or agents of any User (as defined in OC.13.3(a),(b),(c), (d),
(e), (f), (g) and (h)).
OC 13.4 SAFETY RULES

OC 13.4.1. The safety of personnel working on or in close proximity to Transmission
System Plant and Apparatus for or on behalf of the SO is governed by the
NTDC Networks Electrical Safety Rules.
OC 13.4.2. The safety of personnel working on or in close proximity to User Plant and
Apparatus is governed by the NTDC Electrical Safety Rules, or Users Safety
Rules, as appropriate.
OC 13.4.3. In the event of a conflict between the provisions of this Code and the
provisions of the NTDC Electrical Safety Rules, the provisions of the
NTDC Electrical Safety Rules shall take precedence.
OC 13.4.4. In the event of a conflict between the provisions of this Code and the
provisions of the Users Electrical Safety Rules, the provisions of the
User Electrical Safety Rules shall take precedence.
OC 13.4.5. Where clarification is required regarding the correct interpretation of a rule

within the NTDC Electrical Safety Rules, the SO shall issue the
interpretation to the User as provided by the person responsible for the
NTDC Electrical Safety Rules following consultation with the relevant
parties.
OC 13.4.6. In this document, only the following terms have the following meanings:
 HV Apparatus means High Voltage electrical circuits forming part of a
system, on which safety From the System is required or on which safety
precautions are required to allow work to be carried out on the System.
OC 13.4.7. The words mentioned above are defined as follows:

(a) "Safety From the System" means that condition which safeguards the
persons, when work is being carried-out at or near a System, from the
dangers which are inherent to the System.
OC-13 267
(b) "System" means any User System and/or the national Transmission System,
as the case may be.
(c) "Safety Precautions" means isolation and/or Earthing.
(d) Isolation means the disconnection of apparatus from the remainder of the
System in which that apparatus is connected. The integrity of the Isolation
being achieved and maintained by the use of an approved isolation device,
on which all of the procedures to maintain safety from the System have
been carried out. The means of Isolation shall be maintained in accordance
with the rules of the owner of the Isolation.
(e) Earthing means the application of a connection between the isolated system
and the general mass of earth, by an approved means that is adequate for
the purpose, and is required to be in place in a secure condition in
accordance with the rules of the owner of the Isolation.
OC 13.4.8. The rules for achieving and maintaining isolation and earthing at every site
where this Operating Code No. 13 applies shall be agreed to by all
concerned Parties with respect to Connections at that Site. Local safely
instructions shall be exchanged by all concerned Entities having an interest
in the Connections at a Site.
OC 13.5 SAFETY CO-ORDINATORS

OC 13.5.1. Safety Co-ordinators shall be available at all times for all Sites where this
section of the Operation Code is applicable. These Persons are required to
be authorised by their employer to achieve Safety Precautions on their
Systems, as may be required by other Entities.
OC 13.5.2. When a request is received by an Entity requiring that it make Safety
Precautions on its System to enable the requesting Entity to carry out work
or testing, the details of the request shall be recorded (a model form has
been provided in Appendix 1). The form shall be uniquely numbered. The
party making the request shall also record details of the request and
subsequent confirmation on a uniquely numbered form. The suffixes shall
indicate the appropriate function - (I) for Implementing and (R) for
Requesting Safety Precautions. The recoding of details relating to the
request shall only be undertaken by a person authorised to act as a Safety
Co-ordinator at that Site
OC 13.6 PROCEDURE FOR SAFETY AT THE INTERFACE

OC 13.6.1. Both Code Participants and other concerned Entities shall record the
request for Safety Precautions in their system logbooks and the
implementing Safety Co-ordinator shall arrange for the Safety Precautions
to be made. The implementing Safety Co-ordinator shall confirm when the
requested Safety Precautions have been taken to the requesting Safety Co-
ordinator.
OC 13.6.2. If earthing is required, both Code Participants shall record the request and
the implementing Safety Co-ordinator shall record details in his system
logbook of the actions taken to comply request.
OC 13.6.3. Details of the isolation and earthing achieved shall be formally recorded by
both Entities and the agreement timed and recorded on the appropriate
form. Following issue of the form, the requesting Safety Co-ordinator may
proceed to issue safety documentation at the agreed point of the system
interface between the Code Participants. Neither Entity may issue a safety
document which permits the removal of earth connections nor the
application of any source of energy for testing purposes without the
agreement of implementing Safety Coordinator and then only one such
safety document may be issued on that part of the System at any one time.
OC-13 268
OC 13.6.4. It is the responsibility of the implementing Safety Co-ordinator to ensure
that all Safety Precautions are maintained in place until it is confirmed by
the requesting Safety Co-ordinator that they may be removed.
OC 13.6.5. There shall be a Designated Operator for each User Site.
OC 13.6.6. Operation Instructions for each User Site shall, following consultation with
the relevant User, be issued by the SO to the User and will include:
(a) Detail on the demarcation of responsibility for safety of persons carrying out
work or testing at the User’s Site and on circuits which cross the User’s Site
at any point.
(b) Detailed switching sequences for voluntary, fault and emergency switching;
(c) Control and operational procedures;
(d) Identification of operational boundaries;
(e) Identity of the representatives of the SO and the User(s) and/or their
respective agent s who will attend the Transmission Station and/or facility
for operation and during emergencies;
(f) Other matters agreed between the SO and User
OC 13.6.7. The SO and each User shall co-operate in developing procedures and
agreement on any matters that may be relevant for ensuring overall Site
safety and, in particular, the overall safety of equipment at the interface
between the Transmission System and the User System.
OC 13.6.8. In the event of a Modification or a change in operational practices, which
may have an Operational Effect on a User Site, the SO and the User shall
review the adequacy of overall Site safety.
OC 13.6.9. Adequate means of isolation / disconnection (from all sources of Energy
shall be provided at the interface between the Transmission System and
the User System to allow work to be carried out safely at, or either side of
this point, by the SO and each User.
OC 13.6.10. Where necessary adequate facilities for Earthing and short circuiting shall
be applied to Plant and/ or Apparatus at either side of the interface
between the Transmission System and the User System, to allow work to
be carried out safely at or either side of this point.
OC 13.6.11. On completion of work and the cancellation of all safety documentation, the
requesting and implementing Safety Co-ordinators shall agree to the
cancellation of the form; shall co-ordinate the restoration of the system as
appropriate; and shall ensure all requests and subsequent confirmations
have been recorded in their logbooks.
OC 13.7 UNFORESEEN CIRCUMSTANCES

OC 13.7.1. In the event of unforeseen circumstances, where for example due to
broken conductor or connection on one system infringing safe working
clearances on another system. the Safety Co-ordinators for the
systems involved shall agree a procedure following reports from
their local Safety Co-ordinators as to the exact point of the
problem.
OC 13.7.2. Details in the form of "Record of Inter-system Safety Precautions"
Procedures RISSP-R (Model Form) are provided in Appendix 1.
OC-13 269
OC 13 Appendix 1 (A)
Inter-System Safety
Record of Inter-Safety Precautions (RISSP - R)
(For Requesting Safety Co-ordinator's Record)
RISSP No.
Name and location of the Control Centre:
Name of Control Centre Operator: _
Name and Location of Grid Station/Work Station:
PART 1
1.1 (a) Identification of HV Apparatus where isolation and safety from the system is to be
achieved.
(b) Details of work to be done:
(c) Any other instructions or safety measures to be taken:
1.2 Identification and Safety Precautions Established
(Whether on the implementing safety co-ordinator's system or any other users system
connected to implementing safety co-ordinator system) Tick mark √ in the relevant box.
Identifi Location Isolation Earthing Con Locking

cation firm Arrange
of HV Noti ments
Appara ces Provide
(i) □ □ □ □
(ii) □ □ □ □
(iii) □ □ □ □
CC
1.3 Confirmation and Issues
Mr implementing Safety Co-ordinator at location

_______________________________ has confirmed that the safety precautions identified in Para 1.2
have been established and will not be removed until this RISSP is cancelled
Signature: _____________________
Dated: Name: ________________________
Time: (Requesting Safety Co-ordinator)
Date and Time of Commencement of Work

Date and Time of Completion of the Work
Name & Signature of

Incharge of work
(Authorised Person)
PART 2
CANCELLATION
I have confirmed to Mr. ________ implementing Safety Coordinator at location ___________ that all men
working on the HV apparatus as identified in Para 1.2 have been withdrawn, and the safety
precautions set out in Para 1.2 are no longer required and hence the RISSP is cancelled.
Signature:
Name:
(Requesting Safety Co-ordinator)
Dated:
Time:
Date and Time of Re-energizing of Apparatus
CC
OC 13 Appendix 1 (B)
Inter-System Safety
Record of Inter-Safety Precautions (RISSP - R)
(For Requesting Safety Co-ordinator's Record)
RISSP No.
Name and location of the Control Centre:
Name of Control Centre Operator:
Name and Location of Grid Station/Work Station:
PART 1
1.1 (a) Identification of HV Apparatus where isolation and safety from the system is to be
achieved.
(b) Details of work to be done: _____________________________________________
(c) Any other instructions or safety measures to be taken: ________________________
__________________________________________________________________
1.2 Identification and Safety Precautions Established
(Whether on the implementing safety co-ordinator's system or any other users system
connected to implementing safety co-ordinator system) Tick mark √ in the relevant box.
Identifi Location Isolation Earthing Con Locking

cation firm Arrange
of HV Noti ments
Appara ces Provide
(i) □ □ □ □
(ii) □ □ □ □
(iii) □ □ □ □
CC
1.3 Confirmation and Issues
I, implementing Safety Co-ordinator at location __________________

has confirmed that the safety precautions identified in Para 1.2 have been established and will
not be removed until this RISSP is cancelled
Signature:
Name:
(Implementing Safety Co-ordinator)

Dated:
Time:
PART 2
CANCELLATION
Mr. requesting Safety Coordinator at location has
confirmed that the safety precautions set out in Para 1.2 are no longer required and hence the RISSP
is cancelled.
Signature:
Name:
(Implementing Safety Co-ordinator)
Date:
Time:
Date and Time of Re-energizing of Apparatus
End of OC 13
CC
PLANT IDENTIFICATION
CONTENTS
OC 14.2 EXISTING SITES............................................................................................ 276
OC 14.3 MODIFICATIONS TO SITES............................................................................. 276
OC 14.4 OVERRIDING PRINCIPLE................................................................................ 276
CC
PLANT IDENTIFICATION
OC 14.1.1. Operation Code No. 14 sets out the requirements for the numbering of HV
Apparatus at Sites where the System Operator and a distribution company,
transmission-connected consumer or Generator are responsible for the
Operation and maintenance of HV Apparatus. The sub-code applies to all
Sites where there is a Transmission Connection Point.
OC 14.1.2. The numbering and nomenclature standards to be used for HV Apparatus

for each Site where more than one User has an operational interest shall be
defined by the System Operator. The System Operator shall apply a
common standard lo all such Sites that are connected to the System. The
numbering to be used at each such location shall be confirmed on the
Operation Diagram and in the Connection Agreement for each such Site.
The adoption of a common numbering and nomenclature standard shall
reduce the risk of human error when instructing operations on the system.
OC 14.1.3. Special Purpose Transmission Licensees (SPTLs) shall have numbering and
nomenclature in accordance with the system as notified by the system
operator.
OC 14.2 EXISTING SITES
OC 14.2.1. The numbering and nomenclature at all Sites shall comply with System
Operator standards by the dale of Transfer. Users of Sites are responsible
to ensure that the HV Apparatus conforms to the system operator
standards.
OC 14.2.2. The System Operator shall provide Users with details of its numbering and
nomenclature standards on request.
OC 14.3 MODIFICATIONS TO SITES
OC 14.3.1. When modifications are planned to the HV Apparatus at a Site, which shall
involve modifications or additions to the numbering and nomenclature, at
which more than one Code Participant has an operational interest, the Code
Participant instigating the modification shall give the other Code
Participants at least six months advance notice of the proposed changes.
The proposed modifications to the HV Apparatus and numbering and
nomenclature shall be shown on a draft Operation Diagram and included in
a draft Connection Agreement for the Site. Agreement to the proposed
changes to the numbering and nomenclature shall be agreed in writing
within one month of receipt of the notification of change.
OC 14.4 OVERRIDING PRINCIPLE
OC 14.4.1. The numbering and nomenclature used at a Site must be clear and
unambiguous. No alterations to the HV Apparatus and its
numbering and nomenclature that would result in confusion
relating to the identity of the HV Apparatus shall be permitted.
End of OC 14
CC
SYSTEM TESTS
CONTENTS
OC 15.2 NOTIFICATION.............................................................................................. 278
OC 15.3 TEST CO-ORDINATOR AND TEST PANELS........................................................ 278
OC 15.4 THE TESTS AND FOLLOW UP ACTION.............................................................. 279
CC
SYSTEM TESTS
OC 15.1.1. Operating Code No. 11 details the procedure for carrying out system tests
which involve creation of Unusual, extreme or abnormal system conditions
on the Total System, and excludes commissioning or recommissioning
tests, which are carried out on a small defined part of the System. The sub-
code covers the System Operator, Transmission connected Consumers,
Operators of Power Plants, distribution companies and the Operators of
Externally-connected Parties/Consumers. A system test proposed by a User
that shall have no effect on the National Transmission System is not subject
to this sub-code. A system test proposed by the System Operator shall
always to subject to this sub-code.
OC 15.1.2. The purpose of this sub-code is to ensure that the safety of the general
public and the personnel of the Users is not jeopardised and that the risk to
power supplies and facilities of the Transmission System and Users, and the
integrity and security of the system are maintained at the highest levels
possible under such specified conditions.
OC 15.1.3. Tests for distribution company and transmission-connected Consumers

facilities.
OC 15.1.4. The System Operator shall test distribution company's equipment including
132 kV facilities and protective relaying system for compliance with the
Connection Code at the Point of Connection. Test shall include the
following:
(a) Verification of equipment ratings at the substation;
(b) Calibration of under-frequency relay used for load shedding;
(c) Operation of circuit breakers, switches and controls;
(d) Verification of relay co-ordination and settings; and
(e) Calibration of electrical transducers used for measurements.
Distribution Companies and Transmission-connected Consumers shall submit operating

characteristics of their system, relay setting calculation and co-ordination with Transmission
Network protective relaying system, calibration records of electrical transducers
and electrical instruments to the System Operator.
OC 15.2 NOTIFICATION
OC 15.2.1. When a User has decided that it needs to perform a system test, it shall
issue a proposal notice to the System Operator detailing the nature, extent
and purpose and the plant and or apparatus involved. The proposal notice
shall be issued at least 12 months in advance of the proposed system test.
The System Operator shall be satisfied that it has received sufficient time
to give full consideration to the proposal.
OC 15.2.2. Following consideration of the information on the proposal notice, the

System Operator shall determine which other Users are likely to be affected
by tt1e system test and shall, after consultation with the affected Users
appoint a suitably qualified test co-ordinator. The same actions shall be
taken if the proposal notice has been issued by the System Operator.
CC
OC 15.3 TEST CO-ORDINATOR AND TEST PANELS
OC 15.3.1. A preliminary notice shall be issued to all Users affected by the proposed
system test, and shall include an invitation to nominate members of a test
panel. Time schedules shall be agreed to which are consistent with the
System involved, and the nature of the testing to be carried out.
OC 15.3.2. The test panel shall consider the test proposal in relation to the possible
safety, economic and operational risks; the possibility of combining the
proposed test with other tests and proposed system outages. The test
panel shall produce a proposal report which shall include details of the
proposed test and the manner in which the proposed system test shall be
undertaken and monitored. The proposal shall also consider the cost
implications and propose the allocation of costs. The proposal report shall
be circulated to all Users affected by the proposed system test. Objections
to the proposal report shall be considered to determine if the proposal can
be modified to accommodate their objections. In the case of failure to
agree, the matter shall be referred to the Grid Code Review Panel whose
decision shall be binding upon all the concerned Parties.
OC 15.4 THE TESTS AND FOLLOW UP ACTION
OC 15.4.1. Following agreement, the test panel shall prepare a test programme, which
shall detail the procedure to be used on the day of the test. If system
conditions on the day of the test are not as envisaged or if after
consideration of other factors such as severe weather the test co-ordinator
may delay, postpone or cancel the system test.
OC 15.4.2. A final report shall be prepared by the Entity proposing test and circulated
to members of the test panel detailing the tests carried out, the
results and conclusions.
End of OC 15
CC
PROTECTION AND METERING CODE
CONTENTS
PMC 1 INSPECTION AND TESTING............................................................................. 281
PMC 2 METERING AND PROTECTION......................................................................... 281
PMC 3 PROTECTION OF POWER SYSTEM EQUIPMENT................................................. 298
CC
PROTECTION AND METERING CODE
PMC 1 INSPECTION AND TESTING
Each User/Code Participant must furnish, for the System Operator review and approval,
proposed settings of the relays of their facilities. If requested, the System Operator shall
provide its Transmission System data needed to determine the relay settings.
Before commencing integrated operation with the National Transmission System, the
installation must be witnessed and inspected by the System Operator. The Code Participant is
responsible for providing necessary equipment and qualified personnel, who will complete all
required tests. the System Operator shall not perform any of the testing unless contracted to
do so.
The Code Participant must perform submit certified test reports to the System Operator, and
have the System Operator witness the following tests:
(a) CT and PT ratio tests

(b) CT and PT secondary circuit tests to verify phasing, polarity etc.
(c) Completion of relay manufacturers recommended acceptance tests.
(d) Tests of phasing between the national transmission network and Code Participants
System. (Primary Voltage)
(e) Directional test for distance (impedance) relay (s), if required.
(f) Final synchronization tests, before paralleling the two systems, to verify Code
Participants/Generator (s) are in phase with the National Transmission System.
(g) Earthing - Earthing test to be performed at request of the System Operator
(h) Insulation - Megger and hi-pot testing
(i) Switching Operation - Functional Operational Testing
(j) Other tests prescribed by the System Operator to verify design conformance,
functioning and safety of equipment.
(k) CT/PT Continuity test
(l) C & OF test for CT/PT
(m) CT Saturation Curve Test
(n) CT VA Burden test
Satisfactory results shall demonstrate the design performance, functionality, and safety of
individual components as well as the entire substation.
The User/Code Participant must notify the System Operator at least ten business days before
performing the required tests. Updated drawings (as built) must be provided to the System
Operator for verification at least seven business days before performing testing.
Once the System Operator determines the installations to be suitable to operate in parallel
with National Transmission System, both the Code Participant and the System Operator
representatives must sign and date the "Approval for Operation of the Facility" in, parallel with
the National Transmission System. After this is done, the Code Participants facility is
authorized to operate its System in parallel with the National Transmission system.
PMC 2 METERING AND PROTECTION
PMC 2.1 Metering Coordination

PMC 2.1.1 Purpose
This section specifies the minimum technical, design and operational criteria
for revenue metering, for the purpose of electricity sales and flow, which
must be complied with by all Generators and other Users connected to or
CC 280
seeking connection with the electric Transmission System of DISCOs and/or
National Transmission and Dispatch Company.
For the purpose of settlement, electric energy (active and reactive) supplied
and delivered at each defined metering point must be measured and
recorded through metering equipment installed, operated and maintained
under this Metering Code with the accuracy standards defined in this sub-
code.
The scope of this Code applies to all NTDC Transmission System Users, i.e.
(a) NTDC;
(b) All Generators connected at the Transmission system
(c) Generators with capacity greater than 10 MW;
(d) DISCOs;
(e) Transmission-connected Consumers; and
(f) Externally Connected Consumers/Parties, like
(i) Special Licensee Transmission Company
(ii) Provincial Companies
(iii) Interconnector Operators
(iv) Aggregators
(v) Independent Power Producers (IPP)
(vi) Demand Customers who for the purposes of this Metering Code
are deemed to be the Users
PMC 2.1.2 For all Metering Equipment, this Metering Code specifies the conditions
governing the following:
(a) technical, design and operational criteria;
(b) accuracy and calibration;
(c) approval, certification and testing;
(d) meter reading and data management.
PMC 2.2 Meter Provision

PMC 2.2.1 Metering Equipment shall be provided and installed as soon as is reasonably
practicable and shall be maintained and inspected by Relevant Meter
Operator to the standards specified in this Metering Code.
PMC 2.2.2 Records of relevant Meter data, identification and specification details shall
be established and maintained by the Relevant Meter Operator.
PMC 2.3 Location of Metering Points
PMC 2.3.1 The Defined Metering Point shall be at the Connection Point on the
Distribution or Transmission System as applicable, as defined in the relevant
connection agreement to the system.
PMC 2.3.2 Metering facilities would be installed at the substation for Point of Connection
between the Users and the National Transmission System. Metering between
the Generator and the National Transmission System would be installed at
the high voltage side of the Point of Connection.
Metering between the Delivery Point to the User and the transmission
network would be installed at the low side of the connection.
PMC 2.3.3 Metering cabinet shall be installed inside the substation building. Revenue
class instrument transformers as specified in IEC or IEEE Standards shall be
installed at the substation as required.
PMC 2.3.4 Notwithstanding the above, the location of the Metering Point on each
transformer shall be such that the cost of transformation losses shall always
be with the Entity that owns the transformer.
PMC 2.4 Main and Check Metering
CC 281
PMC 2.4.1 For connections greater than or equal to XX MVA and for Generators with
connections below XX MVA who opt to participate in the wholesale market
under the Trading and Settlement Code, Main and Check Metering shall be
provided. Main and Check Meters shall operate from separate current
transformers (CT) and voltage transformers (VT) windings.
PMC 2.4.2 CT and VT windings and cables connecting such windings to Main Meters
shall be dedicated for such purposes and such cables and connections shall
be securely sealed.
PMC 2.4.3 CT and VT windings and cables connecting such windings to Check Meters
may be used for other purposes provided the overall accuracy requirements
are met and evidence of the value of the additional burden is available for
inspection by the Market Operator.
PMC 2.4.4 The Main Meter, Check Meter and additional burdens shall have separately
fused VT supplies.
PMC 2.4.5 Where sub-metering of certain Generating Units is required, with the
agreement of Relevant Meter Operator, a User may supply metering class
CTs and VTs for use on the sub-circuits. This equipment must comply with the
standards set out in this Metering Code. Such equipment shall be subject to
acceptance testing by Relevant Meter Operator for each site.
PMC 2.5 Metering Equipment Approval, Certification And Testing
PMC 2.5.1 The Relevant Meter Operator shall maintain records relating to the calibration
of all Metering Equipment including the dates and results of any tests,
readings, adjustments. Any such records shall be complete and accurate and
retained for the life of the relevant item of Metering Equipment.
PMC 2.5.2 The Relevant Meter Operator shall make arrangements to seal all Metering
Equipment (including the date of sealing) and associated modems and
telephone links.
PMC 2.5.3 Test terminals shall be provided for Main and Check Meters to facilitate on
site tests. These terminals shall be in close proximity to the Meters.
PMC 2.5.4 Meters shall be tested if a divergence occurs between the Main and Check
Meters that is more than XXX times the prescribed limit of error.
PMC 2.5.5 Any affected User may request a test to be carried out. Tests will be
organised such that all relevant Users are aware of the tests, are invited to
witness them if required and the test results are made available to the User
involved.
PMC 2.5.6 Care shall be taken in carrying out tests to ensure that any interruption to
measurement is avoided or minimised.
PMC 2.5.7 Where a test indicates that an error exceeds the limits of error then these
errors shall be recorded before promptly adjusting, repairing or renewing the
Metering Equipment (or part thereof) or replacing any defective components.
The Metering Equipment shall be restored to service and proved to be
operating within the prescribed limits of accuracy as soon, as is reasonably
practicable. In such cases, substitute data shall be provided for settlement
purposes in accordance with the Trading and Settlement Code agreed
procedures.
PMC 2.5.8 Records of the pertinent data required for successful testing / calibration
shall be established and maintained by the Relevant Meter Operator.
PMC 3 Application
Metering shall provide accurate metering of electrical quantities delivered to or

received from the NTDC Transmission System. All points of injection and withdrawal of
energy on the the national transmission system will be metered. The System
Operator will maintain an electronic log of metering failures which will document the
CC 282
duration of meter data failures and this log will be electronically available to other
approved Users of metering data.
Metering devices including all instrument transformers must have revenue class
accuracy in accordance with the applicable System Operator Standards or IEC
Standards as listed in PMC 2.1.f, for reference with options for measuring apparent
energy, active and reactive energy, load demand, power factor, etc. that are required
for billing, planning and engineering purposes. Metered quantities shall be remotely
transmitted and recorded in the metering database at the computer systems of the
System Operator/Market Operator.
Metering shall be provided in a separate metering cabinet to be located in a control

building.
For new metering installations separate dedicated revenue class current (CT) and
potential (PT) transformers shall be provided for revenue metering, and shall not be
shared with protection system or Check meter.
For existing installation where instrument transformers are shared for metering and
protection, a metering audit shall be performed to ascertain that no unacceptable
error due to overload or instrument transformer saturation is introduced in the
metering. If error introduced lo revenue metering is unacceptable, new instrument
transformers for metering shall be installed.
CTs and PTs shall have a locking termination compartment that can be sealed. All
wiring between the CTs and PTs shall be stranded copper wire, with PVC/polyethylene
jacket.
The metering cabinets shall be installed in rigid conduits. The metering cabinet shall
be heavy gauge steel, primed and finished with gray finish, with locking door. A glass
window shall be provided on the door to permit visual reading of the meter.
PMC 4 Principles
Metering facility shall be provided at the Point of Connections between Code

Participants and the transmission system to record energy and maximum power
(Active and Reactive both) supplied to or delivered from the Transmission System for
the purposes of billing, engineering studies, and planning.
Metering must provide accurate measurements of energy and power delivered at the
Points of Connection between National Transmission System, Generators and
other Users. All metered electrical quantities, including time and date information
shall be transmitted to the System Operator for processing, billing and settlement of
accounts. Metering data shall be made available to Code Participants.
PMC 5 Metering Requirements
Metering will be installed by the System Operator at a secured location in the

substation where connection between the Generator or other Users and the
Transmission System is made. Metering and instruments transformers shall be
installed in such a manner that they cannot be tampered with.
Each User/Code Participant shall provide and install the revenue meter at the
connection location. Meter shall be the type and model approved by the NTDC. Meters
and associated CTs and PTs shall comply with relevant IEC Standards listed in PMC
2.1.f., and/or applicable System Operator Standards.
The CTs and PTs shall be supported be required accuracy certificate from the
manufacturer. The energy meter test shall be conducted or site jointly by the System
Operator and the respective Code participant.
CC 283
The System Operator shall be responsible for testing and maintenance of the meters,
and shall have test and calibration facility, with necessary tools and instruments, for
testing and calibration of meters and will be responsible for periodic testing and
maintenance of the metering and ancillary equipment. All test equipment shall
comply with IEC 60736 or applicable IEC Standards to be prescribed by NTDC. The
User shall replace meter or other metering component that is found to be defective.
PMC 6 Standards
Protection/Metering Devices and instrument transformers for revenue metering must

comply with the latest applicable international and local standards, including, but are
not limited to, the following:
 IEC 60145 Var-hour (reactive energy) meters.

 IEC 60521 Class 0.5, 1 and 2 alternating-current watthour Meters.
 IEC 60687 Alternating current static watt-hour meters for active energy
(classes 0.2 S and 0.5 S).
 IEC 61036 Alternating current static watt-hour meters for Active energy
(classes 1 & 2).
 IEC 61107 Data exchange for meter reading, tariff and load control – direct
local data exchange.
 IEC 61354 Electricity meters - marking of auxiliary terminals for tariff devices.
 IEC 61361 Electricity metering - local and remote data exchange.
 IEC 62053-61 Electricity metering equipment (ac) - particular requirements -
Part 61: power consumption and voltage requirements.
 IEC 62056-31 Electricity metering - Data exchange for meter reading, tariff
and load control - Part 31: Use of local area networks on twisted pair with
carrier signalling.
and load control - Part 41: Data exchange using wide area networks: Public
Switched Telephone Network with LINK+ protocol.
and load control - Part 51: Application layer protocol.
 IEC 61869-1 Instrument transformers - Part 1: General requirements.
 IEC 61869-2 Instrument transformers - Part 2: Additional requirements for
current transformers.
 IEC 60255-1 Measuring relays and protection equipment - Part 1: Common
requirements
PMC 7 Performance Requirements
PMC 7.1 Revenue metering and ancillary equipment must read energy and power
(Active and Reactive) delivered to or received from the Transmission
System, with an appropriate degree of accuracy specified in applicable IEC
Standards, but not less than +/- 0.2%. Revenue class metering shall have the
following characteristics:
(i) three elements four-wire configuration, electronic, digital, with accuracy

class of 0.2 in accordance with IEC Standards for Grid Meters.
(ii) Meters shall be capable of measuring and recording active energy at 30
minutes intervals for a period of 70 days with intervals programmable
from 5 minutes to 30 minutes.
(iii) The meter must have the capability of recording active and reactive
power and energy and maximum Load Demand for the entire billing
period. The meter-billing period may be programmable and capable of
being programmed to automatically store the accumulated value and
reset the counter for the next billing period.
CC 284
(iv) Multiplier corresponding to the combination of CT and PT ratios may be
programmable in the meter. Accuracy class of CT and PT shall be in
accordance with System Operator technical specifications.
(v) Meters may be capable of time-of-use and seasonal applications. Meters
shall have internal time clock for time and date stamping of data. Time
clock must have high accuracy and synchronize to GPS time signals.
(vi) Meters may have capability for remote meter reading by telemetering or
by SCADA. Communication ports should be provided with optical and
serial data communication with industry standard protocol support.
(vii) Meter should have self-diagnostic capability and include an alarm to
indicate failure and/or tampering.
PMC 7.2 In cases where data is not available due to a failure or in cases where the
Main Meter has been proven to have operated outside the prescribed limits
of error:
(a) Data substitution and estimation rules may be used.
(b) These data estimation and substitution rules can employ Check
Meters, SCADA and for dispatchable Generators, Generator
Aggregators, ESU & Demand Users instructed quantities and station
energy and any other means deemed appropriate.
(c) These data substitution and estimation rules will be provided by the
Relevant Data Provider for approval by the Commission.
PMC 8 Installation
PMC 8.1 Installation of revenue meter and ancillary equipment at the substation for the
Point of connection shall be the Generator and other Code
Participant/Users' responsibility.
PMC 8.2 The Generators and other User connecting to the Transmission System
shall submit to the System Operator for approval the engineering design for
revenue metering, proposed location of metering equipment and ancillaries
complete with wiring and installation drawings and bill of materials.
PMC 8.3 The proposed metering location shall be adjacent to any telemetering,
communication and data logging equipment.
PMC 8.4 Revenue metering and ancillary devices shall be provided in secured metal
enclosure. Enclosure shall have doors with locks for easy access. Glass window
shall be provided on the door to allow visual reading of the meter inside the
enclosure.
PMC 8.5 Metering Equipment shall be installed such that metered data held in the
metering installation is protected from direct local or remote electronic access
by suitable password and security controls.
PMC 8.6 Instrument transformers shall be installed in secured location and shall be
dedicated and not be shared with protection or other metering devices, to
prevent tampering. All wiring between the instrument transformer outside the
metering compartment shall be installed in rigid galvanized steel conduits.
Meter shall be located where it is accessible for reading the registers and for
testing and maintenance.
PMC 8.7 Access to the metering facility shall be accorded to NTDC personnel as per
PMC 2.1.k.
PMC 9 Telemetering (Data Collection System)
CC 285
PMC 9.1 Facilities are to be provided for remote transmission of metering information
to the System Operator/Market Operator to be recorded in the metering
database. Transmission of telemetered data information must be secure and
reliable and not prone to tampering. All metered quantities including times
and date of acquisition must be telemetered.
Quantities that are to be metered shall include:
i. Apparent Energy
ii. Real Energy
iii. Energy (kWh or MWh) delivered to Load
iv. Energy (kWh or MWh) received from Supply
v. Reactive Energy (kVArh or MVArh)
vi. Peak Demand MW or KW
vii. Peak MVAr or kVAR Demand
viii. Power Factor
ix. Active and Reactive Energy Import and Export (MWh and MVARh)
x. for each 15-minute Demand Period, the Metering Equipment shall be

capable of recording the following Demand Values:
a. Import kW;
b. Import kVAr.
xi. 15-minute Demand Period, the Metering Equipment of Generators and
Customers with their own Generating Units shall be capable of
recording the following Demand Values:
a. (c) Export kW;
b. (d) Export kVAr.
Metering database is to be provided at the System Operator/Market
Operator Headquarters or National Power Control Centre location. Database
shall have metered quantities, meter information, metering constants,
instrument transformer ratios, etc. Information in the data base computer will
be accessible to for billing, engineering studies and planning.
Where any User is required to carry out a process necessitating metered data, the
Relevant Meter Operator shall specify the form and time period in which such
data shall be provided or may be obtained.
Metering data will be electronically shared with other entities in the electric
industry that have a demonstrable need. This includes at a minimum NEPRA, the
System Operator, Discos, Provincial & SPTLs Companies and the CPPA-G or
their successor organizations. Such entities may, for their own purposes, estimate
meter data and use those estimates as long as that fact is disclosed to participants.
The NTDC, in conjunction with other entities in the electric industry may establish
timelines for meter submittal, as well as standard operating procedures for
Validation, Estimation and Editing (VEE) of meter data.
The communication protocol for transmitting metering information shall be in

accordance with IEC 61107.
PMC 9.2 Data Storage

PMC 9.2.1 Data storage facilities for metering data shall be provided as follows:
(a) a storage capacity of 96 periods per day for a minimum of twenty [xx]
days for all Demand Values;
(b) the stored Demand Values shall be integer values of kW or kVAr, or
pulse counts, and have a resolution of better than ~ 0.1% (at full load);
(c) the accuracy of the energy values derived from Demand Values shall
be within + 0.1% (at full load) of the amount of energy measured by the
associated Meter;
CC 286
(d) the value of any energy measured in a Demand Period but not stored
in that Demand Period shall be carried forward to the next Demand
Period;
(e) in the event of a Metering Equipment power supply failure, the
Metering Equipment shall protect all data stored up to the time of the
failure, and maintain the time accuracy in accordance with Section 6.6
below;
(f) to cater for continuous supply failures, the clock, calendar and all data
shall be supported for a period of xx days without an external supply
connected;
(g) any "read" operation shall not delete or alter any stored metered data;
(h) Metering Equipment shall provide any portion of the data stored upon
request by the Data Collection System.
PMC 9.3 Data Communications

PMC 9.3.1 Load profile metering will be equipped with standard communications ports
for local and remote downloading of load profile data and other metered
data.
PMC 9.3.2 All data communications equipment shall conform to the relevant
International Telecommunications Union (ITU) standards and
recommendations for data transmission over telecommunications systems.
PMC 9.3.3 Site specific Isolation requirements may also apply in accordance with
established good practice and in line with the specific requirements of the
telecommunications service provider.
PMC 9.3.4 Metered data collection systems shall remotely interrogate Metering
Equipment to extract data at appropriate intervals as set out by the Relevant
Meter Operator.
PMC 9.3.5 Remote interrogation shall be by means of dial-up telephone, leased line,
mains borne, packet switching data networks or other suitable system, using
Meter and communications equipment protocols as specified by the Relevant
Meter Operator and other data systems required under the Trading and
Settlement Code.
PMC 9.3.6 In the event of failure of communications facilities, metered data shall be
read by a Locally Attached Device and transferred to the central Data
Collection System as set out by the Relevant Meter Operator.
PMC 9.3.7 For new and replacement Meters, the following data shall be capable of
remote interrogation:
(a) Demand Values;
(b) Maximum Demand and energy Registers.
PMC 9.4 Password Security

PMC 9.4.1 To prevent unauthorised access to the data in the Metering Equipment a
security scheme, as described below, shall be incorporated for both local and
remote access. Separate security levels shall be provided for the following
activities:
(a) Level 1 - Password for read only of the following metering data, which
shall be transferable on request during the interrogation process:-
(i) a) Outstation ID;
(ii) b) Demand Values;
(iii) c) Cumulative measured quantities;
(iv) d) Maximum Demand (MD) for kW or kVAr per programmable
Charging Period;
(v) e) Multi-rate cumulative Active Energy;
CC 287
(vi) f) Alarm indications; and
(vii) g) Outstation time and date.
(b) Level 2 - Password for:-

(i) a) corrections to the time and/or date; and
(ii) b) resetting of the MD.
(c) Level 3 - Password for programming of:-

(i) a) displays, tariff schemes and other functions; and
(ii) b) the passwords for levels 1, 2 and 3.
(d) Level 4 - Password for removal of Metering Equipment cover(s)

necessitating the breaking of a seal for:-
(i) a) calibration of the Metering Equipment;
(ii) b) programming the level 3 password and the level 4 password.
PMC 9.4.2 In addition to the functions specified for each level it shall be feasible to
undertake the functions at the preceding or lower level.
PMC 9.5 Timekeeping
PMC 9.5.1 Metering Equipment shall be set to Co-ordinated Universal Time (UTC) with
the facility to switch annually to Daylight Saving Time (DST). No switching
shall occur for quarter hourly data.
PMC 9.5.2 Time adjustments may be performed as required by communications with the
Data Collection System.
PMC 9.5.3 The commencement of each Demand Period shall be within ±20 seconds of
true time. The duration of each Demand Period shall be accurate to within ±
0.1% except where time synchronisation has occurred in that period.
PMC 9.6 Reconciliation of Display Reading for DSO Connected Metering
PMC 9.6.1 Cumulative Total Active and Reactive Energy Registers from Meters are read
remotely each day and are compared with the electronically recorded total
energy for the same time period, as part of the ongoing data validation by
Distribution, Provincial and SPTLs Operators. This energy tolerance
calculation is carried out by the central Data Collection System, and
differences greater than ±2% result in automatic rejection of the metered
data.
PMC 9.6.2 If the Cumulative Total Energy Register is not available remotely, then a
manual read will be taken at twelve monthly intervals for checking purposes.
PMC 9.6.3 For meters where the cumulative total energy Register is available to be read
remotely, a manual read will be taken at twelve monthly intervals for
checking purposes from a random sample of 5% of these metering sites, and:
(a) Within twenty [XX] Business Days from the date of a manual meter
reading a meter reconciliation statement shall be produced. The
difference between the latest manual meter register readings and the
previous manual meter register readings shall be calculated and
compared with the electronically recorded total energy for the time
interval involved, and
CC 288
(b) The calculations shall be recorded and differences greater than 0.1%
shall be highlighted and referred for checking. Where the checks confirm
the discrepancy the Meter Registration System Operator (MRSO)
and other parties as required shall be informed and appropriate actions
shall be taken in accordance with the procedures set out by the MRSO.
PMC 9.7 Reconciliation of Display Reading for TSO Connected Metering
PMC 9.7.1 Meter Advance Reconciliation shall be undertaken in accordance with TSO’s
Metering procedures, submitted to agreement stipulated within the
Commercial Code
PMC 10 Settlement of Account
(1) The data will be validated and substituted, or estimated data will be provided
where appropriate, by the Relevant Data Provider. The data shall be
processed and aggregated to rules set out by the CTBCM_DR.
(2) As a minimum, for each registered Meter, seven [7] full years of metered data
shall be retained.
(3) Discrepancy in meter reading arising from error introduced by the meter or
saturation or defect in instrument transformers should be resolved by the Grid
Code Review Panel. This may require an audit of the metering system to
verify the accuracy of the meter and instrument transformers. If problem with
the meter and instrument transformer accuracy is detected, the reading will be
adjusted as per agreed procedure between the Users/Code Participants and
System Operator.
(4) The User/Code Participant, at his option, may elect to install a check meter to
verify the reading in the revenue meter at the Point of Connection. Instrument
transformers for revenue meter must not be shared with check metering. Any
Check Meters should have separate instrument transformers
(5) All disputes regarding meter readings and settlement of accounts shall be
presided over by NTDC in accordance with the provisions of the Commercial
Code and Bulk Power Supply Agreements (to be developed later).
PMC 10.2 Equipment Accuracy and Error Limits

(a) The accuracy of the various items of measuring equipment shall conform to
the relevant national IEC Standards (or equivalent International Standards).
(b) The accuracy class or equivalent, is based on the MVA capacity of the
connection and shall as a minimum be as follows (subject to operating
within the combined limits of error set out in Section 5.7.6 below):
Table 1 – Equipment Accuracy Class – Active and Reactive Energy
CC 289
(c) Where the Actual Metering Point and the Defined Metering Point do not
coincide then, where necessary, compensation for power transformer
and/or line losses shall be provided to meet the overall accuracy
requirement at the Defined Metering Point. The compensation may be
applied locally within the Metering Equipment or remotely. In both cases,
compensation factors and the justification for them must be recorded.
These records shall be made available for inspection.
(d) For the measurement of Active and Reactive Energy, Metering Equipment
shall be tested and calibrated to operate within the overall limits of error as
set out below, after taking due account of CT and VT errors and the
resistance of cabling or circuit protection. Calibration equipment shall be
traceable to a recognised national or international standard.
Table 2 – Limits of Error at Stated Power Factor – Active Energy
Table 3 – Limits of Error at Stated Power Factor – Reactive Energy
CC 290
PMC 10.3
(a) Records shall be made of the pertinent data required for a successful test
and calibration as per the requirements of Section XXX above. standard.
(b) Where existing measurement transformers do not comply with all of the
conditions of this Metering Code, then these shall be acceptable provided
each of the following conditions are met:-
1. new measurement transformers are installed (fully compliant with
this Metering Code) when a significant electrical plant alteration is
to be carried out;
2. where the transformers are not wholly dedicated to settlement
Metering, then the additional burdens must be quantified and
accounted for in calibrations and testing.
The burden should not be changed without notification of the Relevant

Meter Operator.
PMC 10.4 The Main Meter, Check Meter and additional burdens shall have separately
fused VT supplies.
PMC 11Access
Each User/Code Participant shall authorize each Code Participant, its employee,
agents and sub-contractors right to enter upon and pass through and remain upon
any part of such User's property to the extent necessary for the purpose of
performance obligations under this sub-code.
The right of access provided for under this sub-code includes the right to bring on to
such Code Participants/User's property such vehicles, plant, machinery, and
maintenance or other materials as shall be necessary for the purpose of performance
obligations under this sub-code.
Each User/Code participant shall ensure that all reasonable arrangements and
provisions are made and/or revised from time to time as when necessary or desirable
to facilitate the safe exercise of his right of access.
PMC 12 Tamper and Revenue Protection
Representatives of the System Operator and any other concerned Entity shall
supervise meter installation. After completing the installation, the representatives of
concerned Entity, the System Operator as observers, shall lock and seal the meter
and metering compartment.
CC 291
PMC 13 Testing and Calibration
Meter audits shall be conducted periodically, on a schedule to be determined by the

System Operator and Code Participants/Users but not less than every two years, to
verify meter accuracy and resolve disputes regarding meter reading. Meter audit may
be performed by the System Operator. Meter found to be inaccurate would be
removed for testing and calibration at the System Operator laboratory. the System
Operator laboratory shall have all the necessary equipment and devices to test and
calibrate the different types and models of meters used.
Test and calibration of meters shall be in accordance with applicable IEC Standards
listed in PMC XXX, above. All test equipment for testing energy meters shall conform
to IEC 60736, Testing Equipment for Electrical Energy Meters.
PMC 14 Right to access and use of Discos, Provincial & SPTLs company's
switchyard by the System Operator
The System Operator shall have the right to enter a DISCOs, Provincial & SPTLs
companies and Demand Consumers switchyards for the purpose of installing,
checking, testing and maintaining metering and related equipment and wires.
DISCOs, Provincial & SPTLs and Demand Consumers shall accommodate
requests by the System Operator for access on demand, and shall not prevent the
System Operator from making unscheduled inspections on short notice.
PMC 15 Protection Coordination
a. General
The design of Inter-connection between any Generating and/or Energy Storage

Units, other Users and the National Transmission System should be consistent
with the Operation, Planning Standards and Protection Design Standards of the
System Operator, and the Standards laid down in this Grid Code. Apparatus for
the protection of Generating and/or Energy Storage Units, other Users ,
substation equipment and transmission lines from faults and overloads shall be
provided at the Points of Connection. Both Primary and Secondary (back-up)
protection schemes are to be provided to enhance system reliability. Design
and settings of protection system shall be coordinated between the Users/Code
Participants and the System Operator. Settings of protective devices shall be
reviewed periodically by NTDC to maintain consistency with operation, planning
and protection design standards.
b. Standards and Practices
Protection devices shall conform to the applicable IEC Standards and prudent
utility practices adopted by the System Operator. Design of protection system
at the Points of Connection shall be submitted by Users/Code Participants for
review and approval of the System Operator.
c. Generating Unit, Energy Storage Unit (ESU) Protection
Connection between a Generating Unit, or ESU and National Transmission

System must be controlled by a circuit breaker capable of interrupting the
maximum short circuit current at the Point of Connection. The maximum
short circuit current shall be specified by the System Operator at the time of
design based on most recent analyses.
Protection of Generating Unit, or ESU and their connections to the National

Transmission System must meet the minimum requirements delineated below
(relay settings are to be reviewed by the System Operator from time to time):
CC 292
i. For faults on the Generating Unit’s, or ESU 's equipment directly
connected to the national Transmission System and for faults on the
National Transmission System directly connected to the Generating
Unit’s, or ESU 's equipment, fault clearance period from fault
inception to circuit breaker arc extinction shall be set out in either
Transmission Service or Connection Agreement, as the case may be.
The time limit shall be according to the respective IEC Standards.
ii. In the event the fault clearance times are not met as a result of a
failure to operate the primary or main protection system, a back-up
or secondary protection system shall be provided. Back-up protection
shall be coordinated with the primary protection so as to provide
discrimination.
On the Generating Unit, or ESU connected to the National Transmission

System where only one primary or main protection is provided to clear fault on
the high voltage Generating Unit, or ESU connections within the required
fault clearance time, the secondary or back-up protection in the Generating
Unit, or ESU shall operate within the limits provided in the respective IEC
Standards. On the Generating Unit, or ESU connected to the National
Transmission System where two primary or main protections are provided, the
secondary or back-up protection shall operate to give a total fault clearance,
which is within the time limits provided in the respective IEC Standards.
Generating Unit, or ESU secondary or back up protection shall be required to

withstand, without tripping, the loading incurred during clearance of a fault by a
breaker fail protection on the National Transmission System. Back-up
protections in the Generating Unit, or ESU and National Transmission System
shall be coordinate to provide discrimination.
i. Circuit breakers provided at the Points of Connection between the

Generating Unit, or ESU and the National Transmission System
shall be provided with breaker fail protection. In the event the
breaker failed to operate, the breaker fail protection shall initiate
tripping of all the electrically adjacent circuit breakers within the
time limits provided in the respective IEC Standards.
ii. The target performance for the system fault dependability index
shall not be less than 99%. This is a measure of the ability of the
protection system to initiate successful tripping of circuit breakers
that are associated with the fault in the system.
iii. The Generating Unit, or ESU shall have protection equipment, but
not limited to the following:
• Short circuit and Earth fault Protection of primary conductors from
the current transformer at the line side of the circuit breaker to the
Point of Connection.
• Circuit breaker fail protection equipment shall be provided at the
Generating Unit, or ESU. A back-up trip signal shall be provided
in the event of a main circuit breaker failure to trip the electrically
adjacent breakers to clear the fault.
• Protection shall be provided to initiate a Generating Unit, or ESU
trip when loss of excitation is detected.
• Pole slipping protection shall be provided with the synchronous
generating units.
(iv) Protection system shall be designed to provide adequate protection of the
Generating Unit, or ESU, substation apparatus and the Transmission
System.
(v)
d. Substation Protection
CC 293
Connections between the Transmission System and other Users/Code
participants (DISCOs, Provincial, SPTLs Companies and Demand
Consumers, etc.) substations must meet the minimum requirements
delineated below:
i. For faults on the User's substation equipment directly connected

to the Transmission System and for faults on the Transmission
System directly connected to the User's substation equipment, fault
clearance period from fault inception to circuit breaker arc extinction
shall be set out in the respective Transmission Service or
Connection Agreement as the case may be. The period specified
shall be within the time limits specified in the respective IEC
Standards or by requirements of transient stability.
ii. Longer fault clearing times may be specified by System Operator if
permitted by protection and design criteria of the System Operator.
iii. In the event the primary or main protection system failed to meet
the fault clearance times listed above, a backup or secondary
protection system shall be provided. Backup protection shall be
coordinated with the primary protection so as to provide
discrimination.
iv. Code Participants/Users substations connected to the National
Transmission System where only one primary or main protection is
provided to clear fault of the Points Connection within the required
fault clearance time, the secondary or back-up shall operate to give
a total fault clearance time as specified in the respective IEC
Standards or by requirements of transient stability.
v. Substation secondary or back up protection will be required to
withstand, without tripping, the loading incurred during clearance of
a fault by a breaker fail protection on the National Transmission
System. Back-up protections in the substation and Transmission
System shall be coordinated to provide discrimination.
vi. Circuit breakers provided at the Points of Connection between the
Code Participants/User's substation and the Transmission System
shall be provided with breaker fail protection. In the event the
breaker-failed to operate, the breaker-fail protection will initiate
tripping of all the electrically adjacent circuit breakers within the
time limits specified in the respective IEC Standards or by
requirements of transient stability.
vii. The following protection shall be provided at the substation:
• Bus bar protection
• Transformer protection
• Transmission line protection
• Lightning protection
viii. The target performance for the system fault dependability index
shall not be less than 99%. This is a measure of the ability of the
protection system to initiate successful tripping of circuit breakers
that are associated with the fault on the System.
e. Fault Recording Equipment
Equipment for recording fault condition and sequence of events shall be

provided by the Code Participant/User at the Points of Connection. The
recording equipment shall record a snapshot of the voltages and current during
the fault, and sequence of events for evaluation and analysis of the fault. The
fault recording equipment shall have facilities for the information via SCADA to
f. SCADA
CC 294
The Users shall provide a Remote Terminal Unit (RTU) at the Points of
Connection to monitor and control apparatus at the substation. At the
Generator, a RTU shall be provided for monitoring and control (dispatch) of the
Generators. The Users shall provide the communication link to the nearest
communication node in the Transmission system communication system for
RTU communication with the System Operator SCADA System. The RTU shall
have sufficient number of input and output points; and shall be fully compatible
with the System Operator SCADA system. In addition, RTU provided by the
Generator shall have facility of dispatching and loading the Generator from the
System Operator Control Centre. The communication link shall be fully
compatible with the System Operator communication system.
g. Time Clock Synchronization
Time clock in protection devices, recording equipment and SCADA shall have
facilities for synchronizing time with geostationary positioning satellite (GPS),
according to 9.5.1. The User at the Points of Connection shall provide the
required receiving and signal distribution equipment.
h. Testing, Calibration and Maintenance
The System Operator shall carry out a thorough review of the entire protection
system in their System and at the Points of Connection periodically.
Adjustments or changes in relay settings shall be performed due to changes in

the characteristics of the National Transmission System. In addition, periodic
testing, calibration and maintenance of the protection system for the National
Transmission System and Points of Connection shall be performed by the
System Operator.
The System Operator shall provide testing facility, test vehicle and test
instruments for field and laboratory for the purpose of testing, calibration and
maintenance of protection equipment. Cost of providing this service to Code
Participants/ User shall be included in the tariff.
i. Substation direct current check
All Code Participants/Users shall co-operate with the System Operator in the
scheduling and performance of testing and periodic checks of the readiness and
adequacy of direct current systems and facilities in their substations.
j. Testing Frequency and Calibration
Code Participants shall provide on an annual basis a schedule for testing for
substation facilities in its substations. The System Operator shall have the right
to require additional testing, and to request recalibration of testing equipment.
k. Testing Equipment Ownership
Code Participants shall own and maintain, or contract with qualified testing
companies, for the testing equipment required to perform tests.
l. System Operator Right to Inspect
The System Operator shall have the right to inspect substations and
transmission lines that are connected to the Transmission System, and which
are owned by DISCOs, BPCs, SPTLs or any other Code Participant.
PMC 15.1 Control and switching coordination
a. General
For the purpose of connecting and disconnecting a Generator and User's

substation from the Transmission System, it is essential that the
CC 295
necessary equipment be provided. This equipment shall include, but not
limited to the following:
i. In conjunction with the protection system, circuit breakers shall

be provided at the Point of Connection between the Code
Participants/User and the Transmission System. The circuit
breaker shall have the proper voltage ratings, short circuit
current rating and continuous current rating. Rating shall be
submitted to the System Operator for approval.
ii. Control panels for circuit breakers, disconnecting switches and
protection system shall be provided at the Points of
Connection. SCADA connections for monitoring and control of
circuit breakers, disconnecting switches, metering and
protection devices.
iii. Disconnecting switches shall be provided for isolating circuit
breaker for maintenance. Disconnecting switches shall be no-
load break type and have the same voltage, continuous
current and fault closing current capability as the circuit
breaker.
iv. Disconnecting switches shall be provided for isolating
transformer in the substation for maintenance. Disconnecting
switches shall have wiper to prevent arcing when energizing
the transformer. Disconnecting switches shall be no-load
break type and have the same voltage, continuous current
and fault closing current capability as the circuit breaker.
v. Grounding switches shall be furnished to ground the bus bars
and transmission line for maintenance.
vi. Disconnecting and grounding switches shall be motor-operated
to permit remote operation and interlocking with other
switching devices. Control and electrical interlock for
disconnecting and grounding switches shall be provided in
the control panel. Control shall have interface with SCADA for
remote control and monitoring of the disconnecting and
grounding switches.
b. Switching Procedures
All switching activities performed at the Points of Connection shall be

performed under the direction of the System Operator. All other
switching activities in the Code Participant/Users system shall be
coordinated with the System Operator. Proper communication and
tagging procedure shall be observed to prevent accidents and damage
to equipment involved in the switching operation.
c. Testing and Maintenance of Control Facilities
Control and switching shall be scheduled periodically for testing and

maintenance. Adjustments in protection system and control shall be
made at this time if necessary. Equipment found to be defective would
be repaired or replaced, accordingly. Testing and maintenance shall be
coordinated with The System Operator. Tests, calibration, repair and
replacement of equipment shall be recorded and distributed to all
concerned parties.
PMC 16 Protection Of Power System Equipment
PMC 16.1 Introduction
CC 296
Power system security shall depend greatly on the design of the protection
system, as well as, proper coordination with the protective relay systems and
settings in the User/Code Participant's Systems. As a minimum, a primary
protection scheme and a back-up protection scheme shall be provided for each
User/Code Participant's System. Code Participants/User shall provide protection
systems for the following:
(a) 220 kV , 500 kV and higher voltage levels grid sub-station bus bars
(b) 220 kV , 500 kV and higher voltage levels transmission lines
(c)Transformers
(d) Generators
(e) Circuit breakers
(f) <220 kV distribution company substations, and BPC facilities where
applicable
(g) <220 kV transmission lines
(h) Grid station auxiliary systems
PMC 16.2 Types of Protection
The following protective relaying schemes shall be provided for the following
sub-systems:
(a) 220 kV, 500 kV and higher voltage levels sub-station bus bars
i. Bus differential relaying
ii. Lightning protection by means of surge arrestors
iii. Additional protection for bus bars if needed
(b) 220 kV, 500 kV and higher voltage levels Transmission Lines
i. Distance protection Set-I, alternatively Differential protection SET-I
ii. Distance protection Set-II, alternatively Differential protection SET-II
iii. Transfer trip including communication schemes
iv. Line over current and earth fault protection
v. Line auto re-closing scheme
(c) 1100/500 kV, 765/500 kV, 500/220 kV AND 220/132 kV Transformers

i. Transformer differential protection
ii. Ground protection
iii. Sudden pressure relays-Bucholtz protection
iv. Temperature protection
v. Under/over voltage protection
vi. Over current protections
vii. Over fluxing protection
viii. Over load protection
ix. Tertiary overcurrent relay
x. REF protection
(d) Generators
i. Generator differential protection
ii. Generator under impedance protection
iii. Over current protection
iv. Over/under voltage protection
v. Loss of excitation protection
vi. Ground protection
vii. Over/under frequency protection
(e) Circuit Breakers

i. Breaker-fail protection
ii. Transfer trip protection
(f) 132 kV DISCO, Provincial, SPTLs interface substations
CC 297
i. Bus differential protection
ii. Transformer differential protection, Overcurrent protection
iii. Over and under voltage protection
iv. Breaker failure protection, Distance protection
v. Ground fault protection
vi. Transfer trip protection
vii. Over/under frequency protection, Auto re-closing
The System Operator shall install cross-tripping schemes in the eventuality of

loss of a particular Generator or Power Plant or plant and/or transmission
facility utilizing over/under frequency or voltage protection to protect System
from Total or Partial Collapse.
PMC 16.3 Instrument Transformers
Current Transformers (CTs) and Potential Transformers (PTs) shall be furnished

for the protection systems. CTs and PTs shall have the accuracy, ratio and
burden ratings required to operate the protective relays. Instrument
transformer for protective relaying shall not be shared with revenue metering
equipment. Likewise, instrument transformers for revenue metering shall not
be shared by protective relaying equipment.
PMC 16.4 Shunt Reactor Protection
The shunt reactors shall be protected from internal as well as external faults.
Circuit breakers may be provided for shunt reactors to allow for disconnection
of the shunt reactor if an internal fault occurs. If circuit breakers are not
provided for each reactor then protective relaying on shunt reactors shall be
used to trip associated line circuit breakers. Isolation switch shall be provided
to allow isolation of shunt reactor and circuit breakers for maintenance. The
following relays shall be provided for shunt reactor protection as a minimum:
(a) Differential protection

(b) Impedance protection Sudden Pressure Relays - Bucholtz protection
(c) Lightning protection by means of surge arrestors
Protection settings shall be coordinated with the line and substation protection
to prevent inadvertent and unwanted operations of protective protection.
PMC 16.5 Relay Coordination
Protective relays in the various sub-systems of the national power grid system
must be coordinated to prevent unwanted tripping. Proper coordination of
protection systems of the various sub-systems will enhance the security and
safe operation of the system.
To facilitate proper protective relay coordination, relay coordination software

shall be used by System Operator. Relay coordination should be checked and
updated each time a User/Code Participant's system characteristics are
changed, but in any case, at least every five years.
Any changes in the User/Code Participant's system that affects the operation
of the power system must be communicated to the System Operator
immediately. The System Operator shall evaluate the impact of the changes to
the protection of the power system, and initiate the necessary adjustments in
the operation and/or changes in protective relay settings.
PMC 16.6 Single Pole Tripping
The line relaying system shall be arranged to allow for single pole tripping of
selected 220 kV , 500 kV and higher volage transmission lines, in case of
single phase to earth fault. One-shot re-closing of the tripped line shall be
CC 298
allowed according to studies designed to establish the best re-closing time. If
the tripped phase fails to re-close, all three phases will be tripped accordingly.
PMC 16.7 Relay Testing and Maintenance
Periodic testing of all protective relays shall be performed by System Operator

to ensure that all protective relays are in good operating condition, and are set
properly. Protection devises found defective or with substandard design during
the test must be repaired or replaced, accordingly. Circuit breakers and
control circuits shall be tested periodically, and if parts are found to be
defective or deficient, they should be repaired or replaced.
Protection devises in the User/Code Participant's System shall be tested and

calibrated annually to ensure that they are in good operating condition; and
that the relay settings are correct. User/Code Participants may perform testing
and maintenance of their protective relay under supervision of System
Operator, or request System Operator to perform testing and setting of their
relays for a fee.
All testing and maintenance performed on the protection and control

equipment, including those of the User/Code Participants, shall be recorded
and a copy submitted to the System Operator for review and archiving. All test
and maintenance records shall be kept for a period of 5 years.
End of PMC
CC 299
DATA REGISTRATION CODE
CONTENTS
DCR 1 INTRODUCTION, OBJECTIVE & SCOPE............................................................. 303
DCR 2 The Scope of this Code applies to Users who in this DRC means:.....................303
DCR 3 DATA CATEGORIES AND STAGES IN REGISTRATION......................................... 303
DCR 4 PROCEDURES AND RESPONSIBILITIES............................................................ 304
DCR 5 DATA TO BE REGISTERED.............................................................................. 305
SCHEDULE 1- DATA REGISTRATION CODE-GENERATING UNIT AND POWER STATION

TECHNICAL DATA...................................................................................................... 309
SCHEDULE 2-DATA REGISTRATION CODE- GENERATION PLANNING PARAMETERS,

RESPONSE CAPABILITY DATA AND SDC1 DATA........................................................... 314
SCHEDULE 3- DATA REGISTRATION CODE- GENERATING UNIT/POWER STATION

EQUIPMENT/INTERCONNECTOR OUTAGES................................................................... 323
SCHEDULE 4- DATA REGISTRATION CODE- GENERATOR OUTPUT/LOADING DATA

AND ENERGY SALES DATA......................................................................................... 328
SCHEDULE 5- DATA REGISTRATION CODE USERS SYSTEM DATA..................................329
SCHEDULE 6- DATA REGISTRATION CODE- LOAD CHARACTERISTICS AT GRID

SUPPLY POINTS........................................................................................................ 332
SCHEDULE 7-DATA REGISTRATION CODE DEMAND CONTROL AND GENERAL DATA-

PART 1 - DEMAND CONTROL DATA............................................................................. 333
SCHEDULE 8- DATA REGISTRATION CODE DATA SUPPLIED BY THE SO TO USERS..........335
CC 300
DATA REGISTRATION CODE
DCR 1 INTRODUCTION, OBJECTIVE & SCOPE
DCR 1.1 The Data Registration Code (DRC) presents a unified listing of all data required by
System Operator from Users and by Users from System Operator, from time to time
under the Grid Code. The data which is specified in each section of the Grid Code
is listed and gathered here in the DRC. Where there is any inconsistency in the data
requirements under any particular sub-code of the Grid Code, the provisions of the
Data Registration Code for that particular sub-code of the Grid Code shall
prevail.
DCR 1.2 The DRC identifies the sub-code of the Grid Code under which each item of data is
required.
DCR 1.3 The sub-code under which any item of data is required specifies procedures and
timings for the supply of such data, for routine updating, and for recording
temporary or permanent changes to that data. All timetables for the provision of
data are repeated in the DRC.
DCR 1.4 Various sub-codes of the Grid Code also specify information which the Users shall
receive from System Operator. This information is summarised in a single Schedule
in the DRC (Schedule 1-9).
DCR 1.5 The objective of the DRC is to list and collate all the data to be provided by each
category of User to NTDC under the Grid Code, and to list all the data to be
provided by NTDC to each category of User under the Grid Code.
DCR 2 The Scope of this Code applies to Users who in this DRC means:
x) NTDC;
y) All Generators connected at the Transmission system
z) Generators with capacity greater than 10 MW;
aa) DISCOs;
bb) Transmission-connected Consumers; and
cc) Externally Connected Consumers/Parties, like
27. Interconnector Operators & including HVDC-links
28. Aggregators
DCR 3 DATA CATEGORIES AND STAGES IN REGISTRATION
DCR 3.1 Within the DRC each data item is allocated to one of the following four categories
(DRC 2.2 & DRC 2.3, DRC 2.4, DRC 2.5, DRC 2.6).
(b) Standard Planning Data (SPD in PC)

CC 301
(c) Detailed Planning Data (DPD in PC)
(d) Operational Data (in OC)
(e) Scheduling and Dispatch Code Data (in SDC)
(f) Connection Code Data (in CC)
DCR 3.2 Standard Planning Data (SPD)-PC data
DCR 3.2.1 The Standard Planning Data listed and gathered in this DRC is that data listed in
Part 1 of the Appendix A to the Planning Code.
DCR 3.2.2 Standard Planning Data shall be provided to NTDC in accordance with PC 3 and
PC.A.1 – PC.A.4 of Appendix A of the Planning Code.
DCR 3.3 Detailed Planning Data (SPD)-PC data
DCR 3.3.1 The Detailed Planning Data listed and gathered in this DRC is that data listed in Part
2 of the Appendix A to the Planning Code.
DCR 3.3.2 Detailed Planning Data shall be provided to NTDC in accordance with PC 3 and
PC.A.5 of Appendix A of Planning Code.
DCR 3.4 Operational Data-OC data
DCR 3.4.1 Operational Data is data, which is required by the Operation Codes. Within the DRC,
Operational Data is sub-categorised according to the Code under which it is required
namely, OC X, OC XX, OC XXX….
DCR 3.4.2 Operational Data is to be supplied in accordance with timetables set down in the
relevant Operational Codes.
DCR 3.5 Scheduling and Dispatch Code Data (SDC data)
This data must be supplied in accordance with Schedule and Despatch Codes and
Appendices attached with Scheduling and Dispatch Code of the Grid Code, SDC X,
XX, XXX
DCR 3.6 Connection Code Data (CC data)
This data is to be supplied in accordance with the Connection code of the Grid
Code, CC X, CCXX
DCR 4 PROCEDURES AND RESPONSIBILITIES
DCR 4.1 Responsibility for Submission and Updating of Data
In accordance with the provisions of the various sub-codes of the Grid Code, each
User must submit data as summarised in DRC 4 and listed and gathered in the
schedules attached with each sub-code.
DCR 4.2 Methods of submitting data
DCR 4.2.1 Wherever possible the data Schedules to the DRC are structured to serve as
standard formats for the data submission and such format must be used for the
written submission of data to System Operator.
DCR 4.2.2 Data must be submitted to the System Operator, National Power Control Centre
(NPCC) or to such other department or address as System Operator may advise
from time to time. The name of the person on the behalf of the User who is
submitting each schedule of data must be included.
CC 302
DCR 4.2.3 Where a computer data link exists between a User and System Operator, data may
be submitted via this link. NTDC shall, in this situation, provide computer files for
completion by the User containing all the data in the corresponding DRC Schedule.
DCR 4.2.4 Other modes of data transfer, through CD and other electronic means of data
transfer such as magnetic tape, may be utilised if NTDC gives its prior written
consent.
DCR 4.3 Changes to user’s data
DCR 4.3.1 Whenever a User becomes aware of a change to an item of data which is registered
with System Operator, the User must notify System Operator in accordance with
each sub-code of the Grid Code. The method and timing of the notification to
System Operator is set out in each sub-code of the Grid Code.
DCR 4.4 Data not supplied
DCR 4.4.1 User and System Operator are obliged to supply data as se out in the individual
sub-codes of the Grid Code and repeated in the DRC. If a User fails to supply data
when required by any sub-code of the Grid Code, System Operator shall make an
estimation (typical values) of such data if and when, in the System Operator view, it
is necessary to do so. If System Operator fails to supply data when required by any
sub-code of the Grid Code, the User to whom that data ought to have been
supplied, shall estimate (typical values) of such data if and when, in that User's
view, it is necessary to do so. Such estimates shall, in each case, be based upon
data supplied previously for the same plant and apparatus or upon such other
information as System Operator or that User, as the case may be, deems
appropriate.
DCR 4.4.2 System Operator shall advise a User in writing of any estimated data it intends to
use pursuant to DRC 3.4.1 relating directly to that User's facility, plant, and
apparatus in the event of data not being supplied.
DCR 4.4.3 A User shall advise System Operator in writing of any estimated data it intends to
use pursuant to DRC 3.4.1 in the event of data not being supplied.
DCR 4.4.4 In the event the required data is consistently not supplied or is incomplete or in-
accurate by the User, the System Operator shall refer the matter to the "Review
Panel", which shall issue necessary instructions to the defaulted party in writing.
DCR 4.4.5 Failure to obtain the required data within the specified timeframes from the
defaulted party, the System Operator shall consider the matter as a violation of the
Grid Code provisions. Suitable measures regarding Grid Code non-compliance are
covered in CM 14 of this Grid Code.
DCR 5 DATA TO BE REGISTERED
DCR 5.1 Schedules 1 to 9 attached cover the following data areas.
DCR 5.1.1 SCHEDULE 1 - GENERATING UNIT TECHNICAL DATA. (Directly or Indirectly

Connected to NTDC System, Centrally Dispatched such as connected to the NTDC
system or 132 kV Transmission System of Distribution, Provincial & SPTLs
companies and subject to central dispatch).
Comprising Generating Unit fixed electrical parameters (as covered in respective

appendices of the following sub-codes [(OC 4 Appendix 4, Appendix 5, OC 5
Appendix 1, OC 6 Appendix 1, OC 7 Appendix 1); (PC, Part 1 and 2 of Appendix A);
and (Appendix 1 of CC 8.3. and CC 8.5)] and relevant Addenda 1, 2 & 3 for Solar,
Wind and ESU
CC 303
DCR 5.1.2 SCHEDULE 2 - GENERATION PLANNING PARAMETERS AND GENERATION OFFER
DATA. (Directly or Indirectly Connected to NTDC System, Centrally Dispatched such
as connected to the NTDC system or 132 kV Transmission System of Distribution,
Provincial & SPTLs companies, Demand Side Units, and subject to central
dispatch, Interconnectors subject to Contractual agreement and CTBCM_DR., and
Solar, Wind and ESU and relevant Addenda 1, 2 & 3 for.
Comprising the Generating Plant parameters as connected to the NTDC system or

132 kV Transmission System of Distribution, Provincial & SPTLs companies,
Demand Side Units, and subject to central dispatch, Interconnectors subject to
Contractual agreement and CTBCM_DR., and Solar, Wind and ESU and relevant
Addenda 1, 2 & 3, required for Operational Planning studies and certain data
required under Scheduling and Dispatch Code (as covered in Appendix 5 of OC 4).
DCR 5.1.3 SCHEDULE 3 - GENERATING PLANT OUTAGE PROGRAMMES, Directly or Indirectly

connected to the NTDC system or 132 kV Transmission System of Distribution,
Provincial & SPTLs companies, Demand Side Units, and subject to central
dispatch, Interconnectors Outage Programmes subject to Contractual agreement
and CTBCM_DR., and Solar, Wind and ESU Outage Programmes, OUTPUT USABLE
AND INFLEXIBILITY INFORMATION (OC 4 - Appendix 1, 2).
Comprising Generation Outage Planning of the Generating Units, Demand Side

units subject to central dispatch, Interconnectors Outage Planning, Output Usable
and inflexibility information at timescales down to the daily Availability Declaration.
Also contract information in Contractual Agreement and Technical Code need to
be provided where External Interconnections and Interconnectors Operators are
involved.
DCR 5.1.4 SCHEDULE 4 - INDEPENDENT GENERATING PLANT OUTPUT FORECASTS (Indirectly

Connected to NTDC system, not subject to Central Dispatch such as embedded
generation and SPPs) and subject to relevant Addenda 1, 2 & 3, as the case may be.
Output predictions for Power Stations not subject to Central Despatch (as covered in
Appendix 1 and 2 of OC 4) and subject to relevant Addenda 1, 2 & 3, as the case
may be.
DCR 5.1.5 SCHEDULE 5 - USER'S SYSTEM DATA (Directly connected to NTDC System
Transmission-connected Consumers, Distribution Licensees. and other Externally-
connected Consumers).
Comprising electrical parameters relating to facilities connected to the NTDC

Transmission System (as covered in Part 1 of Appendix A of Planning Code).
DCR 5.1.6 SCHEDULE 6 - USERS OUTAGE INFORMATION
Comprising the information required by NTDC for outages on the Users System
(Directly or Indirectly Connected lo NTDC System). including outages at Power
Plants (Indirectly Connected to NTDC System and not subject to Central Dispatch).
DCR 5.1.7 SCHEDULE 7 - LOAD CHARACTERISTICS (Directly or Indirectly Connected to NTDC

System).
Comprising the estimated parameters of load groups in respect of, for example,
harmonic content and response to frequency (as covered PC.A.4.8 of Appendix A of
Planning Code) and the ESU charging mode.
DCR 5.1.8 SCHEDULE 8 - CONNECTION POINT DEMAND AND ACTIVE ENERGY DATA OF USERS
DIRECTLY OR INDIRECTLY CONNECTED TO NTDC SYSTEM AND GENERATION
SUMMARY (as covered in PC.A.4 - Part 1, of the Appendix A of Planning Code).
Comprising information relating to Demand and Active Energy taken from the NTDC
Transmission System and a summary of the Independent and Consumer Generating
CC 304
Plant connected to the Connection Point. (Indirectly Connected to NTDC System,
and not subject to Central Dispatch) and the ESU charging mode.
DCR 5.1.9 SCHEDULE 8B is, DEMAND CONTROL AND GENERAL DATA. Comprising information
relating to Demand Control of Users Directly or Indirectly connected to the NTDC
system or 132 kV Transmission System of Distribution, Provincial & SPTLs
companies, including requirements for additional data for System operations
purposes.
DCR 5.1.10 SCHEDULE 9 - DATA SUPPLIED BY NTDC TO USERS (as covered in PC.A.4.3, PC.A.4.6
of Part 1 of Appendix 1 of the Planning Code; Appendix 3 and 3A, of OC 4, OC 5.A.8
of OC 5, Appendix 1 of OC 6, Appendix 1 of OC 7, Appendix 1-3 of OC 9; and CC 6.1,
CC 6.2, CC 8.7, CC 8.8, CC 8.10.1, CC 8.12.4, CC 8.13.2, CC 8.17 of Appendix 1 of
Connection Code).
The Schedules applicable to each class of User are as follows:
SR. DESCRIPTION SUBJECT TO SCHEDULE

NO. DISPATCH
(Directly Connected)
i Generating Plants directly connected SD 1,2,3,9

to NTDC system and subject to
Central Dispatch.
ii Generating Plants connected to

132/66kV system of Distribution
Companies subject to Central
Dispatch.
(Indirectly Connected)
i Generators indirectly connected, and NSD 1,2,4,6,9

not subject to Central Dispatch.
Users (Directly Connected)
i Distribution Companies – 5,6,7,8,9
ii Consumers directly connected to NTDC – 5,6,7,8,9

system.
iii Externally-Connected Parties – 4,5,6,8,9
Users (Indirectly Connected)
i BPCs connected to DISCOs distribution – 6,7,8,9

system and indirectly connected to
NTDC system.
ii Externally-Connected Consumers – 6,7,8,9
Notes:
1. Distribution, Provincial & SPTLs Companies and Users with a User
System directly connected to the NTDC Transmission System must
provide data relating to Small Power Producers Plant/Embedded
Generators and/or Customer Generating Plant within their Systems
when such data is requested by NTDC pursuant to PC.A.3 or PC.A.5.
2. The data in Schedules 1 and 3 need not be supplied in relation to Small
CC 305
Power Producers (SPPs) connected to the System of a User at a voltage
level below the voltage level directly connected to the NTDC
Transmission System except in connection with a Master Connection
and Use of System Agreement or unless specifically requested by NTDC.
DCR 5.2 As stated in DRC1, the data listed in the Schedules to this DRC are required to be
submitted by Users to the SO in other parts of the Grid Code and consequently the
schedules should reflect accurately the requirements of other parts of the Code relating
to the submission of data.
DCR 5.3 If at any time the SO considers that the Schedules do not so reflect the operative
provisions relating to the submission of data, the SO may, by notice in writing to all
affected Users amend the Schedules to this DRC.
DCR 5.4 The SO may also vary the format of the Schedules in this way. No changes may be
made in accordance with this DRC5.3 which would affect the substantive obligations of
Users. Changes of this latter nature can only be achieved by means of the usual
procedure for Grid Code changes and will require the approval of the Authority.
DCR 5.5 Confidentiality Obligations
Each Code Participant must use all reasonable endeavours to keep any
information confidential which comes into the possession or control of that Code
Participant or of which the Code Participant becomes aware of. A Code Participant:
a) must not disclose confidential information to any person except as permitted

by the Grid Code;
b) must only use or reproduce confidential information for the purpose for which
it was disclosed or another purpose contemplated by the Grid Code;
c) must not permit unauthorized persons to have access to confidential

information.
Each Code Participant must use all reasonable endeavours:
a) to prevent unauthorized access to confidential information which is in the

possession or control of that Code Participant; and
b) to ensure that any person to whom it discloses confidential information

observes the provisions of Grid Code;
c) The Officers of the System Operator, Distribution, Provincial & SPTLs

companies, and other Authorised Electricity Operators and all other Users
participating in Transmission Service Pricing must not be involved in or
associated in any manner with Competitive Power Trading activities of any
other Code Participant.
End of DCR
CC 306
SCHEDULE 1- DATA REGISTRATION CODE-GENERATING UNIT AND POWER STATION
TECHNICAL DATA
DATA DESCRIPTION UNITS DATA GENERATING UNIT OR POWER STATION DATA

CAT.
G1 G2 G3 G4 G5 G6 G7 STN
GENERAL POWER STATION DATA

- SPD - - - - - - -
Point of connection to the NTDC System in
terms of geographical and electrical
location and System voltage
Capacity of Power Station in MW sent MW SPD - - - - - - -
out for R.C., Min. Gen. (assumed to be
zero in the case of SOLAR, WIND & ESUs
unless a different value is notified by the
User) and, where relevant Max. Gen.
In the case of Wind Farm Power SPD
Stations, a diagram that shows for the
Wind Farm Power Station wind
speed and direction against electrical
output in MW, in “rose” format.
In the case of SOLAR, & ESU, an
equivalent diagram relating to the input
resource of that SOLAR, & ESU.
Maximum auxiliary Demand (Active MW SPD - - - - - - -
Power and Reactive
Power) Mvar SPD - - - - - - -
Where Generating Units form part of a SPD

User's System, the number of such Units
together with their total capacity. If
required by the SO, details of the
Generating Units together with their
energy output profile.
Operating regime of Generating Units not SPD
subject to Central Dispatch (e.g.
continuous, intermittent, peak lopping).
SPD
-
GENERAL GENERATING UNIT DATA Prime SPD
mover type MVA SPD
Generating Unit type KV
-
Generating Unit rating and terminal
voltage
Generating Unit rated power factor SPD -
Registered Capacity sent out MW SPD -
Max.Gen. and Min.Gen. capability sent MW SPD -

out
Reactive Power capability (both Mvar SPD -
leading and lagging) at the lower
voltage terminals of the Generator
Transformer for Max.Gen., normal
Full Load and normal minimum Load.
CC 307
Maximum Auxiliary Demand MW SPD
Mvar
Inertia constant MW SPD

sec
MVA
ABBREVIATIONS:
SPD = Standard Planning Data DPD = Detailed Planning Data
Min Gen = Minimum Generation Max Gen = Maximum Generation
% on MVA = & on Rated MVA RC = Registered Capacity
% on 100 = % on 100 MVA OC1,SDC1,etc= Grid Code for which data is required
DATA DESCRIPTION UNITS DATA GENERATING UNIT OR POWER

CAT STATION DATA
Short circuit ratio
SPD -
SPD
Direct axis transient reactance % on
-
MVA
SPD
SPD
Direct axis sub-transient time constant S -
-
Generator Transformer rated MVA, positive sequence MVA SPD
reactance and tap change range % on SPD
MVA
+%/-
% SPD
Sustained Load Diagram Diagram
-
In relation to the generators comprised within a
SOLAR, WIND & ESU, such General Generating
Unit Data equivalent to that listed above as the
SO shall reasonably require.
A list of the CCGT Modules in the CCGT List

Installation identifying each CCGT Module, and
the CCGT Installation of which it forms part
unambiguously, together with other relevant
information.
Auxiliary Demand
The normal Generating Unit-supplied auxiliary Load MW DPD -
for each Generating Unit at rated MW output MW DPD
The Power Station auxiliary Load, if any,

additional to the Generating Unit supplied
auxiliary Load where the Power Station auxiliary
Load is supplied from the NTDC System
Generating Unit
parameters kV DPD -
MVA DPD
Rated terminal voltage
MW DPD -
MW DPD
Rated MVA
DPD -
Rated MW
DPD
Min.Gen. % on -
Short circuit ratio MVA
Direct axis synchronous reactance
-
CC 308
-
Direct axis transient reactance % on DPD -
MVA
Direct axis sub-transient reactance % on DPD -
MVA
Direct axis transient time constant S DPD -
Direct axis sub-transient time constant S DPD -
Quadrature axis synchronous reactance % on DPD
-
MVA
Quadrature axis transient reactance % on DPD
-
MVA
Quadrature axis sub-transient reactance % on DPD
-
MVA
Quadrature axis transient time constant S DPD
-
Quadrature axis sub-transient time constant S DPD
-
Stator time constant S DPD
-
Stator resistance DPD
-
Stator leakage reactance % on DPD
-
MVA
Turbogenerator inertia constant, or, for generators MWsec/ DPD
-
comprised within a SOLAR, WIND & ESU, Plant inertia MVA
constant
Other than for generators comprised within a SOLAR, A DPD
-
WIND & ESU, rated field current
Other than for generators comprised within a SOLAR, A DPD
-
WIND & ESU, field current (amps) open circuit
saturation curve for Generating Unit terminal voltages
ranged from 50% to 120% of rated value in 10% steps
as derived from appropriate manufacturers' certificates
Parameters for Generating Unit Step-Up Transformers
Rated MVA MVA DPD

-
Voltage ratio DPD
-
Positive sequence reactance (at max., min. & nominal % on DPD
-
tap) MVA
Positive sequence resistance (at max., min. & nominal % on DPD
-
tap) MVA
Zero phase sequence reactance % on DPD
-
MVA
Tap changer range +%/ DPD
-
-%
Tap changer step size % DPD
-
Tap changer type: on Load or off circuit on/off DPD
-
Power Station Transformer Parameters
Rated MVA MVA DPD

-
Voltage ratio DPD
-
Zero sequence reactance as seen from the higher % on DPD
-
voltage side MVA
CC 309
Excitation control system parameters (not for SOLAR,
WIND & ESUs)
DC gain of excitation loop DPD
-
Rated field voltage DPD
-
Maximum field voltage DPD
-
Minimum Field Voltage DPD
Max. rate of change of field voltage (rising) V/sec DPD

-
Max. rate of change of field voltage (falling) V/sec DPD
-
Details of excitation loop described in block diagram Diagram DPD
-
form showing transfer functions of individual elements
Dynamic characteristics of over-excitation limiter DPD
-
Dynamic characteristics of under-excitation limiter DPD
-
Governor Parameters (for Reheat Steam Turbine Units)
H.P. governor average gain MW/Hz DPD

-
Speeder motor setting range Hz DPD
-
H.P. governor valve time constant S DPD
-
H.P. governor valve opening limits DPD
-
H.P. governor valve rate limits DPD
-
Reheater time constant (active energy stored in S DPD
-
reheater)
IP governor average gain MW/Hz DPD
-
IP governor setting range Hz DPD
-
IP governor valve time constant S DPD
-
IP governor valve opening limits DPD
-
IP governor valve rate limits DPD
-
Details of acceleration sensitive elements in HP and IP DPD
-
governor loop
Governor block diagram showing transfer functions of Diagram DPD
-
individual elements
Governor Parameters (for Non-Reheat Steam Turbine
Units and Gas Turbine Units
Governor average gain MW/Hz DPD
-
Speeder motor setting range DPD
-
Time constant of steam or fuel governor valve DPD
-
Governor value opening limits DPD
Governor valve rate limits DPD

-
Time constant of turbine S DPD
-
Governor block diagram Diagram DPD
-
CC 310
Governor parameters (for SOLAR, WIND & ESUs)
Generator torque/speed controller(s) (if any) DPD
Generator blade angle controller(s) (if any) DPD
Generator power limitation function(s) (if any) DPD
Plant Flexibility Performance
Rate of Loading following weekend shutdown MW/m DPD

(Generating Unit and Power Station)
Rate of Loading following overnight shutdown MW/m DPD
(Generating Unit and Power Station)
Block Load following Synchronising, or, in the case of MW DPD
SOLAR, WIND & ESUs, generating whilst connected to
the NTDC System
Rate of Deloading from normal rated MW MW/m DPD
Regulating range MW DPD
Load rejection capability while still Synchronised, or, in MW DPD

the case of SOLAR, WIND & ESUs, generating whilst still
connected to the NTDC System and generating, and
able to supply Load
NOTE:
Users are referred to Schedule 5 which sets down data required for all Users directly connected to the
NTDC System, including Power Stations.
CC 311
SCHEDULE 2- DATA REGISTRATION CODE- GENERATION PLANNING PARAMETERS,
RESPONSE CAPABILITY DATA AND SDC1 DATA
Part 1 of this schedule contains the CDGU and Controllable SOLAR, WIND & ESU or Dispatchable
SOLAR, WIND & ESUs Generation Planning Parameters required by the SO to facilitate studies in
Operational Planning timescales. It also contains the response capability data for CDGUs.
Part 2 of this schedule contains the data required with respect to CDGUs, Pumped Storage Plant
Demand, Energy Storage Power Station Demand, Interconnectors, Interconnector Units,
Demand Side Units, Aggregated Generating Units and/or Controllable SOLAR, WIND & ESU to be
supplied by Users by Gate Closure pursuant to SDC1. Many of these parameters are the same as those
required in Part 1, but the data supplied under Part 1 will not be used for real time operation.
Power Station:
Part 1 - Generation Planning Parameters
DATA DESCRIPTION UNITS DATA GENERATING UNIT OR POWER STATION

CAT. DATA
Generation Planning Parameters for CDGUs
The minimum notice required to Mins OC2 -

Synchronise a Generating Unit from De-
synchronisation
The minimum time between Synchronising Mins OC2
different
Generating Units in a Power Station
The minimum block Load requirements on OC2
Synchronising
Maximum Generating Unit Loading rates
from
Synchronising for the following conditions:
hot MW/ OC2 -
min
Warm MW/ OC2 -

min
cold MW/ OC2 -

min
Minimum time off Load OC2
Maximum Generating Unit Deloading rates

for the following conditions:
Hot MW/ OC2 -

min
warm MW/ OC2 -

min
cold MW/ OC2 -

min
Maximum allowable starts per year:
hot OC2 -
warm OC2 -
cold OC2
CC 312
Generation Planning Parameters for
Controllable SOLAR, WIND & ESUs or
Dispatchable SOLAR, WIND & ESUs

The minimum time to connect/reconnect the OC2
Controllable SOLAR, WIND & ESU or
Dispatchable SOLAR, WIND & ESU (or part
thereof) to the NTDC System following a
Dispatch instruction
The minimum time to connect/reconnect the OC2
thereof) to the NTDC System automatically
following a trip of the Controllable SOLAR,
WIND & ESU or Dispatchable SOLAR, WIND &
ESU (or part thereof) that does not cause
damage to the Controllable SOLAR, WIND &
ESU or Dispatchable SOLAR, WIND & ESU (or
part thereof)
The maximum rate at which Load can be OC2
increased following connection of the
thereof) to the NTDC System
The minimum fault level or voltage at the OC2
Connection Point below which the Controllable
SOLAR, WIND & ESU or Dispatchable SOLAR,
WIND & ESU cannot be connected
Operating Reserve to Frequency change -
Operating Reserve to Frequency change to be

given in a tabular form, describing Primary
Operating Reserve, Secondary Operating
Reserve, Tertiary Operating Reserve band 1, Table
Tertiary Operating Reserve band 2 at different
levels of Load, ranging from Minimum OC3
Generation to Registered Capacity
%
Governor Droop Characteristics Governor
Droop
Unit Control Options %
OC3
%
Maximum Droop Normal Droop Minimum Droop
%
OC3
OC3
OC3
Part 2: Availability, Technical Parameters Data and other data required under SDC1
The following information is required daily by not later than Gate Closure to cover the next following
Trading Day in relation to each CDGU, Pumped Storage Plant Demand, Energy Storage Power
Station Demand, Interconnector, Interconnector Units (only in relation to paragraph 6 below),
Demand Side Unit, Aggregated Generating Unit and/or Controllable SOLAR, WIND & ESU. In so
far as the Availability data is not so submitted, the data to have been submitted in respect of the last
Imbalance Settlement Period of the current Trading Day
CC 313
will be deemed to have been resubmitted. Any further revisions to this data are required to be notified to
the SO when they become known.
1. Availability
Each User must notify the SO by means of an Availability Notice of the Availability of each of its
CDGUs (and in the case of a CCGT Installation, the CCGT Modules within it), Pumped Storage
Plant Demand, Energy Storage Power Station Demand, Interconnectors, Demand Side Units,
Aggregated Generating Units and/or Controllable SOLAR, WIND & ESU.
The Availability Notice shall state the Availability of the relevant CDGU for each Imbalance
Settlement Period in the following
Trading Day (subject to revision under SDC1.4.5.1 (a)).
In addition, Users other than Aggregators and Demand Side Unit Operators must submit an
Additional Grid Code Availability Notice under SDC1.4.2 by no later than Gate Closure each day.
The information contained in an Additional Grid Code Availability Notice broadly relates to a
CDGU’s different Availabilities depending on which fuel a CDGU is firing on (for a CDGU that is
capable of firing on different fuels), the Availability of each CCGT Module within a CCGT
Installation and to the various long-term constraints (such as fuel and emissions constraints) which
can affect the Availability of a CDGU. Technical Parameters
For each CDGU, Controllable SOLAR, WIND & ESU, Dispatchable SOLAR, WIND & ESU,
Demand Side Unit, Aggregated Generating Unit, Energy Storage Power Station Demand and
Pumped Storage Plant Demand, the Technical Parameters listed in the table set out in Appendix
A to SDC1 and copied below. The factors applicable to a particular Plant are indicated with a tick.
CC 314
Demand
Demand
Storage
WIND &
Control
SOLAR,
Pump
ESPS
ESU
Agg.
Gen
Technical Parameter CDGU DSU
- -
Hydr/ En
Demand
Thermal
Demand
Pump S
WIND &
SOLAR,
Indiv.
Sites
Agg.
Disp.
Site
Gen
Ltd
ESU
-
Block Load Cold     
Block Load Hot 
Block Load Warm 
Charging Capacity  
ESPS
Gen
Only
Cycle Efficiency   
ESPS
Gen
Only
Demand Side Unit  
=Notice
Deload Break Point     
Demand Side  
Unit MW
Availability
Demand Side Unit  
MW
Response Time
De-Loading Rate 1     
De-Loading Rate 2     
Dwell Time Up 1     
Dwell Time Down 1     
Dwell Time Up     
Trigger Point 1
Trigger Point 2
Trigger Point 3
Dwell Time Down     
Trigger
Point 1
Dwell Time     
Down
Trigger
Point 2
Dwell Time     
Down
Trigger
Point 3
CC 315
End Point of     
Start Up Period
Energy Limit 
Forecast    
Minimum ESPS
Output Gen
Profile Only
Forecast    
Minimum
Generation
Profile
Load Up Break     
Point Cold (1)
Load Up Break     
Point Cold (2)
Load Up Break 
Point Hot (1)
Load Up Break 
Point Hot (2)
Load Up Break 
Point Warm (1)
Load Up Break 
Point Warm (2)
Loading Rate Cold     
(1)
(2)
(3)
Loading Rate Hot 
(1)
(2)
(3)
Loading Rate Warm 
(1)
(2)
(3)
Max Ramp Down  
Rate (shall be a
number greater
than zero)
Max Ramp Up  
Rate (shall be
a number
greater than zero)
Maximum  
Charge ESPS
Capacity Gen
Only
Maximum Down  
Time
Maximum     
Generation /
Registered
Capacity
Maximum On Time     
CC 316
Maximum Storage 
Capacity
Minimum Charge  
Capacity ESPS
Gen
Only
Minimum Down  
Time
Minimum     
Generation
Minimum Off Time       
Minimum On Time     
Minimum Storage  
Capacity
Off to Generating 
Time
Off to Spin Pump 
Time
(Other relevant      
technical
parameters)
Pumping capacity  
Ramp Down Break      
Point 1
Point 2
Point 3
Point 4
Ramp Down Rate 1      
Ramp Up Break      
Point 1
Point 2
Point 3
Point 4
Ramp Up Rate 1      
Ramp Up Rate 2      
Ramp Up Rate 3      
Ramp Up Rate 4      
Ramp Up Rate 5      
Short Term     
Maximisation
Capability
Short Term     
Maximisation
Time
CC 317
Soak Time Cold (1)     
Soak Time Cold (2)     
Soak Time Hot (1) 
Soak Time Hot (2) 
Soak Time Trigger     
Point Cold (1)
Soak Time Trigger     
Point Cold (2)
Soak Time Trigger 
Point Hot (1)
Point Hot (2)
Point Warm (1)
Point Warm (2)
Soak Time Warm (1) 
Soak Time Warm (2) 
Spin Pump to 
Pumping Energy
Time
Synchronous     
Start-Up Time
Cold
Synchronous     
Start-Up Time
Hot
Synchronous 
Start-Up Time
Warm
Start of Restricted     
Range 1
End of Restricted     
Range 1
Start of Restricted     
Range 2
End of Restricted     
Range 2
Users should also refer to SDC1.4.5.2 for the submission of revised Technical Parameters data.
2. Additional Grid Code Characteristics
The following data are required to be submitted by each User, with the exception of Aggregators,
direct to the SO:
a. Individual CCGT Module data equivalent to the data required for a CCGT Installation. It
shall also show any revisions to the Technical Parameters for each of the CCGT Modules
within it.
b. In the case of a CDGU capable of firing on different fuels, an Additional Grid Code
Characteristics Notice in respect of any additional fuel for the CDGU, each containing the
information set out in the Technical Parameters for each fuel and each marked clearly to
indicate to which fuel it applies.
c. In the case of Interconnector Owners, Interconnector data, including but not
limited to the Availability of Interconnector Filters.
d. In relation to each Demand Side Unit, the Demand Profile and the Initial Demand
Reduction Time.
CC 318
e. Where there is a System Support Services Agreement in place, the System Support
Services which are Available.
f. The parameters listed in the table in Part 2 of Appendix A to SDC 1 and copied below, where
relevant to a User.
The table contained in Part 2 of Appendix A to SDC1 and referred to at paragraph 6 above is copied
below:
Variable Applies to
Time from initiation of a start to achieving CDGUs which are Open Cycle Gas Turbines or
Dispatched Load CCGTs
Governor Droop All CDGUs, except Aggregated Generating Units
Sustained Response Capability All CDGUs, except Aggregated Generating Units
Two shifting limitation (limitation on the All CDGUs, except Aggregated Generating Units
number of Start-ups per Trading Day)
The MW and Mvar capability limits within All CDGUs, except Aggregated Generating Units
which the CDGU is able to operate as shown
in the relevant Generator Performance
Chart
Maximum number of on Load cycles per 24 All CDGUs, except Aggregated Generating Units
hour period, together with the maximum Load
increases involved
^Maximum number of changes to the All CDGUs, except Aggregated Generating Units
Dispatched Fuel per 24 hour period
Maximum quantity of oil in “ready-use All CDGUs, except Aggregated Generating Units
tanks” and associated pipework
^Maximum number of changes to the All CDGUs, except Aggregated Generating Units
Designated Fuel per 24 hour period
^Minimum notice to change the All CDGUs, except Aggregated Generating Units
Designated Fuel.
Settings of the Unit Load Controller for each All CDGUs, except Aggregated Generating Units
CDGU for which a Unit Load Controller is
required under CCS1.5.5 of the SONI Grid
Code
Declared Maximisation Capacity All CDGUs, except Aggregated Generating Units
Time between De-Synchronising different All CDGUs, except Aggregated Generating Units
CDGUs in a Power Station which, in the case
of Coolkeeragh Power Station only, shall be
stated for both paired and single CDGUs.
Users should also refer to SDC1.4.5.2 for the submission of revised Additional Grid Code
Characteristics data.
3. Reserve capability
Each Generator and Generator Aggregator shall submit reserve capability data in accordance
with SDC1.4.4.3 and, in the case of PPA Generation, Appendix B to SDC1.
4. Other Relevant Data
For each Plant which has been declared Available in an Availability Notice (and, in the case of
a CCGT Installation, CCGT Modules within):
(i) any newly arisen special factors which in the reasonable opinion of the User may have
a material effect on the likely Output or Demand Reduction of such Plant (and, in
the case of a CCGT Installation, CCGT Modules therein) or, in the case of an
CC 319
Interconnector, the Availability of the Interconnector Filters; and
(ii) any temporary changes, and their likely duration, to the Registered Data of such Plant
(and, in the case of a CCGT Installation, CCGT Modules therein) (other than those
already notified under the foregoing provisions of this Part II of Schedule 2).
5. Commercial Offer Data
Each Generating Unit, Pumped Storage Generator (in respect of Pumped Storage Plant
Demand), Energy Storage Generator (in respect of Energy Storage Power Station
Demand), Interconnector User (in respect of an Interconnector Unit), Demand Side Unit
Operator and Generator Aggregator shall submit Commercial Offer Data to the SO (either
directly or by means of an Intermediary) by Schedule Day for the following Trading Day in
accordance with the CTCBM_DR. Specific requirements for Energy Limited Generating Units
and Pumped Storage Plants are listed in SDC1.4.4.5.
CC 320
SCHEDULE 3- DATA REGISTRATION CODE- GENERATING UNIT/POWER STATION
EQUIPMENT/INTERCONNECTOR OUTAGES
Power Station/Interconnector name .........................
Generating Unit number .......................................
Registered Capacity ............................................
PART 1 - GENERATING PLANT/POWER STATION EQUIPMENT/INTERCONNECTOR OUTAGE

PROGRAMMES
CDGU (AND/OR CCGT MODULE, AS PROVIDED IN UNITS TIME UPDATE DATA CAT.
OC2)/ CONTROLLABLE SOLAR, WIND & ESU/ COVERED TIME
DISPATCHABLE SOLAR, WIND & ESU/ POWER
STATION EQUIPMENT/ INTERCONNECTOR OUTAGE
PROGRAMMES
(Note: References to CCGT Installations include CCGT

Modules
as provided in OC2)
Indicative Term Operational Planning: Planning for years
4 to 7 ahead
Suggested Indicative Outage Programme containing: Year 7 By end OC2

March
(i) identity of the CDGUs (or, in the case of a CCGT

Installation, CCGT Module(s) therein), Controllable
SOLAR, WIND & ESUs, Dispatchable SOLAR, WIND
& ESU (or Generating Unit(s) therein) Power Station
Equipment and/or Interconnector concerned;
(ii) MW concerned (i.e. which will not be Available as a MW

result of the Outage and that which will still be
Available);
(iii) duration of Outage; weeks
(iv) preferred Start Date and Start Time; date/

time
(v) whether Flexible or Inflexible;
(vi) if Flexible:
(a) period by which Outage may be deferred; days
(b) period by which Outage may be days

advanced;
(vii) if the Outage is required to enable the Generator
or Interconnector Owner to comply with statutory
obligations and, in such case, the latest date by which
the Outage must be taken.
(Note: References to CCGT Installations include CCGT

Modules
as provided in OC2)
Long Term Operational Planning: Planning for years 2 & 3 Year 3 By end OC2
ahead March
Suggested Provisional Outage Programme containing:
SOLAR, WIND & ESUS or Dispatchable SOLAR, WIND
& ESUs (or Generating Unit(s) therein) Power Station
CC 321
Available);

(v) whether Flexible or Inflexible; time
(vi) if Flexible:
(b) period by which Outage may be advanced; days
(vii) if the Outage is required to enable the Generator or

Interconnector Owner to comply with statutory obligations
and, in such case, the latest date by which the Outage
must be taken.
(The TSO's response as detailed in OC2 Year 3 By end Sept. OC2)
(Generators' responses to changes suggested by the SO

Year 3 By end Oct. OC2)
and resolution of any disputes as set out in OC2
Up-dated suggested Provisional Outage Programme Year 2 By end March OC2
containing:
Installation, CCGT Module(s) therein),Controllable SOLAR,
WIND & ESUs or Dispatchable SOLAR, WIND & ESUs (or
Generating Unit(s) therein) Power Station Equipment
and/or Interconnector concerned;
result of the Outage and that which will still be Available);
(iv) preferred Start Date and Start Time; date/ time
(v) whether Flexible or Inflexible;
(vi) if Flexible:
(b) period by which Outage may be advanced. days
(vii) if the Outage is required to enable the Generator or
must be taken.
(the TSO’s response as detailed in OC2 Year 2 By end OC2)
Sept.
(Generators' and Interconnector Owner’s responses to the
Year 2 By end Oct OC2)
TSO's
changes and resolution of any disputes as set out in OC2
Medium Term Operational Planning: Planning for Year 1
ahead
Suggested Final Outage Programme containing: Year 1 By end March OC2
SOLAR, WIND & ESUs or Dispatchable SOLAR, WIND &
ESUs (or Generating Unit(s) therein) Power Station MW
(ii) MW concerned (i.e. which will not be Available as a

Available);
CC 322
time
(v)whether Flexible or Inflexible;
(vi)if Flexible:
(a) period by which Outage may be deferred;
(b)period by which Outage may

be advanced.
(vii) if the Outage is required to enable the Generator or days days
must be taken.
By end June OC2)
(the TSO's response as detailed in OC2

(Generators' or Interconnector Owners’ responses to the
By end July OC2)
TSO's changes and resolution of any disputes as set out in
OC2
(The SO to notify Generators of any further changes By end Sept. OC2)
required as detailed in OC2
Short Term Operational Planning : Planning for Year 0
During Year 0, OC2 requires notices to be given in respect - Year 0 - OC2
of the following (the details of which can be found in OC2):
(i) movements of Flexible Planned Outages - on not

less than 7 days' notice by the SO;
(ii) amendments to Planned Outages - request to be made

by the SO by notice in writing;
(iii) substitution of a different CDGU and/or Generating

Unit(s) within a Controllable SOLAR, WIND & ESU,
Dispatchable SOLAR, WIND & ESU for an Outage -
request to be made by the Generator by notice in
writing;
(iv)Short Term Planned Maintenance Outages - to be

requested by Generators or Interconnector Owners by
not less than 7 days' notice in writing, containing the
following information:
(a) identity of the CDGU(s), (or, in the case of a

CCGT Installation, CCGT Module(s) therein),
Controllable SOLAR, WIND & ESUs or Dispatchable
SOLAR, WIND & ESUs (or Generating Unit(s) therein)
Power Station Equipment and/or Interconnector
concerned; MW
(b) MW concerned (i.e. MW which would not be

Available as a result of the Outage and that which
would still be Available);
(c)duration of Outage (not exceeding 72 hours); hours
CC 323
(d)preferred Start Date & Start Time; date/time
(e) if the Outage is required for maintaining the

brush gear of a CDGU (or, in the case of a CCGT
Installation, CCGT Module(s) therein) and/or a
Controllable SOLAR, WIND & ESU or Dispatchable SOLAR,
WIND & ESU (or Generating Unit(s) therein)
(The SO will respond to a request for a STPMO in

accordance with OC2)
(v) Notified Unplanned Outages - to be notified by a
OC2
Generator as early as possible;
(vi)24 Hour Recall (in relation to a Notified OC2

Unplanned Outage) to be requested by the SO and,
if agreed to by the Generator or Interconnector
Owner, acknowledged by the Generator or
Interconnector Owner by notice in writing; date & time OC2
(vii)Forced Outages - to be notified by the Generator

or Interconnector Owner in writing, not later than 48
hours after the event, such notice to include the
Generator's best estimate of the date and time by
which the CDGU/Controllable SOLAR, WIND &
ESU/Dispatchable SOLAR, WIND & ESU/Power Station
Equipment/Interconnector is likely to have been
repaired and restored to its full level of Availability;
(viii)Release of CDGUs/Controllable SOLAR, WIND & OC2 OC2

ESU/Dispatchable SOLAR, WIND & ESU/Power Station OC2
Equipment/Interconnector for Outage – the TSO's
express formal consent required (see Schedule 8);
(ix)Return to service from Outage to be notified by the

Generator or Interconnector Owner to the SO;
(x)Overruns of Outages to be notified by the

Generator or Interconnector Owner to the SO
immediately the Generator or Interconnector Owner
becomes aware of the situation in writing, such notice
to include:
(a) the reason for the delay; and

date & time
(b) the Generator's or Interconnector Owner’s best

estimate of the date and time of return to service.
Part 2: Independent Generating Plant Outages

Each Generator with Independent Generating Plant shall be obliged to submit such information in
relation to that Independent Generating Plant for the purposes of Operation Planning as the SO
may reasonably require pursuant to OC2.4.1.
CC 324
SCHEDULE 4- DATA REGISTRATION CODE- GENERATOR OUTPUT/LOADING DATA AND
ENERGY SALES DATA
DATA DESCRIPTION UNITS TIMESCALE UPDATE DATA

COVERED TIME CATEGORY
GENERATION OUTPUT
Where requested by the SO, the Generator at The preceding Daily at OC1
each Power Station with a Registered Schedule Day 10.00
Capacity of 2MW, but not exceeding 5MW
must provide to the SO a half-hourly printout of
metered output in respect of such Power MW
Station for: MVAr
(i) Active Power; and
(ii) Reactive Power
LOADING PROFILES
Where requested by the SO, each Generator MW Years 1-3 ahead By end OC1
with Independent Generating Plant with a of week
Registered Capacity of 2MW and above and 45
in respect of each of its CDGUs other than PPA
CDGUs in relation to Predicted Output shall
provide the SO with estimated Loading profiles
for such Units for a period of 3 years ahead,
beginning in week 1 of the following year.
Where requested by the SO, each Generator with MW Following Schedule Daily at OC1
Independent Generating Plant other than Day (Following 3/2 10.00
SOLAR, WIND & ESUs with a Registered Schedule Days
Capacity of 2MW and above shall submit an where given as
estimate of Loading profiles including the half Friday/Saturd ay
hourly output. and for longer
periods at holiday
times)
Where requested by the SO, each Generator MW Following By 06.00 OC1

with Independent Generating Plant that is a Schedule Week on Friday
SOLAR, WIND & ESU with a Registered
Capacity of 2MW and above shall submit to
the SO an estimate of Loading profiles
ENERGY SALES
Each Supplier must provide to the SO in GW/h Years 1 - 3 ahead By end OC1
writing details of its anticipated aggregate of week
annual sales of Energy in respect of each of the 48
three following years in accordance with
OC1.4.1.1.
CC 325
SCHEDULE 5- DATA REGISTRATION CODE USERS SYSTEM DATA
The data listed in this Schedule 5 is required to be provided by:

1. a User (and by proposed Users applying for a Connection Agreement) in connection
with applications for new or modified arrangements for connections to or use of the NTDC
System;
2. a User who has requested a Statement of System Capacity as referred to in PC5.2;
3. a User at the time it notifies the SO of any significant changes to its System or operating regime; and
4. the categories of User specified in PC6.3.3 on a routine annual basis by the end of calendar week 52 of each
year.
DATA DESCRIPTION UNITS DATA

CATEGORY
Modelling Data
Modelling data of the Users Plant and Apparatus at the Connection Point in SPD
accordance with PC.A2.1.4 and PC.B2.1.3
User System layout
SPD/DPD
Single line diagrams of existing and proposed arrangements of main Plant and
Apparatus including:
(i) busbar layouts
(ii) electrical circuitry (i.e. lines, cables, transformers, switchgear
(iii) etc) phasing arrangements
(iv) earthing arrangements
(v) switching facilities
(vi) operating voltages
(vii) numbering and nomenclature
Reactive Compensation Equipment
For all independently switched reactive compensation equipment on the User's

System at 11kV and above, other than power factor correction equipment associated
directly with the User's Plant and Apparatus, the following information is required:
(i) type of equipment DPD
(ii) capacitive and/or inductive rating or its operating range in MVAr Mvar DPD
(iii) details of any automatic control logic to enable operating characteristics to be DPD
determined
(iv) the point of connection to the User's System in terms of electrical location and DPD
voltage
Short Circuit Infeed to the NTDC System
The total short circuit infeeds calculated in accordance with good industry practice into the
NTDC System
from the User System at the Connection Point as follows:
(i) maximum 3-phase short circuit infeed including infeeds from any Generating MVA SPD/DPD
Plant
forming part of the User's System
(ii) additional maximum 3-phase short circuit infeed from induction motors via the MVA DPD
User's System
(iii) minimum zero sequence impedance of the User's System at the Connection % on 100 SPD/DPD
Point
Lumped System Susceptance
Details of equivalent lumped network susceptance of the User's System at nominal % on 100 DPD
Frequency back to the connection with the NTDC System. This should include any
shunt reactors which are an integrated part of a cable system and which are not normally
in or out of service independently of the cable (i.e. they are regarded as part of the
CC 326
cable). It should not include:
(i) independent reactive compensation plant connected to the User's System; or
(ii) any susceptance of the User's System inherent in the Active and Reactive
Power Demand
(iii) data given under PC.A.3.2
Interconnection Impedance
% on 100 DPD
For User interconnections which operate in parallel with the NTDC System and
equivalent single impedance (resistance, reactance and shunt susceptance) of the
parallel User System. If the impedance is, in the reasonable opinion of the SO,
low, the more detailed information in the equivalent or active part of the parallel
User System may be requested.
Demand Transfer Capacity
DPD
Where the same Demand may be supplied from alternative NTDC System points of
supply, the proportion of Demand normally fed from each NTDC System supply point
and the arrangements (manual or automatic) for transfer under planned /fault Outage
conditions shall be provided. Where the same Demand is supplied from different User
supply points, then this information should be provided to all parties.
System Data
Each User with an existing or proposed User System connected at High Voltage
shall provide the following details relating to that High Voltage System:
(i) circuit parameters for all circuits:
rated voltage kV DPD
operating voltage kV DPD
positive phase sequence reactance % on 100 DPD
positive phase sequence resistance % on 100 DPD
positive phase sequence susceptance % on 100 DPD
zero phase sequence reactance % on 100 DPD
zero phase sequence resistance % on 100 DPD
zero phase sequence susceptance % on 100 DPD
(ii) Interconnecting transformers between the User's higher voltage system and the
User's primary voltage system:
rated MVA MVA DPD
voltage ratio DPD
winding arrangement DPD
positive sequence reactance (max, min, and nominal tap) % on MVA DPD
positive sequence resistance (max, min, and nominal tap) % on MVA DPD
zero sequence reactance % on MVA DPD
tap changer range +% to -% DPD
tap changer step size % DPD
tap changer type: on Load or off circuit DPD
(iii) Switchgear, including circuit breakers, switch disconnectors and isolators on all
circuits connected to the Connection Point including those at Power Stations:
rated voltage kV DPD
operating voltage kV DPD

CC 327
rated short circuit breaking current, 3-phase kA DPD
rated short-circuit breaking current, 1-phase kV DPD
rated load-breaking current, 3-phase kA DPD
rated load-breaking current, 1-phase kA DPD

rated short-circuit marking current, 3-phase kA DPD
rated short-circuit making current, 1-phase kA DPD
Protection Data
The following information relates only to Protection which can trip or intertrip or close any
Connection Point circuit breaker or any the SO circuit breaker:
(i) a full description, including estimated settings, for all relays and Protection systems DPD
installed or to be installed on the User's System;
(ii) a full description of any auto-reclose facilities installed or to be installed on the User's DPD
System, including type and time delays;
(iii) a full description, including estimated settings, for all relays and Protection systems DPD
installed or to be installed on the Generating Unit Generator Transformer, station
transformer and their associated connections:
(iv) for Generating Units having (or intended to have) a circuit breaker on the circuit leading DPD
to the Generator Terminals, at the same voltage, clearance times for electrical faults
within the Generating Unit zone; and
(v) the most probable fault clearance time for electrical faults on the User's System m/Sec DPD
Earthing Arrangements
Full details of the means of permanently connecting the User System to each, including impedance DPD
values.
Transient Overvoltage Assessment Data
When requested by the SO, each User is required to submit estimates of the surge impedance DPD
parameters present and forecast of its User System with respect to the Connection Point and to
give details of the calculations carried out. The SO may further request information on physical
dimensions of electrical equipment and details of the specification of Apparatus directly connected to
the Connection Point and its means of Protection.
User's System Demand (Active and Reactive Power)
Forecast daily Demand profiles net of the output profile of all Generating Plant directly connected to
the User's System in time marked half hours throughout the day as follows:
(a) peak day on the User's System MW/Mvar SPD/DPD
(b) day of peak Demand (Active Power) MW DPD
(c) day of minimum Demand (Active Power) MW DPD
User Customer Demand Management Data
The potential reduction in Demand available from the User in MW and MVAr, the notice required MW/Mvar DPD
to put such reduction into effect, the maximum acceptable duration of the reduction in hours and + text
the permissible number of reductions per annum.
Conversion Factor Data
The figures described as “fixed unit load” and “unit load scalar” under the TSC, which are the figures
submitted by a Generator or an Intermediary on its behalf pursuant to the “net output function”
provisions of the TSC.
Additional Conversion Factor Data
For Kilroot and Ballylumford Power Stations, the different configurations at which the Power
Stations may operate and which can affect the Conversion Factors, such configurations being
submitted in the form set out at PC.A3.3.12.
CC 328
SCHEDULE 6- DATA REGISTRATION CODE- LOAD CHARACTERISTICS AT GRID SUPPLY
POINTS
All data in this Schedule 6 is categorised as Standard Planning Data (SPD) and is required for existing and agreed
future connections. This data is to be updated annually by the end of week 52 for each of the next 7 financial years.
DATA DESCRIPTION UNITS DATA FOR FUTURE YEARS
Yr 1 Yr 2 Yr 3 Yr 4 Yr 5 Yr 6 Yr 7
For all types of Demand

(i) Type and electrical loading of
equipment to be connected:
number and size of motors;
types of drive and control
arrangements.
(ii) The sensitivity of the Demand to MW/kV
variations in voltage and Mvar/kV
Frequency on the NTDC System. MW/Hz
Mvar/Hz
(iii) The maximum harmonic content %
which the User would expect its
Demand to impose on the NTDC
System
(iv) The average and maximum phase %
unbalance which the User would
expect it’s Demand to impose on
the NTDC System.
For Fluctuating Loads > 5 MVA
(i) Details of the cyclic variation of
Demand (Active and Reactive
Power)
(ii) The rates of change of Demand
(Active and Reactive Power)
both increasing and decreasing.
(iii) The shortest repetitive time
interval between fluctuations in
Demand (Active and Reactive
Power)
(iv) The magnitude of the largest step
changes in Demand (Active and
Reactive Power) both increasing
and decreasing.
(v) Maximum energy demanded per half
hour by the fluctuating Load cycle
(vi) Steady state residual Demand

(Active Power) occurring
between Demand fluctuations
For User's Abnormal Loads
Details should be provided on any individual
Loads which have characteristics differing
from the normal typical range of Loads in
the domestic, commercial or industrial fields.
In
particular, details on arc furnaces, rolling
mills, traction installations etc. which are
liable to cause flicker problems
CC 329
SCHEDULE 7-DATA REGISTRATION CODE DEMAND CONTROL AND GENERAL DATA-
PART 1 - DEMAND CONTROL DATA
DATA DESCRIPTION UNITS TIME COVERED UPDAT DATA CAT.

E TIME
Customer Demand Management Initiated by a Supplier

A Supplier which enters into (or amends) an agreement or End of current By end OC4
other arrangement with a Customer allowing Customer year to 30th of
Demand Management must notify the SO in writing in April and/or for March
accordance with OC4.4.2.2 of its best estimate of the following year
following (on an aggregated basis) when the aggregate of its commencing 1st
possible Customer Demand Management pursuant to all May
such agreements or arrangements it has effected can equal
or exceed 2MW at any point in time:
(i) the level of expected and possible Demand MW OC4
Control
(ii) the circumstances in which the Customer OC4
Demand Management is expected to be and
may be utilised
(iii) the expected duration of Demand Control OC4
and the maximum permitted
(iv) the expected and possible frequency of initiation OC4
(v) the locations at which it is expected that OC4
Demand Control will be exercised
A Supplier must notify the SO in writing on each occasion The following OC4
that any Customer Demand Management of which it has Schedule Day
notified the SO under OC4.4.2.1 and OC4.4.2.2, is planned (where the
to be instructed (or has been instructed) by that Supplier Customer
and which will in aggregate equal or exceed (or has equalled Demand
or exceeded) 2MW at any point in time other than following Management is
an instruction by the TSO. Such notification must be given planned
in accordance with the timing requirements of OC4.4.2.4 sufficiently far in
and will contain: advance).
(a) the amount of Customer Demand Management

planned to be instructed, or which had been MW OC4
instructed;
(b) the length of time which the Customer Demand hours/ OC4
Management is anticipated to be in force and the minute
time at which it is to commence, or commenced; s
and
(c) the location on the Total System at which the location OC4
Customer Demand Management is to be, or
has been, implemented.
The Supplier must, in addition, notify the Customer MW OC4
Demand Management actually achieved (to the extent it
differs from the data already supplied) within 2 weeks of
initiation, including MW
profiles on a half hourly basis and the amount of Demand
reduction achieved
CC 330
Where a Supplier wishes to utilise voltage reduction as Customer OC4
Demand Management on the User System of any of its
Customers, the Supplier must notify the SO of such details as the
SO reasonably requires as far in advance as reasonably
practicable.
Customer Demand Management Initiated by the TSO
Where a Supplier wishes to make arrangements with the SO OC4

Year By end
whereby the SO would be given the ability to use Customer
commencing 1st of March
Demand Management for the purposes of Demand Control, it
May each
must notify the SO in writing of the following:
year
(i) the amount of the Demand Control reduction available; MW OC4
(ii) how often it can be used; OC4
(iii) the length of time that Demand Control can be used; hours/mins OC4
(iv) the notice required to be given to the Supplier by the hours/mins OC4
SO;
(v) any situations under which the available OC4
Customer Demand Management may be varied
or cannot be instructed by the SO;
(vi) the duration of the arrangement with the Customer; and OC4
(vii) any other information which the Supplier reasonably OC4
considers would be relevant to the TSO.
All forecast maximum Demand levels submitted to the SO by Users shall be on the basis of ACS Conditions.
All Users with Demand are obliged to provide such additional forecast Demand data as the SO may reasonably
request to enable the SO to estimate the diversified total Demand at various times throughout the year.
Part 2 - General Data

The SO may, by notice in writing, require Users, pursuant to OC8.4.2 to supply to it information of a technical (but not
commercial) nature to enable the SO to fulfil its obligations relating to the operation of the NTDC System (examples of
the type of information which may be required are set out in Appendix 2 to OC8 but that is not an exhaustive list).
PMC 331
SCHEDULE 8- DATA REGISTRATION CODE DATA SUPPLIED BY THE SO TO USERS
GRID CODE PROVISION DATA DESCRIPTION
Site Responsibility Schedules/Ownership Diagrams

CC9.1.3/CC9.1.4 The SO shall, in respect of each connection to the NTDC System for which a
Connection Agreement is required and those covered by Regulation 26 and Parts 1
and 2 of Schedule 3 of the Electricity Supply Regulations (NI) 1991, prepare:
(i) a Site Responsibility Schedule; and
(ii) an Ownership Diagram.
Operational Planning
OC2.6.2(c)(i)
The SO shall, by the end of September in each calendar year, provide each Generator in
writing with a Provisional Outage Programme showing the CDGUs, Controllable
SOLAR, WIND & ESUs or Dispatchable SOLAR, WIND & ESUs (or Generating
Unit(s) therein) and/or Power Station Equipment it may potentially withdraw from
service during each week of Years 2 and 3 for a Planned Outage.
OC2.6.3(c)(i)/ The SO shall, by the end of June in Year 1, provide each Generator in writing with a
OC2.6.3(f)(i) draft Final Outage Programme showing the CDGUs, Controllable SOLAR, WIND &
ESUs or Dispatchable SOLAR, WIND & ESUs (or Generating Unit(s) therein) and/or
Power Station Equipment it may potentially withdraw from service during each week of
Year 1 for a Planned Outage and shall, by the end of September, notify any further
changes by the issue of a Final Outage Programme.
OC2.6.7.3 The TSO’s express formal permission must be obtained by a Generator prior to
withdrawing a CDGU, Controllable SOLAR, WIND & ESUs or Dispatchable SOLAR,
WIND & ESUs (or Generating Unit(s) therein) or item of Power Station Equipment
for a Planned Outage, which permission shall specify:
(i) the identity of the CDGU, Controllable SOLAR, WIND & ESUs or
Dispatchable SOLAR, WIND & ESUs (or Generating Unit(s) therein) and/or
Power Station Equipment and MW concerned;
(ii) the duration of the Outage; and
(iii) the Start Date and Start Time.
0C2.7.1 If there is a deficit indicated in any week, the SO and the Other SO shall jointly issue a
System Capacity Shortfall Warning.
OC2.7.2 If there is a deficit indicated in any day, the SO and the Other SO shall jointly issue a
System Capacity Shortfall Warning.
OC2.8.2 The SO will, by the end of September in each calendar year, notify each Generator in
writing of those aspects of the draft NTDC System Outage plan which may affect such
Generator operationally, including proposed start dates and end dates of relevant NTDC
System Outages. The SO will also inform each Large Demand Customer with a
Demand greater than 10 MW of the aspects of the plan which may affect it.
OC2.8.5(a)(ii) The SO will, by 11.00 hours each Thursday during the Programming Phase, notify each
Generator in writing of those aspects of the NTDC System Outage plan which may affect
it operationally, including proposed start dates and end dates of relevant NTDC System
Outages. The SO will also inform each Large Demand Customer with a Demand
greater than 10 MW of the aspects of the plan which may affect it.
Indicative Operations Schedule
SDC1.4.8.9 The SO will issue the Indicative Operation Schedule each day to each Generator
with CDGUs, Controllable SOLAR, WIND & ESUs or Dispatchable SOLAR, WIND
& ESUs, each Pumped Storage Generator with respect to their Pumped Storage
Plant Demand, Energy Storage Generator with respect to their Energy Storage
Power Station Demand, each Interconnector Owner with regard to their
Interconnectors, each Demand Side Unit Operator in relation to their Demand
Side Units, provided that all the necessary information from these Users was made
PMC 332
available by not later than Gate Closure.
GRID CODE PROVISION DATA DESCRIPTION

Initial Planning Data
PC6.4.1 Initial planning data to be submitted on the SO website including the following information:
(i) User’s name (legal and project name);
(ii) User’s contact details;
(iii) User’s date of completed application;
(iv) Status of application, for example in progress or issued;
(v) Specific location, including grid co-ordinates; and
(vi) The capacity applied for the project; and
(vii) Interacting group where applicable.
DATA TO BE SUPPLIED BY THE SO IN CONNECTION WITH APPLICATIONS FOR CONNECTION TO THE NTDC SYSTEM OR
USE OF THE DISTRIBUTION, PROVINCIAL & SPTLs POWER SYSTEM
1. The SO Licence requires the SO to produce a Transmission System Statement (save where the SO is
relieved of such obligations by the Authority) which provides a means by which Users and intending Users
of the Transmission System are able to assess opportunities for connecting to and using the Transmission
System. The TSO’s obligations in this respect are described more fully in PC5.
2. The TO Licence requires the DISCOs, PROVINCIAL & SPTLs to produce a DISCOs, PROVINCIAL & SPTLs
System Statement (save where the DISCOs, PROVINCIAL & SPTLs Operator is relieved of such
obligations by the Authority) which provides a means by which Users and intending Users of the DISCOs,
PROVINCIAL & SPTLs System are able to assess opportunities f or connecting to and using the DISCOs,
PROVINCIAL & SPTLs System. The DISCOs, PROVINCIAL & SPTLs Operator’s obligations in this respect
are described more fully in PC5.
3. The SO Licence also imposes upon the SO certain obligations to offer to enter into an agreement for a new or
modified connection to the NTDC System or for use of the Distribution System and NTDC Transmission
Networks. In the case of a new or modified connection, the intending User's Plant and Apparatus must
comply with the requirements of the CC. Where a User or intending User requires more detailed information
concerning the requirements for a particular connection, that User may obtain such information pursuant to
CC6.1, CC.S1.1 and CC.S2.1.
End of DRC
PMC 333
SCHEDULING AND DISPATCH CODE NO.1 (SDC 1)
GENERATION SCHEDULING
CONTENTS
SDC 1.1 INTRODUCTION............................................................................................. 338
SDC 1.2 OBJECTIVE.................................................................................................... 340
SDC 1.3 SCOPE.......................................................................................................... 341
SDC 1.4 PROCEDURE................................................................................................. 341
APPENDIX A- (SCHEDULING AND DISPATCH CODE NO.1)............................................. 367
Generation Scheduling and Dispatch Parameters (GSDPs).......................................... 367
APPENDIX B- (SCHEDULING AND DISPATCH CODE N0.1)- POWER PLANT – DAILY

SCHEDULING NOTICES.............................................................................................. 368
APPENDIX C (SCHEDULING AND DISPATCH CODE 1)- GSDP REVISION NOTICE...............374
APPENDIX D (SCHEDULING AND DISPATCH CODE 1)- NOTIFICATION OF REVISED

AVAILABILITY........................................................................................................... 376
APPENDIX E (SCHEDULING AND DISPATCH CODE 1)- FACSIMILE.................................. 378
APPENDIX G (SCHEDULING AND DISPATCH CODE 1)- SCHEDULING DATA:

PARTICIPATING GENERATORS.................................................................................... 381
Appendix H: Market Development and the Implementation of CTBCM.........................383
SDC-1 334
SDC 1 SCHEDULING AND DISPATCH CODE NO.1
GENERATION SCHEDULING
SDC 1.1 INTRODUCTION

As a part of functions of the National Transmission and Dispatch Company (NTDC),
Scheduling and Dispatch of generation is performed by the System Operator. The
Generation Scheduling subcode (SDC 1) defines the roles and responsibilities of the
System Operator the Code Participants and the Market Operator in the scheduling of
available generation, Import/export and controllable load facilities, and operation
and management of a secure bulk power national transmission system of.The
purpose of this sub-code is to set out the processes, guidelines, and procedures for:
a) Generation/Load Scheduling
b) Ancillary Services Scheduling and Dispatch
c) Generator Outage Co-ordination
d) Market Operator and Commercial Settlements Code Interaction
SDC 1.1.1 CTBCM Provisions
This Scheduling and Dispatch Code No. 1 ("SDC1") forms part of the Sections under Common
Governance of the Grid Code. The Sections under Common Governance are those parts of the
Grid Code which are under common governance in both the Grid Code and the Grid Code of
Other SO/IO.
a) The form of this SDC1 is similar to the SDC1 in the Other Grid Code.
Differences relate to references to relevant power systems and related terms.
b) This SDC1 is intended to work in conjunction with other documents, including
the CTBCM Design Report (“CTBCM_DR”). The provisions of the Grid Code
and the Other Grid Code will take precedence over the CTBCM_DR.
c) Where stated in SDC1 the obligation to submit data in relation to some of the
information required to be provided to the SO may be fulfilled by Users where
such information submitted under the CTBCM_DR by a User or by an
Intermediary on behalf of Users is then provided to the SO by the Market
Operator in accordance with the CTBCM_DR, as further provided in this SDC1.
The SO may require Users to verify or provide revisions to data received by it
via the Market Operator.
d) Further provisions dealing with the Sections under Common Governance

are contained in the General Conditions.
SDC 1.1.2 SDC1 sets out the procedure used by the SO to develop unit commitment
schedules in respect of CDGU’s, Wind & Solar Farms, BESUs, Interconnectors and
Demand Side Units including the requirements for Users to submit data to support
this procedure:
i. Availability: the submission by a User to the SO of an Availability

Notice in respect of each of its:
(i) CDGUs (which for the avoidance of doubt comprise, Generating
Units subject to Central Dispatch, CCGT Installations, Hydro
Units, Pumped Storage Generating (but not Pumped Storage
Plant Demand or Energy Power Station Demand), ESGU and
Dispatchable Solar & Wind);
(ii) Pumped Storage Plant Demand;
(iii) Energy Storage Power Station Demand;
SDC-1 335
(iv) Interconnector Availability (in the case of the Interconnector
Owner);
(v) Demand Side Units;
(vi) in the case of Generator Aggregators, its Aggregated

Generating Units;
ii. Technical Parameters: the notification to the SO of the Technical

Parameters, in respect of the following Trading Day, by each User in a
Technical Parameters Notice, notification of Other Relevant Data and
notification of other technical data including Ancillary Services capability;
iii. Commercial Offer Data: the notification of Commercial Offer Data in

accordance with the CTBCM_DR;
iv. Physical Notifications: the declaration by a User to the SO of

Physical Notifications data in accordance with the CTBCM_DR;
v. Interconnector Schedule Quantities: the declaration by a

Scheduling Agent to the SO of Interconnector Schedule Quantities
in accordance with the CTBCM_DR; Revisions/Re-declarations:
revisions / Re-declarations of such information as provided for this
in SDC1
;
vi. Indicative Operations Schedules: the periodic production and issuing by
the SO of Indicative Operation Schedules as required under SDC
Compilation of Indicative Op.SCH. as a statement of which:
(i) CDGUs
(ii) ESGUs;
(iii) Pumped Storage Plant Demand;
(iv) Energy Storage Power Station Demand;
(v) Interconnectors;
(vi) Demand Side Units;
(vii) Aggregated Generating Units; and/or
(viii) Dispatchable Solar & Wind
may be required.
For avoidance of doubt, SDC1 sets out Procedure for in particular for:
(a) The daily Notification by a Generator to the SO of the Availability of any of
its CDGUs in an Availability Notice;
(b) The daily Notification to the System Operator of whether there are any
Parameters which differ from the Contracted Generation Scheduling and
Dispatch Parameters (GSDPs) in respect of the following schedule day by each
Generator in a GSDP Notice;
(c) Each Generator with CDGUs (Centrally Dispatched Generating Units), the daily
Notification to the System Operator in respect of the next following Schedule
Day in an Availability Notice of the MW Availability of each Generator with
CDGUs;
(d) In the case of all Generators under Central Dispatch with PPA ' and/or PSODA
as applicable, the submission to the System 1 Operator of any revisions to
SDC-1 336
fuel rates (or energy purchase prices, : as the case may be) by such
Generators as per the provisions of, their PPA and/or PSODA as applicable.
(e) The issuance by the System Operator of a "Day Ahead Notification" on the day
before the Schedule Day as a "Statement" of which of the Available
Generators may be required for the next Schedule Day.
(f) The daily Notification by a externally connected stakeholders and inteconnectors
to the System Operator of the Availability of any of its CDGUs in an Availability
Notice
Provided that the System Operator, in the process of Scheduling and Dispatch of
generation facilities shall have the following consideration: All the information
contained in Appendices A-G of SDC 1 needs to be provided by all the CDGUs, which
are declaring their Availability for the next Schedule Day.
SDC 1.1.3 The SO (in conjunction with the Other SO and Interconnector Operators) shall
develop, maintain and publish the process describing the methodology and
parameters to be used by the SO (and the Other SO and Interconnector
Operators) in fulfilling their responsibilities under this SDC1 and SDC2.
SDC 1.1.4 The System Operator shall take into account the impact/effects of power transfers
across any External Interconnection when reviewing the Generation Schedule
(including taking into account the power system security as well as cost of any
such transfers when compiling the "Generation Schedule"); and any power
transfers across the NTDC's Transmission System.
SDC 1.1.5 (a)This sub-code (SDC 1) requires that each Generator under Central Dispatch to
submit an Availability Notice, the form of which is set out in, Appendix B, which
needs to be submitted in writing or through telephone; and the required
information is to be submitted in full in such a notice.
(b) The notice, if given through telephone, must then be confirmed by facsimile and in
writing as soon as possible thereafter (and in any event be sent to the System Operator
within 2 hours). Where a facsimile and written notice are so sent by way of confirmation,
each notice shall state clearly that it is in confirmation of a notice already given by
telephone and must state the exact time at which the notice was given by telephone.
SDC 1.1.6 In this SDC 1, the term "Notice Submission Time" shall mean, 10.00 a.m.
SDC 1.1.7 For the purposes of this SDC 1, any reference to the fuel used for a CDGU
shall, in the case of a PPA CDGU (regardless of the entity it is contracting
with) be construed as a reference to the Des·1gnated Fuel.
SDC 1.2 OBJECTIVE

To enable the System Operator to prepare a "Generation Schedule" (utilising,
amongst other things, a Merit Order) to be used in the Scheduling and Dispatch
process, and thereby :
(a) To ensure the integrity of the National Transmission System, and that the SO
acts in conjunction with the Other SO so that the Other SO can ensure the
integrity of the Other Transmission System
SDC-1 337
(b) To ensure the security and quality of supply; and that the SO acts in
conjunction with the Other SO so that the Other SOs can ensure the security
and quality of supply in relation to the Other Transmission System
(c) That there is sufficient scheduled generation capacity to meet total demand at
all times together with an appropriate Reserve Margin (Sum of Operating and
Contingency Reserve).
(d) To enable the SO, in conjunction with the Other SO, to prepare and update
Indicative Operations Schedules to be used in the scheduling and Dispatch
process;
(e) To ensure that Indicative Operations Schedules are published
as provided for in this SDC1.
(f) Compliance with emissions requirements if any; and,
submitted to fulfilment of 1.2(a),(b) and (c),
(g) To minimise the cost of scheduled divergence from the
Physical Notifications in accordance with Merit Order, subject
to SDC1.2(g);
(h) In fulfilling the objective in SDC1.2(c), minimise the
requirement to issue Notices to Synchronise as per Final
Generation Schedule.
The purpose of this sub-code is also to enable the System Operator to prepare and
issue the "Day-ahead Notification·.
The Security Constrained Unit Commitment (SCUC) algorithm is used to

process the information and fulfilled the eight SDC1 objectives. SCUC is
described in Appendix H.
SDC 1.3 SCOPE

SDC 1 applies to, the System Operator and to all the Generators
under Central Dispatch with regard to their Generating Plants.
SDC1 applies to the SO and to the following Users:
(a) Generators with regard to their:
CDGUs and Dispatchable Solar & Wind.

(b) Pumped Storage Generators with regard to their Pumped Storage
Plant Demand;
(c) Energy Storage Generators with regard to their Energy Storage
Generating Unit or Power Station Demand as the case may be;
(d) In respect of the submission of Availability Notices under SDC1.4.1,
Interconnector Owners with regard to their Interconnectors
(e) In respect of the submission of Interconnector Schedule Quantities
under SDC1.4.4.6, Scheduling Agents with regard to the scheduling of
imports and exports across each Interconnector they have been
nominated to schedule;
(f) Demand Side Unit Operators in relation to their Demand Side Units;
and
(g) Generator Aggregators in respect of their Aggregated Generating
Units.
Each of which (other than the SO) is a “User” under this SDC1.
SDC 1.4 PROCEDURE

SDC 1.4.1 Availability Notice
SDC 1.4.1.1 Requirements
SDC-1 338
(a) Each Code Participant including those at a Power Station with multiple
Generating Units shall, by no later than the notice submission time each
Schedule Day, notify the System Operator by means of an Availability
Notice, in the form set out in Appendix B to this SDC 1 or in such other form
as the System Operator may specify with the approval of NEPRA, notify to
each Generator, and/or from time to time, changes of the Availability and/or
DSU MW availability, of each of its COG Us.
(i) CDGUs;
(ii) Controllable Solar & Wind farms;
(iii) Pumped Storage Plant Demand;
(iv) Energy Storage Plant Demand;
(v) Energy Storage Generating Units;
(vi) Interconnectors (to be submitted by the Interconnector

Owner);
(vii) Demand Side Units; or
(viii) Aggregated Generating Units as the case may be.

(b) A User may satisfy this obligation by submitting the data under the
CTBCM_DR, unless the SO requires, by notice to the User, the data to be
submitted to it directly under the Grid Code.
A Generator Aggregator will satisfy the obligation in this SDCxxxxx by
notifying to the SO in an Availability Notice in the form described in
paragraph (a) above the Availability of its Aggregated Generating Units as
the case may be.
(c) As a general requirement, the User shall ensure that the data in any
Availability Notice or any revision is consistent with its obligations under
SDCxxxxx and SDCxxxx.
SDC 1.4.1.2 Contents

The Availability Notice shall state the Availability of the:
(a) Relevant CDGU Controllable Solar & Wind, Interconnector, Demand Side
Unit or Pumped Storage Plant Demand as the case may be, (including,
in the case of a CCGT Installation, the Availability of each of the CCGT
Units within it) for each Imbalance Settlement Period in the time up to
and including the end of the relevant Trading Day (subject to revision
under SDCxxxxx). A new Availability Notice will supersede the previous
one in relation to Availability for Imbalance Settlement Periods which
are covered by the new one for each period in the following Schedule Day
(subject to revision under SDC 1.4.2.5(a)).
(b) In respect of Interconnectors, the Availability Notice shall state the

physical capability of the Interconnector, and shall take account of any
further restrictions placed by any relevant agreement or the provisions of
any licence in respect of the Interconnector, but shall not otherwise take
account of any expected transmission constraints or other aspects of the
operation of the Transmission System or an External System. A new
Availability Notice will supersede the previous one in relation to
Availability for Imbalance Settlement Periods which are covered by
the new one.
(c) In the case of a Generator Aggregator, the Availability Notice shall
state the Availability of its Aggregated Generating Units as a whole.
SDC-1 339
SDC 1.4.1.3 Whole Numbers: The MW figure stated in the Availability Notice shall be a whole
number.
SDC 1.4.1.4 Atmospheric Conditions
In the case of CDGUs and Controllable PPMs which are affected by ambient
conditions, an Availability Notice submitted by a Generator shall be stated as
being the User’s best estimate of the prevailing atmospheric conditions for the
Imbalance Settlement Period to which each part of the Availability Notice
relates.
SDC 1.4.2 Additional Grid Code availability notice
SDC 1.4.2.1 The following items are required to be submitted by each User by no later than
the Schedule Day each day, with the exception of Aggregators and
Demand Side Unit Operator, direct to the SO, regardless of whether these
have to be submitted under the CTBCM_DR. The requirements in SDC1.4.1 in
relation to data apply to this SDC1.4.2 as if repeated here.
SDC 1.4.2.2 Fuels
SDC 1.4.2.3 In case where a PPA CSGU (with/without PSODA) is capable of firing on different
fuels, then the Generator must submit an Availability Notice in respect of each
Designated Fuel for the CDGU, each containing the information set out in SDC
1.4.1.1.a above for each Designated Fuel and each marked clearly to indicate
for which Designated Fuel the Availability Notice applies to.
SDC 1.4.2.4
(a) Notwithstanding that a CDGU has been declared unavailable, the Generator
shall submit all the information that it would have submitted under this SDC 1
had the CDGU been declared Available.
(b) The System Operator shall use its reasonable endeavours to seek uniform
treatment in terms of availability of Gas turbines for start-up purposes with
due regard to their PPA and/or PSODA conditions as applicable.
SDC 1.4.2.5
(a) In relation to gas turbine PPA CDGUs (the Availability of which ( varies
according to ambient temperature), an Availability Notice 1 ,' submitted by a
Generator to NTDC for the purposes of declaring the level of Availability of
such CDGU must state the Availability at an ambient temperature of 15°C. )
(b) The Availability shall be deemed to be declared for all ambient temperatures
by reference to the level of Contracted Capacity for a PPA CDGU as specified
in the relevant Schedule to their Power Purchase Agreement (PPA) and/or
Power Station Operation & Dispatch Agreement (PSODA) adjusted by the
temperature correction factor set out in the relevant schedule of the relevant
Power Purchase Agreement (PPA) and/or Power Station Operation & Dispatch
Agreement (PSODA) by applying that absolute MW value.
(c) In relation to gas turbine PPA CDGUs, the term “Availability” shall be
construed accordingly.
SDC 1.4.2.6 In relation to any steam turbine PPA CDGU (with/without PSODA) at a power
plant which is capable of firing both on gas (which may include a mixture of gas
and oil) and on oil, the System Operator may, in respect of any settlement
period (and/or successive settlement periods) give notice (an "Overburn
Notice") to the relevant Generator with as much notice as possible and in any
event (except in the circumstances specified in (c) below) not less than 24
hours before the start of such settlement period (or the first such period) with
the fallowing effect and subject as follows:
(a) the Contracted Capacity (Gas) shall thereby be increased to Overburn
Contracted Capacity in respect of such settlement period (or periods)
following which the Generator shall re-declare the Availability of the CDGU in
an Availability Notice (and, for the avoidance of doubt, such increase shall
only apply for the settlement periods specified in the Overburn Notice);
SDC-1 340
(b) the aggregate number of settlement periods in any period of 24 hours and in
any period of 12 months for which Overburn Notices may be given shall be no
greater than the limits set out in the respective Schedule of the relevant
Agreement (PSODA) as applicable;
(c) The System Operator shall waive the rebate of Availability Payments for late
declaration of Availability under relevant schedule to the relevant Power
Agreement (PSODA) as applicable if the Overburn Notice is issued by NTDC
less than 24 hours in advance of the start of the relevant settlement period.
SDC 1.4.2.7 The Availability Notice issued by the Generator at a Power Plant where CDGUs
can be operated singly or in pairs, in accordance with SDC 1.4.1.1 (a) shall, in
addition to the information required by SDC 1.4.1.1 (a), state the CDGUs, that
have been declared to be Available for the next following Schedule Day, shall
be operated in pairs; and which CDGUs shall be singly operated.
SDC 1.4.2.8 The Generator may change the pairing of its CDGU Generators in consultation
with the System Operator.
SDC 1.4.2.9 Generating Unit Works Units
Once per week, on a day and time specified by the System Operator from time
to time but not less than two (2) hours before the occurrence of maintenance
outage, each Generator, Controllable Solar & Wind, Energy Storage
Generating Unit or Aggregated Generating Unit must, in respect of each of
its Power Plants, unless the data is supplied in some other agreed and
approved form, submit to the System Operator, in writing, details of the
Generating Unit Works Units for that Power Plant consumed by that Power Plant
since the last submission under this SDC 1.4.2.4, together with such other
information as the System Operator may require in order to calculate the
Generating Unit Works Units consumed by each CDGU, Controllable Solar &
Wind, Energy Storage Generating Unit or Aggregated Generating Unit at
that Power Plant.
SDC 1.4.3 General Availability requirements

SDC 1.4.3.1 Availability of Generating Plant
Each Generator and Generator Aggregator, subject to the terms and
conditions of the relevant Power Purchase Agreement (PPA) and/or Power
Station Operation & Dispatch Agreement (PSODA) throughout the term of the
Agreement (PSODA), shall in relation to its CDGUs, Controllable Solar & Winds
or Aggregated Generating Units maintain, repair, operate and fuel the CDGU
and/or Controllable Solar & Wind, and/or an Energy Storage Generating
Unit and/or Aggregated Generating Unit as required by Prudent Utility
Practice and any legal requirements applicable to its jurisdiction, with a view to
providing the required. the power delivery, the Ancillary Services as provided
for in an Ancillary Services Agreement , Contracted Capacity, and the
Contracted GSDPs.
SDC 1.4.3.2 Each Generator under Central Dispatch Power Station with multiple Generating
Units shall, subject to the terms and conditions of the relevant Power Purchase
Agreement (PPA) and/or Power Station Operation & Dispatch Agreement
(PSODA) throughout the term of the Power Purchase Agreement (PPA) and/or
Power Station Operation & Dispatch Agreement (PSODA) relating to a particular
CDGU, maintain, repair, operate and fuel its CDGU as required by Prudent
Operating Practices and any legal requirements with a view to providing the
SDC-1 341
power delivery, system support services, Contracted Capacity, and the
Contracted GSDPs.
SDC 1.4.3.3 Each Generator, and where relevant each Generator Aggregator, shall, subject
to the exceptions in 0 and SDC1.4.3.3A, use reasonable endeavours to ensure that
it does not at any time declare by issuing or allowing to remain outstanding an
Availability Notice, or a GSDP Notice which declares the Availability or GSDPs
of its CDGU, Controllable Solar & Wind, Energy Storage Generating Unit or
Aggregated Generating Unit, the Availability or Technical Parameters at
levels or values different from those that the CDGU, Controllable Solar & Wind,
Energy Storage Generating Unit and/or an Aggregated Generating Unit
could achieve at the relevant time under its Purchase Agreement (PPA) and/or
Power Station Operation & Dispatch Agreement (PSODA) with NTDC as
applicable except under unavoidable circumstances with the prior consent of
The SO can reject declarations to the extent that they do not meet these
requirements.
SDC1.4.1.12 shall not apply to the extent:
Provided that nothing contained in this Grid Code shall require the Generator to
declare levels or values better than the Contracted Capacity.
i. It would require the Generator or, where relevant, the Generator

Aggregator to declare levels or values better than the Registered Capacity,
the Contracted GSDPS in respect of a PPA CDGU and Technical
Parameters as submitted under the Planning Code in respect of a CDGU,
a Controllable Solar & Wind Energy, Storage Generating Unit and/or
an Aggregated Generating Unit necessary during periods of Scheduled
Outage or Short Term Scheduled Outage or otherwise with the consent of
the SO;
ii. Necessary while repairing or maintaining the CDGU, the Controllable Solar &
Wind and/or the Aggregated Generating Unit or equipment necessary to the
operation of the CDGU, the Controllable Solar & Wind and/or the Aggregated
Generating Unit where such repair or maintenance cannot reasonably, in
accordance with Prudent Utility Practice, be deferred to a period of Scheduled
Outage or Short Term Scheduled Outage;
iii. Necessary to avoid an imminent risk of injury to persons or material
damage to property (including the CDGU, the Controllable Solar &
Wind, Energy Storage Generating Unit and/or the Aggregated Generating
Unit); or
iv. It is not lawful for the Generator to operate the CDGU, the Controllable
Solar & Wind, Energy Storage Generating Unit and/or the Aggregated
Generating Units.
SDC 1.4.3.4 SDC1.4.3.2 shall not apply for a CDGU, a Controllable Solar & Wind, Energy
Storage Generating Unit, an Aggregated Generating Unit, Energy Storage
Power Station Demand or Pumped Storage Plant Demand that is
disconnected during the any one or more of the following:
(a) Any SO scheduled Annual Maintenance Outage or portion thereof on the
Outturn Availability Connection Asset lasting up to and including a
maximum of five days in total in a calendar year; or
SDC-1 342
(b) Where work to the Transmission System is being carried out that is driven
by the relevant CDGU, Controllable Solar & Wind, Energy Storage
Generating Unit, Aggregated Generating Unit, Energy Storage Power Station
Demand or Pumped Storage Plant Demand or driven by works related to
the Connection Agreement of the relevant CDGU, Controllable Solar & Wind,
Energy Storage Generating Unit, Aggregated Generating Unit, Energy
Storage Power Station Demand or Pumped Storage Plant Demand. This
does not include work carried out related to another Generation Unit with a
different Connection Point but a shared asset.
The relevant CDGU, Controllable Solar & Wind, Energy Storage Generating
Unit, Aggregated Generating Unit, Energy Storage Power Station Demand
or Pumped Plant Demand shall declare Availability at a value of zero during
any one or more of (a) or (b) above, as advised by the SO.
SDC 1.4.3.5 Availability of Demand Side Units
SDC 1.4.3.6 Each Demand Side Unit Operator shall, subject to the exceptions in SDC1.4.3.5
and SDC1.4.3.5A, use reasonable endeavours to ensure that it does not at any time
declare the Demand Side Unit MW Availability and the Demand Side Unit
characteristics of its Demand Side Unit at levels or values different from those
that the Demand Side Unit could achieve at the relevant time. The SO can reject
declarations to the extent that they do not meet these requirements.
SDC 1.4.3.7 SDC1.4.3.4 shall not apply to the extent:
(a) It would require the Demand Side Unit Operator to declare levels or
values better than Demand Side Unit MW Capacity and Technical
Parameters as submitted under the Planning Code in respect of a
Demand Side Unit;
(b) Necessary during periods of Scheduled Outage or Short Term
Scheduled Outage or otherwise with the consent of the SO;
(c) Necessary while repairing or maintaining the Demand Side Unit or
equipment necessary to the operation of the Demand Side Unit where
such repair or maintenance cannot reasonably, in accordance with
Prudent Utility Practice, be deferred to a period of Scheduled
Outage or Short Term Scheduled Outage.
(d) Necessary to avoid an imminent risk of injury to persons or material

damage to property (including the Demand Side Unit);
(e) It is not lawful for the Demand Side Unit Operator to change its
Demand Side Unit MW Response or to operate its Demand Side
Unit.
SDC1.4.3.4 shall not apply for a Demand Side Unit that is disconnected during
any one or more of the following:
(a) Any SO scheduled Annual Maintenance Outage or portion thereof on the

Outturn Availability Connection Asset lasting up to and including a
maximum of five days in total in a calendar year; or
(b) Where work to the Transmission System is being carried out that is driven
by the relevant Demand Side Unit or driven by works related to
Connection Agreement of the relevant Demand Side Unit. This does not
include work carried out to another Generating Unit with a different
Connection Point but a shared asset.
SDC-1 343
The relevant Demand Side Unit shall declare Availability at a value of zero
during any one or more of (a) or (b) above, as advised by the SO.
SDC 1.4.3.8 If at any time when the Availability of a CDGU is zero, an Availability Notice
shall be given increasing the Availability of the CDGU with effect from a
specified time, such Notice shall (in the case of a steam turbine CDGU) be
construed as meaning that the CDGU is capable of being synchronised with the
NTDC's System at that specified time or, (in the case of a gas turbine PPA
CDGU), capable of being started at that specified time. A dispatch instruction
issued by the System Operator to synchronise the CDGU to the NTDC's System
or, as the case may be, start the CDGU, at or after the specified time shall be a
valid dispatch instruction (regardless of the minimum time to synchronise
specified in the GSDPs).
SDC 1.4.3.9 If at any time when a CDGU is synchronised with the National Transmission
System, the Generator issues an Availability Notice increasing the level of
Availability of the CDGU from a specified time, such notice shall be construed
as meaning that the CDGU is capable of being dispatched to increase
generation to levels greater than the previously prevailing level of Availability
up to the level specified in the new Availability Notice but commensurate with
the maximum loading rate declared for the CDGU as a GSDP f ram the
specified time.
SDC 1.4.3.10 If at any time when a CDGU is synchronised with the National Transmission
System, the Generator issues an Availability Notice decreasing the level of
Availability of the CDGU from a specified time, such Notice shall be construed
as meaning that the CDGU is capable of maintaining output at the level of the
prevailing Availability until the time specified in the Notice and thereafter, shall
be capable of maintaining output to the level which would have been achieved
if a dispatch instruction had been given to de-load, with effect from the
specified time, at the maximum de-loading rate declared for the CDGU in the
GSDP Notice at such time down to the level of Availability specified in the new
Availability Notice.
SDC 1.4.3.11 Changes in Availability:

a) A User may, subject to this SDC1.4.3 and as provided for in this SDC1,
make revisions to the Availability Notice submitted to the SO under
SDC1.4.1.1at any time after submission of the Availability Notice in
accordance with its obligations to make the unit Available under SDC1.4.3
by submission by the Electronic Interface of a revised Availability
Notice which shall be in the form set out on the SO website or in such other
form as the SO may reasonably notify to each User from time to time.
b) In the event that the SO submits a Post Event Notice under OC.XX in
relation to any part of the period covered by the Availability Notice at any
time after submission of the Availability Notice, the User shall be deemed
to have submitted a revised Availability Notice consistent with such Post
Event Notice.
c) The revisions to the Availability Notice may include revisions of the levels
of Availability in the CCGT Installation Matrix reflecting the revised
Availability.
d) Additional Grid Code Availability Notice: A User may, subject to
SDC1.4.3 and to the provisions of this SDC1, make revisions to the
Additional Grid Code Availability Notice submitted to the SO under
SDC1.4.2 at any time after the submission of the Additional Grid Code
Availability Notice in accordance with its obligations to make the unit
SDC-1 344
Available under SDC1.4.3 by submission by the Electronic Interface of a
revised Additional Grid Code
Availability Notice. The Notice shall be in the form set out on the SO
website or in such other form as the SO may reasonably notify each User
from time to time.
e) Increasing Availability: If a Generator, a Generator Aggregator or a

Demand Side Unit Operator in respect of a CDGU, an Aggregated
Generating Unit, a Demand Side Unit, Energy Storage Power
Station, Energy Storage Generating Unit or Pumped Storage Plant
in relation to Demand, issues an Availability Notice increasing (from
zero or otherwise) the level of Availability or Demand Side Unit MW
Availability from a specified time, such notice shall be construed as
meaning that:
(i) in the case of a CDGU and/or Aggregated Generating Unit, the

CDGU and/or Aggregated Generating Unit is capable of being
synchronised to the Transmission System or Distribution
System at that specified time or increasing its MW Output at that
specified time as the case may be;
(ii) in the case of a CDGU which is an Open Cycle Gas Turbine, the
CDGU is capable of being started at that specified time; or
(iii) in the case of a Demand Side Unit, the Demand Side Unit is
capable of delivering a greater Demand Side Unit MW Response
at that specified time.
f) Controllable Solar & Wind and ESGU: If a Generator or, where
relevant a Generator Aggregator, in respect of a Controllable Solar &
Wind and ESGU, issues an Availability Notice increasing (from zero or
otherwise) or decreasing the level of Availability from a specified time,
such notice shall be effective from the Imbalance Settlement Period
following the specified time.
g) Decreasing Availability: When a CDGU and/or Controllable Solar &
Wind and ESGU is Synchronised to the System the Generator may
have occasion to issue an Availability Notice decreasing the level of
Availability of the CDGU and/or Controllable Solar & Wind and ESGU
from a specified time. Such notice shall be construed as meaning that the
CDGU and/or Controllable Solar & Wind and ESGU is capable of
maintaining Load at the level of the prevailing Availability until the time
specified in the notice. Thereafter, the CDGU and/or Controllable Solar &
Wind and ESGU shall be capable of maintaining Load to the level which
would have been achieved if a Dispatch Instruction had been given to
reduce the Load. This would have occurred with effect from the specified
time, at the maximum De-Loading Rate and/or Ramp-Down Rate
declared for the CDGU and/or Controllable Solar & Wind and ESGU as
a Technical Parameter at such time down to the level of Availability
specified in the new Availability Notice.
When a Demand Side Unit is providing a Demand Side Unit MW
Response the Demand Side Unit may have occasion to issue an
Availability Notice decreasing the level of Demand Side Unit MW
Availability of the Demand Side Unit from a specified time. Such notice
shall be construed as meaning that the Demand Side Unit is capable of
maintaining Demand Side Unit MW Response at the level of the
prevailing Demand Side Unit MW Availability until the time specified in
the notice. Thereafter, the Demand Side Unit shall be capable of
SDC-1 345
maintaining Demand Side Unit MW Response to the level which would
have been achieved if a Dispatch Instruction had been given to reduce
the Demand Side Unit MW Response. This would have occurred with
effect from the specified time, at the Maximum Ramp Down Rate
declared for the Demand Side Unit as a Technical Parameter at such
time down to the level of Demand Side Unit MW Availability specified in
the new Availability Notice.
(h) If an Interconnector Owner in respect of an Interconnector issues an

Availability Notice increasing (from zero or otherwise) or decreasing the
Availability of the Interconnector as a whole from a specified time, such
notice shall, subject to SDC1.4.3.6a) be effective immediately following the
specified time.
SDC 1.4.3.12 Further Revisions

(a) A If a Generator, a Generator Aggregator or a Demand Side Unit
Operator in respect of a CDGU, an Aggregated Generating Unit, a
Demand Side Unit, Energy Storage Power Station, Energy Storage
Power Plant with multiple Generating Units may make revisions to the
Availability Notice submitted to the System Operator under SDC 1.4.1. at
any time after submission of the Availability Notice in accordance with its
obligations under SDC 1.4.1.2 by submission of a revised Availability
Notice which shall be in the form set out in Appendix D - F to this SDC 1
or in such other form as the System Operator may reasonably notify to
each a Generator, a Generator Aggregator or a Demand Side Unit
Operator in respect of a CDGU, an Aggregated Generating Unit, a
Power Plant from time to time.
(b) In the event that the a Generator, a Generator Aggregator or a Demand
Side Unit Operator in respect of a CDGU, an Aggregated Generating
Unit, a Demand Side Unit, Energy Storage Power Station, Energy
Storage Power Plant submits a maintenance outage notice under OC 4 or
NTDC submits a post-event notice under OC 12 in relation to any part of
the period covered by the Availability Notice at any time after submission
of the Availability Notice, the Generator shall be deemed to have
submitted a revised Availability Notice consistent with such Outage Notice
or post event notice, as the case may be. However, in the case where the
Outage Notice is not issued immediately and does not specify the reduced
Availability, a Generator, a Generator Aggregator or a Demand Side
Unit Operator in respect of a CDGU, an Aggregated Generating Unit, a
Power Plant must, as soon as possible, submit a revised Availability
Notice reflecting its reduced Availability. The System Operator shall,
insofar as it is reasonably possible, take account of such revisions in the
preparation of its "Generation Schedule".
(c) If any of the data submitted to the System Operator under SDC 1.4.2.1 and
SDC 1.4.2.2 changes, a a Generator, a Generator Aggregator or a
Demand Side Unit Operator in respect of a CDGU, an Aggregated
Generating Unit, a Demand Side Unit, Energy Storage Power Station,
Energy Storage Power Plant must (in the case of data submitted under
SDC 1.4.2.1 by means of a GSOP Notice) make revisions to such data and
must notify the System Operator of any revisions to any previously revised
data by submitting another Revised GSDP Notice (in the form set out in
Appendix C to this SDC 1 or in such other form as the System Operator
may reasonably notify to each Generator from time to time) and must
notify the System Operator of any Other Generation Relevant Data of
SDC-1 346
which it becomes aware at any time after any original submission in
writing. The System Operator shall, insofar as it is reasonably possible,
take account of such revisions or notifications. The provisions of SDC
1.4.4.1 (b} shall apply to revisions under this paragraph to data submitted
under SDC 1.4.2.1 and SDC 1.4.2.2.
(d) As a general requirement, the Generator must ensure that the data in any
Availability Notice, GSDP Notice, or Notice of any Other Generation
Relevant Data or any revision thereto is consistent with its obligations
under SDC 1.4.1.2(b) and the Power Purchase Agreement (PPA) and/or
Power Station Operation & Dispatch Agreement (PSODA) with NTDC.
SDC 1.4.3.13 Default Availability:

(a) Insofar as any data submitted or deemed to have been submitted on any
particular day in any Availability Notice, or any revision is inconsistent with
any other data in any other such notice, then the most recently submitted
data which, if substituted for the inconsistent data, would make the data in
such notices consistent, shall apply for the next following Trading Day or any
other values that the SO may reasonably deem appropriate.
(b) Insofar as an Availability Notice is not submitted, the User shall be deemed
to have submitted an Availability Notice by Schedule Day stating that the
Availability of the relevant CDGU, Controllable Solar & Wind and ESGU,
Demand Side Unit and/or the Aggregated Generating Units for the whole
of the relevant Trading Day will be the level of Availability and Operating
Mode declared in respect of the final Imbalance Settlement Period of the
current Trading Day or any other values that the SO may reasonably deem
appropriate.
SDC 1.4.4 Technical & Commercial information

a) Technical Parameters
(i) By not later than the Schedule Day, each User shall in respect of
each:
o CDGU;
o Controllable Solar & Wind and ESGU;

o Aggregated Generating Unit,
o Pumped Storage Plant Demand
o Energy Storage Power Station Demand; and/or
o Demand Side Unit,
submit to the SO a Technical Parameters Notice in such form
as the SO may reasonably notify to each User or in the form
published on the SO website from time to time, containing the
Technical Parameters to apply for the relevant Trading Day.
(ii) A User may satisfy this obligation by submitting the data under
the CTBCM_DR, unless the SO requires, by notice in writing to the
User, the data to be submitted to it under the Grid Code.
(iii) Subsequent revisions to the Technical Parameters Notice may

be submitted according to the technical offer data submission
provisions as set out in the CTBCM_DR. If there is a change to the
SDC-1 347
data submitted under the CTBCM_DR, the User shall notify the
SO.
(iv) As a general requirement, the User shall ensure that the data in
any Technical Parameters Notice, or any revision thereto is
consistent with its obligations under SDC1.4.3.2 and SDC1.4.3.4.
b) Flexibility:
(i) In the case of any Technical Parameters as to which the User
should, acting in accordance with Prudent Utility Practice, have
some flexibility either in the revision itself or in the time at which
the revision is to take effect the SO may, acting reasonably,
suggest an amended data figure and/or an amended time at which
the data figure is to take effect.
(ii) Insofar as it is able to do so without breaching any obligations

regarding confidentiality contained either in the SO Licence or in
any agreement, the SO shall notify the User of the reasons for
such flexibility request in such degree of detail as the SO
considers reasonable in the circumstances.
If the User agrees to such suggestion (such agreement not to be
unreasonably withheld) the User shall use reasonable endeavours
to accommodate such suggestion and submit a revised Technical
Parameters Notice accordingly. In any event, the SO may
require such further information on the revision as is reasonable
and the User shall give the SO such information as soon as
reasonably practicable.
A User shall notify the SO as soon as it becomes aware, acting in accordance with
Prudent Utility Practice, that any of the data submitted under SDC1.4.4.1
changes.
(c) Changes to Technical Parameters:
If any of the data submitted to the SO under this SDC1.4.4.1 changes, a User
shall, subject to SDC1.4.3, make revisions to such data. The User shall notify
the SO of any revisions to any previously revised data by submitting by the
Electronic Interface a revised Technical Parameters Notice in the form
set out on the SO website or in such other form as the SO may reasonably
notify to each User from time to time.
(d) Energy Limits for Hydro Units:

A Generator in respect of its Hydro Units shall resubmit Energy Limits on
the Trading Day regardless of whether the Energy Limits have changed
since the Schedule Day. Revised Energy Limits for Hydro Units may be
submitted at any time up until 11.00 hours on the relevant Trading Day in a
format specified by the SO.
(e) Default Technical Parameters:
Insofar as any data submitted or deemed to have been submitted on any

particular day in any Technical Parameters Notice (such notice not being
relevant to an Interconnector Owner), or any revision thereto is inconsistent
with any other data in any other such notice, then the most recently
submitted data which, if substituted for the inconsistent data, would make the
data in such notices consistent, shall apply for the next following Trading
Day or any other values that the SO may reasonably deem appropriate.
SDC-1 348
Insofar as not submitted or revised, the applicable Standing Technical Offer
Data for Technical Parameters shall apply for the next relevant Trading
Day.
Default Energy Limits for Hydro Units: Notwithstanding the obligations in

SDC1.4.4.1(d), in respect of Hydro Units, the Energy Limit that applied to
the previous Trading Day will be used.
SDC 1.4.4.1 Availability of Generating Units

Additional Grid Code Characteristics Notice
The following items are required to be submitted by each User direct to the SO:
(a) Individual CCGT Unit data equivalent to the data required for a CCGT
Installation. It shall also show any revisions to the Technical
Parameters for each of the CCGT Units within it.
(b) Different Fuels: In the case where a CDGU is capable of firing on different
fuels, then the Generator shall submit an Additional Grid Code
Characteristics Notice in respect of any additional fuel for the CDGU,
each containing the information set out in SDC1.4.4.1 above for each fuel
and each marked clearly to indicate to which fuel it applies.
(c) Export adjustment factors applied by the User in submitting data and that
may be applied by the SO where applicable in issuing Dispatch
Instructions and otherwise in calculations relating to instructions in
relation to the relevant Plant and/or Apparatus, between the Generator
Terminals and the Connection Points.
(d) In the case of Interconnector Owners, Interconnector data, including
but not limited to the Availability of Interconnector Filters.
(e) In relation to each Demand Side Unit, the Demand Side Unit Notice
Time and the Demand Side Unit MW Response Time.
(f) Where there is an Ancillary Services Agreement in place, the Ancillary
Services which are Available.
(g) The parameters listed in Appendix A Part XX of SDC1.
A Generator shall submit to the SO the Operating Reserve capabilities for each
category of Operating Reserve defined in OC4.6.3 for each of its CDGUs for each
Imbalance Settlement Period.
A User shall notify the SO as soon as it becomes aware, acting in accordance with
Prudent Utility Practice, that any of the data submitted under SDC1.4.4.2 no
longer correct.
(a) By no later than the notice submission time each Schedule Day, each
Generator shall in respect of each CDGU which has been declared
Available in an Availability Notice under SDC 1.4.1.1 in respect of the
following Schedule Day submit to the System Operator in writing (in
the form set out in Appendix B to this SDC1 or in such other form as
the System Operator may notify to each Generator from time to time)
details in relation to the following Schedule Day of any "newly arisen
special factors" which in the reasonable opinion of the Generator may
have a material effect on the likely output of its Generating Unit. The
notice must be consistent with the Generator's obligations under the
provisions of SDC 1.4.1.2(b).
(b) In the case where a CDGU is capable of firing on different fuels, the
Generator must submit details in respect of each Designated Fuel for
the CDGU, each containing the information set out in (a) above for
SDC-1 349
each Designated Fuel, and each marked clearly to indicate to which
Designated Fuel (or fuel) it applies to.
A User may make revisions to the Additional Grid Code Characteristics Notice
submitted to the SO under SDC1.4.4.2 at any time after the submission of the
Additional Grid Code Characteristics Notice by submitting by the Electronic
Interface a revised Additional Grid Code Characteristics Notice. The notice
shall be in the form set out on the SO website or in such other form as the SO may
reasonably notify to each User from time to time.
SDC 1.4.4.2 Other Relevant Data
(a) By not later than the Schedule Day of each day, each User in respect of
each of its Plant, shall in respect of the following Trading Day submit
to the SO in writing in the form set out on the SO website or in such
other form as the SO may reasonably notify to each User from time to
time), details in relation to the relevant Trading Day of any newly
arisen special factors, including abnormal risk to loss, which in the
reasonable opinion of the User may have a material effect on the likely
MW Output or Demand Side Unit MW Response of such Plant
(including, for a CCGT Installation in relation to each of the CCGT
Units therein). The notice shall be consistent with the User’s obligations
under SDC1.4.3.2. The provisions of this paragraph also apply to
Interconnector Owners in relation to their Interconnector Filters.
(b) Where a CDGU is capable of firing on different fuels, then the
Generator shall submit details in respect of each fuel for the CDGU.
Each set of details shall contain the information set out in (a) above for
each fuel and each shall be marked clearly to indicate to which fuel it
applies
SDC 1.4.4.3 Additional Supply Data and timelines
The following procedures shall be followed to allow the System Operator to develop
a daily "Schedule" for dispatching:
(a) Sixty days prior to 1 April of each year, all bilateral contracts shall be
submitted to NEPRA, CRPEA and the System Operator for review and
approval.
(b) On or before 1 April of each year, all CDGU, an Aggregated Generating Unit,
Energy Storage Power Station, Energy Storage Power Plant, including
Hydel, PV plants, Wind power parks and Nuclear shall submit a declaration of
Availability to the System Operator covering a period of next one year.
(c) Demand-side Users, DISCOS, Provincial and SPTL Companies and BPCs, shall
submit a daily energy purchase requirement on an hourly basis. The System
Operator shall calculate, and issue the national transmission system line
losses for billing after-the-fact as per the provisions of the approved
CTBCM_DR.
SDC 1.4.4.4 Changes to Other Relevant Data
(a) A User, acting in accordance with Prudent Utility Practice, shall notify
the SO as soon as it becomes aware that any of the data submitted
under SDC1.4.4.4 has changed.
SDC-1 350
If any of the data submitted to the SO under this SDC1.4.4.4 is no longer
correct, a User shall, subject to SDC1.4.3, make revisions to such data.
The User must notify the SO of any new Other Relevant Data of which
it becomes aware at any time, in writing.
(b) In respect to Fuel Rate, the generation or energy purchase prices

including any revisions to the energy purchase prices for a PPA CDGU
in respect of the week beginning on the Schedule Day falling on the
next following Monday shall be deemed to be submitted by that
Generator by the notice submission time each Tuesday.
(c) In so far as not revised or if the fuel rate in the energy bid price notice
is higher than that deemed to have been submitted under (a) above,
the. most recently submitted generation or energy prices shall apply
for the relevant week
(d) In case where a CDGU is capable of firing on different fuels, any
revisions shall be address separately for each fuel.
(e) Default Other Relevant Data
Insofar as any data submitted or deemed to have been submitted on any
particular day in any notice of Other Relevant Data or any revision
thereto is inconsistent with any other data in any other such notice, then
the most recently submitted data which, if substituted for the
inconsistent data, would make the data in such notices consistent, shall
apply for the next following Trading Day or any other values that the
SO may reasonably deem appropriate.
Insofar as not submitted or revised, the last notice relating to Other
Relevant Data to have been submitted shall apply for the next
relevant Trading Day.
(f) As a general requirement, the User shall ensure that the data in any
Availability Notice, Technical Parameters Notice, or notice of any
Other Relevant Data or any revision thereto is consistent with its
obligations under SDC1.4.3.2 and SDC1.4.3.4.
SDC 1.4.4.5 Commercial Offer Data

(a) Each:
 Generator;
 Energy Storage Generator;
 Energy Storage Power Plant Demand
 Pumped Storage Generator;
 Demand Side Unit Operator; and
 Generator Aggregator,
Shall in respect of:
 Each of its CDGUs;
 Each of its Energy Storage Power Station Demand; Each of its

Pumped Storage Plant Demand;
 Each of its Demand Side Units; and Its Aggregated Generating

Units, submit to the SO, either directly or by means of an
Intermediary on its behalf (if applicable), Commercial Offer Data in
accordance with the CTBCM_DR.
(b) The SO may require, by notice to the relevant User, the data referred to
SDC-1 351
at SDC1.4.4.4(a) to be submitted to it directly under the Grid Code. All
data items submitted under this SDC1.4.4.4 are to be at levels of MW
Output at the Connection Point.
(c) Amendments to Commercial Offer Data shall be in accordance with the
CTBCM_DR.
(d) Default Commercial Offer Data: Insofar as not submitted or revised,

Commercial Offer Data shall be deemed in accordance with the
CTBCM_DR.
SDC 1.4.4.6 SDC1.4.4.6 Users Physical Notifications, Interconnector Schedule Quantities

& Revisions
(a) Each:
i. Energy Storage Generator;
ii. Energy Storage Power Plant Demand
iii. Pumped Storage Generator;
iv. Demand Side Unit Operator; and
v. Generator Aggregator,
vi. Shall in respect of:
 Each of its CDGUs;
 Each of its Pumped Storage Plant Demand;
 Each of its Energy Storage Power Station Demand;
 Each of its Pumped Storage Plant Demand;
 Each of its Demand Side Units; and
 Its Aggregated Generating Units,
submit to the SO, either directly or by means of an Intermediary on its

behalf (if applicable), Physical Notifications by Schedule Day for the
corresponding Trading Days in accordance with the CTBCM_DR. Physical
Notifications shall be technically feasible. Users shall ensure that the
accuracy of Physical Notifications is commensurate with Good Industry
Practice.
(b) Prior to Final Generation Schedule, Physical Notifications submitted in
accordance with SDC1.4.4.6(a) shall be amended by the User (or
Intermediary if applicable) to align with changes to their expected Active
Power Generation or Active Power Demand. A new Physical
Notification will supersede the previous one in relation to a Physical
Notification for Imbalance Settlement Periods or parts thereof which
are covered by the new one. At Final Generation Schedule, Physical
Notifications for the relevant Imbalance Settlement Period become
Final Physical Notifications for that Imbalance Settlement Period.
Final Physical Notifications may not be amended.
(c) Each Generator may, in respect of their Controllable PPM submit

Physical Notifications in accordance with the provisions of SDC1.4.4.6(a)
and SDC1.4.4.6(b).
SDC-1 352
(d) In the case where a CDGU is capable of firing on different fuels, then
the Generator must submit a GSDP Notice in respect of each
Designated Fuel for the CDGU (or fuel in the case of an Externally-
connected CDGU), each containing the information set out in (a) above
for each Designated Fuel (or each fuel) and each marked clearly to
indicate to which Designated Fuel (or fuel) it applies to.
(e) Each Scheduling Agent shall in respect of each Interconnector they

have been nominated to schedule, submit to the SO, Interconnector
Schedule Quantities by Schedule Day for the corresponding Trading
Days in accordance with the CTBCM_DR. Prior to Final Generation
Schedule, Scheduling Agents shall submit further Interconnector
Schedule Quantities in accordance with the CTBCM_DR to reflect trading
in intraday markets. At Final Generation Schedule (or an alternative later
time advised from time to time by the SO acting in accordance with
Prudent Utility Practice) for an Imbalance Settlement Period, further
Interconnector Schedule Quantities may not be submitted for that
Imbalance Settlement Period.
(f) Any revisions to the Contracted GSDPs during Real Time Operations
must be well documented and agreed to with the System Operator
including the nature and quantification of the revision, duration of such
revision, reason for the revision, and anticipated time when the
Generator shall be back to its Contracted GSDP values.
i. By no later than the notice submission time each Schedule Day, each
Generator shall in respect of each of its CDGU that has been declared
Available in an Availability Notice submit to the System Operator in a
revised GSDP Notice, in the form set out in Appendix C to this SDC 1
or in such other form as the System Operator may notify to each
Generator from time to time.
ii. In the case of a PPA CDGU (with/without PSODA), any revisions to the
GSDPs compared with the Contracted GSODPs to apply for the next
following schedule day in the form set out in Appendix C to this SDC
1 or in such other form as the System Operator may specify from
time to time.
(g) Notwithstanding the obligations in SDC1.4.4.6(a), SDC1.4.4.6(b) and

SDC1.4.4.6(d), a value of zero will be deemed in all Imbalance Settlement
Periods, or parts thereof, for which Physical Notifications data or
Interconnector Schedule Quantities date has not been submitted.
(h) If a User has submitted proposals for a test to the SO and subsequently
receives approval for the test from the SO, the User (or their
Intermediary, if applicable) shall submit Physical Notifications for the
unit under test in accordance with the CTBCM_DR to identify the time
periods during which their units are under test. The User shall ensure that
the Physical Notifications submitted in respect of a unit under test align
with the approved test start time, test MW Output profile (or Demand
Unit MW Response profile in the case of Demand Side Units) and test
end time.
(i) In the case of any revision to the GSDPs, as to which the CDGU,
Controllable Solar & Wind, Energy Storage Generating Unit,
Aggregated Generating Unit, Energy Storage Power Station
Demand, Demand Side Unit or Pumped Plant Demand should, acting
in accordance with prudent operating practices, have some flexibility
either in the revision itself or in the time-frame in which the revision is to
take place, the System Operator may, acting reasonably, suggest an
SDC-1 353
amended revision to the CDGU, Controllable Solar & Wind, Energy
Storage Generating Unit, Aggregated Generating Unit, Energy
Storage Power Station Demand, Demand Side Unit or Pumped Plant
Demand (including a statement to provide that there shall be no further
revision) and/or an amended time at which the revision is to take effect.
(j) Insofar as the System Operator is able to do so without breaching any

obligations regarding confidentiality contained either in the System
Operator Licence or in any Agreement, the System Operator shall notify
the CDGU, Controllable Solar & Wind, Energy Storage Generating Unit,
Demand, Demand Side Unit or Pumped Plant Demand of the reasons
for such amended revision request in such degree of detail as the
System Operator considers reasonable under the circumstances. If the
CDGU, Controllable Solar & Wind, Energy Storage Generating Unit,
Demand, Demand Side Unit or Pumped Plant Demand agrees to such
suggestion of the System Operator (such Agreement not to be
unreasonably withheld by either Entity), the CDGU, Controllable Solar &
Wind, Energy Storage Generating Unit, Aggregated Generating Unit,
Energy Storage Power Station Demand, Demand Side Unit or
Pumped Plant Demand shall use reasonable endeavours to
accommodate such suggestion, and submit a revised GSDP Notice
accordingly.
(k) In any event, the System Operator may require such further information
on the revision as is reasonable, and the CDGU, Controllable Solar &
Pumped Plant Demand must give the System Operator such
information as soon as possible. None of the revisions to the GSDPs shall
be in violation of the terms of the specific PPA Agreements with the
System Operator. Financial impacts of such deviations or revisions in the
Contracted GSDPs shall be assessed by the System Operator, and
communicated with the CDGU, Controllable Solar & Wind, Energy
Demand.
(l) Supplemental Energy Bid : Each Generator, Controllable Solar &

Pumped Plant Demand may in respect of each Generator Controllable
Solar & Wind, Energy Storage Generating Unit, Aggregated
Generating Unit, Energy Storage Power Station Demand, Demand
Side Unit or Pumped Plant Demand each day prior to the notice
submission time submit to the System Operator a supplemental energy
bid, if any, in accordance with the approved commercial arrangements
as per the provisions of the approved CTBCM_DR.
(m) Excess Output: Each Generator, Controllable Solar & Wind, Energy
Demand may in respect of each PPA CDGU (with/without PSODA) on
each day prior to the notice submission time submit to the NTDC a set
of generation or energy prices consistent with its PPA in respect of the
SDC-1 354
following Schedule Day; in case of CDGU this must be in relation to
output over and above the Contracted Capacity for the relevant
Declared Fuel or Designated Fuel.
The methodology of calculating the financial impacts of GSDPs revisions

requested by the Generator shall be sufficiently detailed in the
approved CTBCM_DR.
(n) A Generator must notify System Operator in writing in the form set out
in Appendix C of this SDC 1 as soon as it becomes aware, acting in
accordance with prudent operating practices, if (whether due to a
defect in the CDGU or in its associated Power Plant equipment) any of
its CDGUs is unable to meet the Spinning Reserve capability set out [in
the case of a PPA CDGU (with/without PSODA)] in the Sustained Load
Diagram attached to relevant Schedule of the Power Purchase
Agreement (PPA) and/or Power Station Operation & Dispatch Agreement
(PSODA) as applicable, and submitted pursuant to the Planning Code or
Connection Code or in the relevant applicable documents.
(o) Such notification must be made by submitting a GSDP Revision Notice

(Appendix C) in relation to item 2(c) of Appendix A to this SDC 1. In
accordance with the Generator's, Controllable Solar & Wind, Energy
Demand obligations under SDC 1.4.1.2(b), such reserve characteristics
may only be amended (with the System Operator's consent) in the
event of a defect in or failure of a CDGU, Controllable Solar & Wind,
Energy Storage Generating Unit, Aggregated Generating Unit,
Pumped Plant Demand or any associated Power Plant equipment. Such
amendment shall only take place so long as it takes place in accordance
with Prudent Operating Practices, legal requirements of the Power
Agreement (PSODA) as applicable for the relevant CDGU Controllable
Solar & Wind, Energy Storage Generating Unit, Aggregated
Generating Unit, Energy Storage Power Station Demand, Demand
Side Unit or Pumped Plant Demand or associated Power Plant
equipment to be repaired; and such repair must re-instate the Spinning
Reserve capability to its level stated in the GSDPs or to such other level
as the System Operator may propose acting in accordance with prudent
operating practices, and agree, taking into account the provisions of
SODC 1.4.1.2(a), and the Generator, Controllable Solar & Wind, Energy
Demand must then submit a GSDP Revision Notice re-declaring its re-
instated Spinning Reserve capability accordingly.
(p) The Generator, Controllable Solar & Wind, Energy Storage Generating
Unit, Aggregated Generating Unit, Energy Storage Power Station
Demand, Demand Side Unit or Pumped Plant Demand must specify
to the System Operator of the nature of any such. defect or its failure:
and of the Generator's, Controllable Solar & Wind, Energy Storage
Generating Unit, Aggregated Generating Unit, Energy Storage
Power Station Demand, Demand Side Unit or Pumped Plant
Demand best estimate, acting as a reasonable and prudent Generator,
Controllable Solar & Wind, Energy Storage Generating Unit,
Demand, Demand Side Unit or Pumped Plant Demand of the time it
SDC-1 355
shall take to complete the repair and restore the reserve characteristics
to their former Contracted levels.
SDC 1.4.5 The SO shall, insofar as it is reasonably able, take account of revisions or notifications
submitted under SDC1.4 for Scheduling and Dispatch purposes.
SDC 1.4.6 Form of Submission
a) Where this SDC1 requires a User to submit a notice, it may instead of

submitting it in writing, submit the information required in such a notice
(which information shall be supplied in full) by telephone subject to the
SO’s prior consent (identifying unambiguously the type of notice which is
thereby being submitted).
b) The individual who is giving the notice by telephone on behalf of the User
shall firstly specify the time at which the notice is being given, then identify
himself and ask the individual receiving the notice on behalf of the SO also
to identify himself. The information required by the notice shall then be
given, including (without limitation) the identity of the CDGU, Controllable
Solar, Wind & ESGUs, Energy Storage Power Station Demand, Aggregated
Generating Unit, Pumped Storage Plant and Demand Side Unit to
which the notice relates.
c) The notice shall then be confirmed by facsimile transmission or by any

electronic means as agreed with the SO as soon as possible thereafter (and
in any event be sent to the SO within 2 hours). Where a facsimile is so sent
by way of confirmation, it shall state clearly that it is in confirmation of a
notice already given by telephone and shall state the exact time at which
the notice was given by telephone.
SDC 1.4.7 Compilation of Indicative Operations Schedules
SDC 1.4.7.1 Indicative Operations Schedules will be compiled by the SO in conjunction with
the Other SO & Interconnector Operators as further provided in this SDC1.4.7
as a statement of which CDGUs and/or Controllable Solar, Wind & ESGUs
and/or transfers across any Interconnector and/or Demand Side Units and/or
Pumped Storage Plant Demand, Energy Storage Power Station Demand
and/or Aggregated Generating Units and equivalent units in Pakistan may be
required to operate and their expected MW Output. The SO in conjunction with
the Other SO & Interconnector Operators will periodically update the
Indicative Operations Schedules.
SDC 1.4.7.2 Merit Order
SDC 1.4.7.3 Subject as provided below, a Merit Order will be compiled by the SO (in
conjunction with the Other SO & IO) for each Imbalance Settlement Period of
the Schedule day from the Price Quantity Pairs, Start-Up Cost, Shutdown
Cost and No-Load Cost (which together shall be known as the “Price Set”) and,
subject as provided in this SDC1, used to determine which of the CDGUs,
Controllable Solar, Wind & ESGUs, Pumped Storage Plant Demand, Energy
Storage Power Station Demand, Demand Side Units, Aggregated
Generating Units or Interconnector power transfer to Schedule and Dispatch
in relation to their Price Sets at values that differ from those indicated by
Physical Notifications, as required to deliver the objectives set out in SDC1.2(a),
SDC1.2(b) and SDC1.2(c). The Merit Order for increasing MW Output above the
level indicated in Physical Notifications and Interconnector Schedule
Quantities will be on the basis of ascending prices so that the CDGU,
SDC-1 356
Storage Power Station Demand, Demand Side Unit, or Aggregated
Generating Unit Price Set or bid-offer data from an External System
Operator at the head of a Merit Order will be that which has the lowest price per
MWh, and that at the foot of a Merit Order shall be the one with the highest price
per MWh. Each CDGU, Controllable Solar, Wind & ESGUs, Pumped Storage
Plant Demand, Energy Storage Power Station Demand, Demand Side Unit,
Aggregated Generating Units and/or bid-offer data from an External System
Operator shall appear in the Merit Order for each Price Set submitted.
SDC 1.4.7.4 The Merit Order for dispatching MW Output to a level below that indicated in
Physical Notifications and Interconnector Schedule Quantities will be on the
basis of descending prices so that the CDGU, Controllable Solar, Wind &
ESGUs, Pumped Storage Plant Demand, Energy Storage Power Station
Demand, Demand Side Unit, Aggregated Generating Unit Price Set or bid-
offer data from an External System Operator at the head of a Merit Order will
be that which has the highest price per MWh, and that at the foot of a Merit
Order shall be the one with the lowest price per MWh. Each CDGU, Controllable
PPM, Pumped Storage Plant Demand, Energy Storage Power Demand,
Demand Side Unit, Aggregated Generating Units or bid-offer data from an
External System Operator shall appear in the Merit Order for each Price Set
submitted.
SDC 1.4.7.5 In compiling the Indicative Operations Schedules in conjunction with the Other
SO & IO, the SO will take account of the following factors (and the equivalent
factors on the Other Transmission System will be so treated separately by the
Other SO):
(i) Physical Notifications, Final Physical Notifications or Interconnector
Schedule Quantities (as the case may be) submitted in accordance with
SDC1.4.4.6;
(ii) Transmission System constraints from time to time, as determined by
the SO;
(iii) Reserve constraints from time to time, as determined by the SO;
(iv) The need to provide an Operating Margin (by using the various
categories of reserve as specified in OC.4.6 and CC.7.3.1.1 (as the case
may be), as determined by the SO acting in conjunction with the Other
SO;
(v) Transmission System stability considerations;
(vi) The level of MW Output and availability covered by Non
Centrally Dispatched Generating Units, by Plant
subject to Priority Dispatch and by Controllable
Solar, Wind & ESGUS;
(vii) The Energy Limits for Hydro Units;
(viii) The Energy Limits for ESPPS
(ix) In respect of all Plant, the values of their Technical Parameters

registered under this SDC1 and other information submitted under
SDC1.4.4.4;
(x) Commercial Offer Data for each CDGU and/or Controllable Solar,
Wind & ESGUS and Demand Side Unit and equivalent commercial data
provided by an External System Operator in respect of
Interconnectors;
(xi) The requirements, as determined by the SO, for Voltage Control and
Mvar reserves;
SDC-1 357
(xii) CDGU and/or Controllable Solar, Wind & ESGUS stability, as
determined by the SO;
(xiii) Other matters to enable the SO to meet its Licence Standards and the
Other SO to meet its equivalent;
(xiv) The requirements as determined by the SO, for maintaining Frequency

Control;
(xv) Monitoring and/or Testing and/or Investigations to be carried out, or
being carried out, under OC.10 (as the case may be), Testing to be carried
out, or being carried out, at the request of a User under OC.8 and/or
Commissioning Testing under the CC;
(xvi) System Tests, Operational Tests and Commissioning Tests;
(xvii) The inability of any CDGU and/or Controllable PPM to meet its full
reserve capability;
(xviii) Inter-jurisdictional Tie Line limits;
(xix) Other facts as may be reasonably considered by the SO

to be relevant to the Indicative Operations Schedule;
(xx) The inflexible characteristics as declared by the Generator and abnormal
risks;
(xxi) Losses on the Transmission System and on the Other Transmission
System;
(xxii) Requirements within any Constrained Group;

(xxiii) Any "Take or Pay" contract for the purchase of fuel to which a Generator
is a party, and the terms of which have been agreed to by the System
Operator and which impacts the National Transmission System, and/or
the terms of any other contract to which the System Operator is a party
of, and which may, in its opinion be relevant;
(xxiv) Factors used by the SO (and the Other SO) in order to comply with
Statutory Instruments, Statutory Regulations and/or the Licence which
may impact scheduling and Dispatch;
(xxv) factors used by the SO (and the Other SO) to comply with the objectives
in SDC1.2(g);
SDC 1.4.7.6 Taking account of and applying the factors referred to in SDC1.4.7.3, Indicative
Operations Schedules shall be compiled by the SO in conjunction with the Other
SO to schedule such CDGUs, Controllable Solar, Wind & ESGUs, Pumped
Storage Plant Demand, Energy Storage Power Station Demand, Demand
Side Units, Aggregated Generating Units and/or such Interconnector power
transfers, which have been declared Available in an Availability Notice (and the
equivalents on the Other Transmission System):
(i) in accordance with the applicable Merit Order;
(ii) as will in aggregate (after taking into account electricity delivered other
than from CDGUs, Controllable Solar, Wind & ESGUs, Aggregated
Generating Units, and/or Interconnector power transfers and variation
in Demand from Pumped Storage Plant Demand, Energy Storage
Power Station Demand and Demand Side Units) be sufficient to match
at all times (to the extent possible having regard to the Availability or
Demand Side Unit MW Availability of CDGUs, Controllable Solar,
Wind & ESGUs, Pumped Storage Plant Demand, Energy Storage
Power Station Demand, Demand Side Units, Aggregated
Generating Units and Interconnector power transfers) the forecast
SDC-1 358
aggregated Demand (derived under OC1 of the Grid Code and the Other
Grid Code) together with such margin of reserve as the SO working in
conjunction with the Other SO shall consider to be appropriate; and
(iii) as will in aggregate be sufficient to match minimum forecast Demand

levels together with a sufficient Minimum Demand Regulation.
The taking account of and application of the factors in SDC1.4.7.3 will mean
that, in general, strict adherence to Merit Order may not necessarily be
feasible.
SDC 1.4.7.7 Before issuing the Final IOS, the SO will periodically rerun the scheduling process
and issue revised Indicative Operations Schedules to take account of any of the
following factors (and the equivalent factors on the Other Transmission System
which will be so dealt with separately by the Other SO)
(a)Changes to Physical Notifications and Interconnector Schedule
Quantities, i.e. GSDPs of CDGUs notifications to the System Operator
after the commencement of the scheduling process;
(b) Changes to Commercial Offer Data [and bid-offer data from External
Transmission System Operators];
(c) Changes to Availability or Demand Side Unit MW Availability and/or Technical
Parameters of CDGUs and/or Controllable Solar, Wind & ESGUs and/or
Aggregated Generating Units and/or Interconnectors and/or Demand Side
Units notified to the SO;
(d) Changes to Demand forecasts on the Republic of Pakistan;
(e)Changes to resource forecasts on the Republic of Pakistan;
(f) Changes to Transmission System constraints, emerging from the necessarily
iterative process of Scheduling and network security assessment;
(g) Changes to CDGU and/or Controllable Solar, Wind & ESGUs requirements
following notification to the SO of the changes in capability of a Generator
to provide a Special Remedial Action as described in SDC2;
(h) Changes to CDGU and/or Controllable Solar, Wind & ESGUs requirements
within Constrained Groups, following re-appraisal of System Demand
forecasts on Republic of Pakistan within that Constrained Group;
(i) Changes to Monitoring and/or Testing and/or Investigations to be carried out, or
being carried out, under OC.10 (as the case may be), changes to testing to
be carried out, or being carried out, at the request of a User under OC.8
and/or Commissioning Testing under CC15;
(j) Changes to any conditions which in the reasonable opinion of the SO, would
impose increased risk to the Transmission System and would therefore
require an increase in the Operating Margin;
(k)Unexpected Outages of large Embedded Generators connected to the
distribution company's Systems after the commencement of scheduling
process.
(l) Unexpected Outages on major 132/66 kV transmission facilities of distribution,
Provincial and SPTLs companies.
(m) Known (or emerging) limitations and/or deficiencies of the Scheduling
process.
SDC 1.4.7.8 Factors to possibly cause amendment of Physical notifications by SO.
When:
(a) Adverse weather is anticipated;
(b) there is a high risk to the whole or part of the transmission system and/or the
other transmission system;
(c)Demand Control has been instructed by the SO; or
(d) A Total Shutdown or Partial Shutdown exists.
These factors may mean that a CDGU, Controllable Solar, Wind & ESGUs,
Pumped Storage Plant Demand, Energy Storage Power Station Demand,
Demand Side Unit, Aggregated Generating Unit and/or Interconnector
SDC-1 359
transfers is/are chosen other than in accordance with the profile described in
Physical Notifications (the Active Power profile derived from Interconnector
Schedule Quantities in respect of Interconnectors) and amended in line with
Merit Order to a greater degree than would be the case when merely taking into
account and giving due weight to the factors listed in SDC1.4.7.3 in order to seek
to maintain the integrity of the Transmission System.
SDC 1.4.7.9 The Synchronising and De-Synchronising times (and, in the case of Pumped
Storage Plant Demand and Energy Storage Power Station Demand, the relevant
effective time) shown in the Indicative Operations Schedule are indicative only and
it should be borne in mind by Users that the Dispatch Instructions could reflect
more or different CDGU, Aggregated Generating Unit and/or Controllable Solar,
Wind & ESGUs, Pumped Storage Plant Demand, Energy Storage Power Station
Demand and/or Aggregate Generating Unit requirements than in the Indicative
Operations Schedule. The SO may issue Dispatch Instructions in respect of any
CDGU and/or Aggregated Generating Unit, Controllable PPM, Pumped Storage Plant
Demand, Energy Storage Power Station Demand or Aggregated Generating Unit
which has not declared an Availability or Demand Side Unit MW Availability of 0 MW
in an Availability Notice. Users with CDGUs and/or Aggregated Generating Units,
Controllable Solar, Wind & ESGUs, Pumped Storage Plant Demand or Energy
Storage Power Station Demand shall ensure that their units are able to be
Synchronised, or in the case of Pumped Storage Plant Demand, used at the times
Scheduled, but only if so Dispatched by the SO by issue of a Dispatch Instruction.
Users shall, as part of a revision to the Technical Parameters, indicate to the SO the
latest time at which a Dispatch Instruction is required to meet the scheduled
Synchronising time or in the case of Pumped Storage Plant Demand or Energy
Storage Power Station Demand, the Scheduled relevant effective time.
SDC 1.4.7.10 The provisions of SDC1.4.7.7(a) shall apply to Demand Side Units with the
exception that reference to relevant effective time shall be read as a
reference to Demand Side Unit Notice Time.
SDC 1.4.7.11 Content of Indicative Operations Schedules
The information contained in the Indicative Operations Schedules will

indicate, where appropriate, on an individual CDGU, Controllable Solar, Wind
& ESGUs, Pumped Storage Plant Demand, Energy Storage Power Station
Demand, Demand Side Unit, Aggregated Generating Units and/or
Interconnector basis, the period and Loading for which it is Scheduled. In the
case of a CDGU which is capable of firing on two different fuels, it will also
indicate the fuel for which it is Scheduled. If no fuel is contained in the
Indicative Operations Schedule, then the most recently specified fuel shall be
treated as having been indicated.
SDC 1.4.7.12 Issue of Final Indicative Operations Schedules

(a) The Day Ahead Notification of Final IOS shall be issued in writing to
the Generator, Controllable Solar, Wind & ESGUs, Pumped Storage
Plant Demand, Energy Storage Power Station Demand, Demand
Side Unit, Aggregated Generating Units and/or Interconnector by
1700 hours each day, provided that all the necessary information from
the Generators Controllable Solar, Wind & ESGUs, Pumped Storage
Plant Demand, Energy Storage Power Station Demand, Demand
Side Unit, Aggregated Generating Units and/or Interconnector has
been made available by no later than the notice submission time.
SDC-1 360
However, if on any occasion, the System Operator is unable to meet
this time, the system Operator reserves the right to extend this time
scale for the issuance of Day Ahead Notification to the extent
necessary.
(b) The Day Ahead Notification received by each Generator Controllable
Solar, Wind & ESGUs, Pumped Storage Plant Demand, Energy
Storage Power Station Demand, Demand Side Unit, Aggregated
Generating Units and/or Interconnector shall contain information
relating to its Plant only.
(c) The initial Indicative Operations Schedule for a Trading Day will be
published for access by Users by xxxx hours on the Trading Day
preceding the relevant Trading Day. However, if on any occasion the SO
is unable to meet this time, the SO also reserves the right to extend the
timescale for the issue of the Indicative Operations Schedules to the
extent necessary. Following the issue of the initial Indicative Operations
Schedule preceding the relevant Trading Day, the SO will periodically
issue revised Indicative Operations Schedules to reflect updated
information from the scheduling process.
(d) Indicative Operations Schedules issued by the SO may comprise
several schedules covering short term, medium term or long term
timeframes where long term covers the period up to 48 hours immediately
following real time.
(e) The SO may issue Dispatch Instructions to Users in respect of CDGUs,
Controllable Solar, Wind & ESGUs, Pumped Storage Plant Demand,
Energy Storage Power Station Demand and/or Demand Side Units
and/or Aggregated Generating Units and/or Interconnector power
transfers before the issue of the initial Indicative Operations Schedule
for the Trading Day to which the Dispatch instruction relates if the
Synchronous Start Up Time for the relevant CDGUs and/or
Controllable Solar, Wind & ESGUs, Pumped Storage Plant Demand,
Energy Storage Power Station Demand and/or Demand Side Unit
and/or Aggregated Generating Unit requires the Dispatch instruction
to be given at that
time. When the length of the time required for Notice to Synchronise is
within 30 minutes of causing the CDGU and/or Controllable Solar, Wind
& ESGUs and/or Pumped Storage Plant Demand and/or Energy
Storage Power Station Demand to be unable to meet the indicative
Synchronising time in the Indicative Operations Schedule or a
subsequent indicative Synchronising time and no Dispatch Instruction
has been received, the Generator shall inform the SO without delay.
SDC 1.4.7.13 Minimum Demand Regulation (MDR)
It is a requirement for running the Transmission System that all Synchronised

CDGUs and/or Controllable Solar, Wind & ESGUs shall at all times be capable
of reducing MW Output sufficient to allow a sufficient Regulating Margin for
adequate Frequency Control. The SO will monitor the MW Output data of the
Final Indicative Operations Schedule against forecast of System Demand on
the Republic of Pakistan to see whether the level of regulation for any period is
sufficient, and may take any shortfall into account in Scheduling and Dispatch
process.
SDC 1.4.7.14 Data Requirements
SDC1 Appendix A Part 1 sets out the Technical Parameters for which values are
to be supplied by a User in respect of each of its CDGUs and/or Controllable
Solar, Wind & ESGUs and/or Pumped Storage Plant Demand and/or Demand
Side Units and/or Energy Storage Power Station Demand and/or
SDC-1 361
Aggregated Generating Units by not later than Schedule Day for the relevant
Trading Day.
SDC1 Appendix A Part 2 sets out the additional data items required in respect of an
Additional Grid Code Characteristics Notice.
SDC-1 362
SDC 1.5 Verification of Contract Fulfilment
The System Operator shall be responsible for the enforcement of the PSODA with the
Generators. The System Operator shall also be responsible for the verification of
contract fulfilment for the purpose of account settlement. The System Operator shall
prepare a report of all dispatch transactions with the exact time and amount of
power delivered to the network; and amount of power delivered to the Code
Participants and other Users. A separate report shall be prepared by the System
Operator for the ancillary services provided to the National Transmission System.
For the purpose of Verification, the System Operator shall provide accurate active
and reactive power measuring instruments at the Points of Connection between
transmission system and Code Participants. For billing purposes and account
settlement, the System Operator shall provide revenue metering at the Points of
Connection, as specified in the Protection and Metering Code. The information shall
be collected by the System Operator SCADA System and communicated to the
System Operator/ as appropriate.
The System Operator has the sole authority to Schedule and Dispatch generation,
manage and discipline a secure and safe operation of the National Transmission
System. The Code Participants who are contracted to supply generation power
supplies must comply with the dispatch instructions of the System Operator, in
totality, regardless of their circumstances or prevailing conditions. Any Failure of
Code Participant to comply with dispatch instructions of the System Operator shall be
subject to penalties, in accordance with the provisions of the Grid Code under Code
Management sub-code.
System Operator shall oversee compliance and impose penalties, if necessary.

NEPRA shall consider failure to comply with the System Operator's dispatch
instruction as an infraction to the Power Purchase Agreement (PPA) and/or Power
Station Operation & Dispatch Agreement (PSODA), and shall use the available
information to evaluate continued eligibility of respective NEPRA licence of the Code
Participant/User of NTDC's Transmission System.
System Operator shall notify the Code Participant, Review Panel, and NEPRA of each
infraction not agreed to by the offending Code Participant/User in writing,
immediately. If there is a justified cause for the infraction, the Code Participant must
reply in writing to SO Review Panel, and NEPRA within seven (7) days after receiving
the infraction notice. Review Panel/NEPRA shall review justification submitted by the
offending Code Participant within seven (7) days from the receipt of the letter of
justification. Review Panel/NEPRA shall accept or reject the justification and issue
their final adjudication including imposition of penalties, if any.
SDC-1 363
APPENDIX A- (SCHEDULING AND DISPATCH CODE NO.1)
Generation Scheduling and Dispatch Parameters (GSDPs)
A. For each CDGU:
1. (a) in the case of steam turbine CDGUs, synchronising times for the various levels
of warmth;
(b) in the case of gas turbine CDGUs, the time from initiation of a start to
achieving dispatched load.
2. Basic data:
(a) Minimum Generation in MW;
(b) Governor Droop (%);
(c) Sustained Response Capability.
(d) Available reactive power generation both leading and lagging, in Mvar
3. Two shifting limitation (limitation on the number of Start-ups per schedule day);
4. Minimum on time;
5. Block load following synchronisation in MW;
6. Maximum loading rates for the various levels of warmth and for up to two output
ranges;
7. Maximum de-loading rates for up to two output ranges;
8. The MW and MVAr capability limits within which the CDGU is able to operate as
shown in the relevant Generator Performance Chart;
9. Maximum number of changes to the dispatched fuel per 24 hour period;
10. Maximum quantity of oil in "ready-use tank(s)" and associated pipe work;
11. Maximum number of changes to the designated fuel per 24 hour period;
12. Minimum notice to change the designated fuel;
13. Maximum number of on load cycles per 24 hour period, together with the maximum
load increases involved; and
14. Settings of the Unit Load Controller for each CDGU for which a Unit Load Controller
is required under CC7.5.5.;
15. in the case of gas turbine CDGUs only, the declared peak capacity.
In the case of a Gas Turbine Unit, only the data applicable to Gas Turbine Units should be
supplied.
B. For the Power Plant of which the CDGU forms part:
1. Time between synchronising different CDGUs in a power plant taking account of

actual off-load periods for the various levels of warmth; and
2. Time between de-synchronising different CDGUs in a Power Plant.
SDC-1 364
APPENDIX B- (SCHEDULING AND DISPATCH CODE N0.1)- POWER PLANT – DAILY
SCHEDULING NOTICES
FACSIMILE
TO : System Operator Control Centre, xxxxxxxxxx, xxxxxxxxx Page 1 of 4
FAX :
FROM :
POWER PLANT – DAILY SCHEDULING NOTICES
1. AVAILABILITY NOTICE
The availability of each CDGU at ( ) Power plant for the schedule day to which this notice
refers is shown on page 2 attached
2. ENERGY BID PRICE NOTICE (Rs/MWHr • enter bid price where appropriate)
( Power Limited) offers NTDC the following energy prices (which are lower than the
contracted prices) for the schedule Day to which this notice refers.
(Fuel) (Fuel)
(Fuel) (Fuel)
(Fuel)
3. GSDP NOTICE
The Generation Scheduling and Dispatch Parameters for each CDGU at ( ) Power Plant for
the Schedule Day to which this notice refers are as given in Schedule 1 of the relevant Power
Purchase Agreement {PPA) or Power Station Operation & Dispatch Agreement (PSODA)
YES / NO (Delete as appropriate)
(If NO, each GSDP which varies from Schedule 1 must be shown on page 3 attached
If YES, page 3 shall be omitted)
4. OTHER GENERATION RELEVANT DATA
5. DECLARATION
These notices are issued by ( Power Limited) in respect of the Centrally Dispatched
Generating Units (CDGUs) at ( ) Power Plant in accordance with the requirements of
SDC 1.
We declare that the figures and other information given in the notices fully reflect the actual
capability of the CDGUs
The notices are applicable lo Schedule Day:
SDC-1 365
Signature Name
Position: Commercial Engineer/ Control Engineer (delete as applicable)
Date/Time of issue:
SDC-1 366
AVAILABILITY NOTICE
Page 2 of 4
Settlement (UNITS ON OIL) (UNITS ON GAS) GAS TURBINES

Period REDUCTION
1 2 1 2 1 2
Contracted
Capacity
0000 – 0030 _______ _______ _______ _______ _______ _______
0030 – 0100 _______ _______ _______ _______ _______ _______
0100 – 0130 _______ _______ _______ _______ _______ _______
0130 – 0200 _______ _______ _______ _______ _______ _______
0200 – 0230 _______ _______ _______ _______ _______ _______
0230 – 0300 _______ _______ _______ _______ _______ _______
0300 = 0330 _______ _______ _______ _______ _______ _______
0330 – 0400 _______ _______ _______ _______ _______ _______
0400 – 0430 _______ _______ _______ _______ _______ _______
0430 – 0500 _______ _______ _______ _______ _______ _______
0500 – 0530 _______ _______ _______ _______ _______ _______
0530 – 0600 _______ _______ _______ _______ _______ _______
0600 – 0630 _______ _______ _______ _______ _______ _______
0630 - -0700 _______ _______ _______ _______ _______ _______
0730 – 0800 _______ _______ _______ _______ _______ _______
0800 – 0830 _______ _______ _______ _______ _______ _______
0830 – 0900 _______ _______ _______ _______ _______ _______
0900 – 0930 _______ _______ _______ _______ _______ _______
0930 – 1000 _______ _______ _______ _______ _______ _______
1000 – 1030 _______ _______ _______ _______ _______ _______
1030 – 1100 _______ _______ _______ _______ _______ _______
1100 – 1130 _______ _______ _______ _______ _______ _______
1130 – 1200 _______ _______ _______ _______ _______ _______
1200 – 1230 _______ _______ _______ _______ _______ _______
1230 – 1300 _______ _______ _______ _______ _______ _______
1330 – 1400 _______ _______ _______ _______ _______ _______
1400 – 1430 _______ _______ _______ _______ _______ _______
1430 – 1500 _______ _______ _______ _______ _______ _______
1500 – 1530 _______ _______ _______ _______ _______ _______
1530 – 1600 _______ _______ _______ _______ _______ _______
1600 – 1630 _______ _______ _______ _______ _______ _______
1630 – 1700 _______ _______ _______ _______ _______ _______
1700 – 1730 _______ _______ _______ _______ _______ _______
1730 – 1800 _______ _______ _______ _______ _______ _______
1800 – 1830 _______ _______ _______ _______ _______ _______
1830 – 1900 _______ _______ _______ _______ _______ _______
1900 – 1930 _______ _______ _______ _______ _______ _______
1930 – 2000 _______ _______ _______ _______ _______ _______
2000 – 2030 _______ _______ _______ _______ _______ _______
2030 – 2100 _______ _______ _______ _______ _______ _______
2100 – 2130 _______ _______ _______ _______ _______ _______
2130 – 2200 _______ _______ _______ _______ _______ _______
SDC-1 367
2200 – 2230 _______ _______ _______ _______ _______ _______
2230 – 2300 _______ _______ _______ _______ _______ _______
2300 – 2330 _______ _______ _______ _______ _______ _______
2330 – 2400 _______ _______ _______ _______ _______ _______
SDC-1 368
GSDP NOTICE Page 3 of 4
Power Limited! declares that the undermentioned CDGUs are presently unable to perform to the
characteristics stated in [Schedule 1 of the relevant Power Purchase Agreement (PPA) or Power
Station Operation & Dispatch Agreement (PSODA)j and that the affected characteristics are
mentioned below with revised values that should be used for the purposes of Scheduling and
Dispatch.
GENERATION SCHEDULING AND CONTRACTED REVISED TIME

UNIT DISPATCH PARAMETER AFFECTED VALUE VALUE FROM TO
Examples
1 Governor Droop 4% 4.5% 0000 2400 2

Loading Rate after Hot Start 300+ MW 6.0 2.5 1800 2200
This notice is applicable to schedule day:
Signature:
SDC-1 369
Page 4 of 4
Notes
1. All Availabilities shall be expressed in MW. Alongside the MW figure shall be placed the unit
operating status (in brackets) as defined by the Final Generation Outage Programme: 1 = Normal
Availability, 2 = Inflexible Outage, 3 = Flexible Planned Outage, 4 = Advanced Flexible Planned
Outage, 5 = Deferred Flexible Planned Outage, 6 = Short Term Planned Maintenance Outage, 7 =
Return to Service, 8 = Notified Unplanned Outage, 9 = Forced Outage.
2. For each CDGU, an Availability figure must be entered for the first settlement period. Where the
CDGU is completely unavailable, a zero shall be entered. Thereafter, an Availability figure shall
only be entered where the Availability for the CDGU is changed from the previously expressed
value.
3. This Availability Notice shall include all planned Outages agreed with NTDC and all
Unplanned/Forced Outages already notified to NTDC. It shall not include Unplanned/Forced
Outages not yet notified to NTDC unless the appropriate Outage Notice is attached.
SDC-1 370
APPENDIX C (SCHEDULING AND DISPATCH CODE 1)- GSDP REVISION NOTICE
Page 1 of 1
FACSIMILE
TO/FROM System Operator Control Centre, xxxxxxxx, xxxxxxxxxxxxxxxxxxxx
FAX [ ]
FROM/TO [ Power Limited]
GSDP REVISION NOTICE
___________________________________________________________________________________
POWER PLANT REQUEST
Power Limited] advises System Operator that the GSDPs mentioned below for the following CDGUs
are not in accordance with Schedule 1 of the relevant Power Purchase Agreement (PPA) or
Power Station Operation & Dispatch Agreement (PSODA) and, as a result, the CDGUs shall be
unable to meet their Spinning Reserve capability.
ESTIMATED
CONTRACTED REVISED START DURATION
UNIT ID GSDP AFFECTED VALUE VALUE DATE TIME HRS
______ _____________ ________ ________ _______ _______ ______

______ _____________ ________ ________ _______ _______ ______
______ _____________ ________ ________ _______ _______ ______
______ _____________ ________ ________ _______ _______ ______
______ _____________ ________ ________ _______ _______ ______
______ _____________ ________ ________ _______ _______ ______
______ _____________ ________ ________ _______ _______ ______
______ _____________ ________ ________ _______ _______ ______
Reason for Change
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
Signature ___________________________ Name ______________________________
(in block capitals)
Position: Commercial Engineer/Control Engineer (delete as applicable)
Date/Time of issue ________________________
____________________________________________________________________________________
SDC-1 371
APPENDIX D (SCHEDULING AND DISPATCH CODE 1)- NOTIFICATION OF REVISED
AVAILABILITY
Page 1 of 1
NOTIFICATION OF REVISED AVAILABILITY
Settlement (UNITS ON OIL) (UNITS ON GAS) GAS TURBINES

Period 1 2 1 2 1 2
Contracted
Capacity
0000 – 0030 _______ _______ _______ _______ _______ _______

0030 – 0100 _______ _______ _______ _______ _______ _______
0100 – 0130 _______ _______ _______ _______ _______ _______
0130 – 0200 _______ _______ _______ _______ _______ _______
0200 – 0230 _______ _______ _______ _______ _______ _______
0230 – 0300 _______ _______ _______ _______ _______ _______
0300 = 0330 _______ _______ _______ _______ _______ _______
0330 – 0400 _______ _______ _______ _______ _______ _______
0400 – 0430 _______ _______ _______ _______ _______ _______
0430 – 0500 _______ _______ _______ _______ _______ _______
0500 – 0530 _______ _______ _______ _______ _______ _______
0530 – 0600 _______ _______ _______ _______ _______ _______
0600 – 0630 _______ _______ _______ _______ _______ _______
0630 - -0700 _______ _______ _______ _______ _______ _______
0730 – 0800 _______ _______ _______ _______ _______ _______
0800 – 0830 _______ _______ _______ _______ _______ _______
0830 – 0900 _______ _______ _______ _______ _______ _______
0900 – 0930 _______ _______ _______ _______ _______ _______
0930 – 1000 _______ _______ _______ _______ _______ _______
1000 – 1030 _______ _______ _______ _______ _______ _______
1030 – 1100 _______ _______ _______ _______ _______ _______
1100 – 1130 _______ _______ _______ _______ _______ _______
1130 – 1200 _______ _______ _______ _______ _______ _______
1200 – 1230 _______ _______ _______ _______ _______ _______
1230 – 1300 _______ _______ _______ _______ _______ _______
1330 – 1400 _______ _______ _______ _______ _______ _______
1400 – 1430 _______ _______ _______ _______ _______ _______
1430 – 1500 _______ _______ _______ _______ _______ _______
1500 – 1530 _______ _______ _______ _______ _______ _______
1530 – 1600 _______ _______ _______ _______ _______ _______
1600 – 1630 _______ _______ _______ _______ _______ _______
1630 – 1700 _______ _______ _______ _______ _______ _______
1700 – 1730 _______ _______ _______ _______ _______ _______
1730 – 1800 _______ _______ _______ _______ _______ _______
1800 – 1830 _______ _______ _______ _______ _______ _______
1830 – 1900 _______ _______ _______ _______ _______ _______
1900 – 1930 _______ _______ _______ _______ _______ _______
1930 – 2000 _______ _______ _______ _______ _______ _______
2000 – 2030 _______ _______ _______ _______ _______ _______
2030 – 2100 _______ _______ _______ _______ _______ _______
2100 – 2130 _______ _______ _______ _______ _______ _______
2130 – 2200 _______ _______ _______ _______ _______ _______
2200 – 2230 _______ _______ _______ _______ _______ _______
SDC-1 372
2230 – 2300 _______ _______ _______ _______ _______ _______
2300 – 2330 _______ _______ _______ _______ _______ _______
2330 – 2400 _______ _______ _______ _______ _______ _______
Notes:
1 AR Availabilities shall be expressed in MW. Alongside the MW figure shall be placed the unit
operating status (in brackets) as defined by the Final Generation Outage Programme: 1 = Normal
Availability, 2 = Inflexible Planned Outage, 3 = Flexible Planned Outage, 4 = Advanced Flexible
Planned Outage, 5 = Deferred Flexible Planned Outage, 6 = Short Term Planned Maintenance
Outage, 7 = Return to Service.
2 For each CDGU. an Availability figure shall be entered in respect or the relevant settlement
period(s) where the Availability of the CDGU is changed from a value notified previously in an
Availability Notice. Where the change in Availability occurs otherwise than at the commencement
of an Availability period, an appropriate annotation must be made, stating the exact time or the
change. If the CDGU is unavailable, a zero shall be entered.
This notice is applicable to schedule day:
Signature: _______________________________________
SDC-1 373
APPENDIX E (SCHEDULING AND DISPATCH CODE 1)- FACSIMILE
Page 1 of 1
FACSIMILE
TO System Operator Control Centre, xxxxxxxx, xxxxxxxxxxxxxxxxxxxx

FAX [ ]
FROM [ ]
POWER PLANT· DAILY SCHEDULING NOTICES
1 AVAILABILITY NOTICE
The Availability of each CDGU for the schedule day to which this notice refers is shown on page 2
attached.
2 ENERGY BID PRICE NOTICE [£.x.xxxx/GJ - enter bid price where appropriate)
[______________ ] offers the following energy prices (which are lower than the contracted prices) for the
week commencing the Monday following this notice.
(Fuel)
3 GSDP NOTICE
The Generation Scheduling and Dispatch Parameters for each CDGU al [ ] Power plant for the
schedule day to which this notice relies are as given under Contracted Operating Characteristics in
the respective Schedule of the relevant Power Purchase Agreement (PPA) or Power Station
Operation & Dispatch Agreement (PSODA)
YES/ NO (Delete as appropriate)
(It NO, each GSDP which varies from Schedule 1 contracted operating characteristics must be on page
3 attached. If YES page 3 shall be omitted)
4 OTHER GENERATION RELEVANT DATA

___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
5 DECLARATION
These notices are issued by [ ] in respect of the Centrally Dispatched
Generating Units (CDGUs) and Ranges at [ l Power Plant in accordance with the
requirements
of SDC 1
We declare that the figures and other information given in the notices fully reflect the actual
capacity of the CDGUs and Ranges.
The notices are applicable to schedule day: _______________________ _
Signature ______________________ Name ______________________________
(in block capitals)
SDC-1 374
APPENDIX F (SCHEDULING AND DISPATCH CODE 1)- NOTIFICATION OF REVISED
AVAILABILITY
Page 1 of 1
FACSIMILE
NOTIFICATION OF REVISED AVAILABILITY
1. [ ] POWER PLANT NOTIFICATION
[ ] hereby notifies the System Operator that the Availability of the undermentioned CDGU(s) is/are
not in accordance with that declared in the current Availability/Range Availability Notice
and is/are being redeclared as shown below:
UNIT DECLARED REVISED VALID

RANGE/ID MW/MW(e) MW/MW(e) FROM TO
_________ _________ _________ _________ _________

_________ _________ _________ _________ _________
_________ _________ _________ _________ _________
_________ _________ _________ _________ _________
_________ _________ _________ _________ _________
_________ _________ _________ _________ _________
Note: where Availability is being increased, the time to be slated for the
increase to take effect shall be slated in accordance with the Grid Code.
Reason for Change

____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
_________________________________________________________________________________
This notice confirms the telephone notice issued at ______ (insert time of telephone notice, if
applicable). If this notice contradicts the information given in the telephone notice it shall be
disregarded and NTDC shall so inform the Generator.
Signature ______________________ Name ______________________________
(in block capitals)
SDC-1 375
APPENDIX G (SCHEDULING AND DISPATCH CODE 1)- SCHEDULING DATA: PARTICIPATING
GENERATORS
Page 1 of 2
PART 1
UNIT NOMINATIONS
Name of Participating Generator
Name of Generating Unit
Date on which Scheduling Day Commences
Local Unit Nomination (SDC 1.4.2.3C (c))
Settlement Unit
Period Nomination
(Totals)
Start End (kWh)
06.00 06.30
06.30 07.00
07.00 07.30
07.30 08.00
08.00 08.30
08.30 09.00
09.00 09.30
09.30 10.00
10.00 10.30
10.30 11.00
11.30 12.00
12.00 12.30
12.30 13.00
13.00 13.30
13.30 14.00
14.00 14.30
14.30 15.00
05.00 05.30
05.30 06.00
SDC-1 376
APPENDIX G Page 1 of 2
(SCHEDULING AND DISPATCH CODE 1)
PART 2
SUPPLEMENTAL ENERGY BIDS
1. Name of participating Generator
2. Name of Generating Unit
3. Date on which Scheduling Day commences
4. Supplemental Energy Bid for Scheduling Day Start Up Price (Rs.)
Fixed Price (Rs./hour)
Incremental Price (Rs./MWh or Rs./kWh)
SDC-1 377
APPENDIX H: MARKET DEVELOPMENT AND THE IMPLEMENTATION OF CTBCM
1. Security Constrained Economic Dispatch
2. Inputs to SCED
3. Implementation of SCED by the System Operator
4. Frequency
5. Price Validation
6. Manual Dispatch
7. Method of Payment
8. Interaction between the Independent Auction Administrator and the System Operator
9. System Operator and the Planning Function
SDC-1 378
Upon implementation of the CTBCM some new concepts will be introduced by the System Operator. One of
the largest changes will be the implementation of SCED (Security Constrained Economic Dispatch) by the
System Operator. SCED is a simplified optimal power flow problem that is widely used internationally. In its
most simple variation, it consists of two solutions for each time horizon, namely an unconstrained
economic dispatch that does not consider certain constraints, such as losses or congestion, and a second
solution that explicitly accounts for network security constraints. The System Operator will use SCED to
dispatch resources on the grid.
1. Security Constrained Economic Dispatch.
2. Inputs to SCED
The NPCC will implement Security Constrained Economic Dispatch
All power plants will be required to stipulate whether they are dispatchable (subject to centralized Security
Constrained Economic Dispatch by the System Operator) or non-dispatchable (e.g. small run of river hydro,
etc.). This information will be stored in a static data repository database so it can be accessed by different
systems.
The NPCC may designate certain units as Reliability-Must-Run (RMR) units and those units will have
heightened scheduling responsibilities in that their schedules should be arranged with the NPCC given the
special status of their units. These RMR units will be identified based on system studies undertaken by the
NPCC and shared with the relevant parties, if need be under the auspices of a non-disclosure agreement.
Dispatchable generators are required to submit three-part bids based on the characteristics of the
generator, namely, start-up cost, minimum load cost, and an economic bid profile. These are all variable
generation costs.
Any units that are part of an aggregate will also submit transition costs that represent the fuel cost of the
transition zone.
Non-dispatchable units will submit schedules of their expected generating profile.
Variable energy resources, such as wind and solar, will submit forecasts of their expected output.
Demand resources such as discos will submit their load profile
All entities will submit this data set for a rolling seven-calendar-day window every single day so that the
System Operator always seven days of data available and it has sufficient visibility into issues as they
arise.
3. Implementation of SCED by the NPCC
Every day the System Operator will perform congestion analysis taking into account outages on the
transmission system, generator outages, as well as any other events that may affect the congestion
pattern on the high-voltage grid, such as international transactions for example. Thereafter the System
Operator will detail the initial conditions under which it analyses the congestions, such as the fact that
some units may already be online and need not be started within the daily horizon. The formation of initial
conditions can either be done manually in a simplified model or be populated from SCADA/State Estimator
when those applications are producing data of sufficient quality to support these applications and
processes. Armed with the initial conditions, the state of the network model, the generation and load
profiles of the various entities on the Pakistani grid the NPCC will perform the Security Constrained
Economic Dispatch such that it meets the load requirement on a least cost basis and that the dispatch is
based on the variable cost of generation, with no heed paid to the fixed costs by the dispatch algorithm.
The NPCC will use specialized software for this task but failing that it will perform this analysis manually
and daily. In each case it will save the scenarios it generates for After-The-Fact (ATF) analysis.
4. Frequency
The NPCC will perform the SCED process a minimum of twice for each operating day. The initial event will
be in the day-ahead time frame, meaning it will release the proposed schedule and pricing details for each
SDC-1 379
operating day the day before at a time that it stipulates and posts on its website, such as 4PM every day
for example. This will be the day-ahead run and the results will be indicative, but not financially binding.
Starting not more than two hours before midnight every day the System Operator will run the SCED once
an hour for each hour of the operating day. These schedules and prices will be binding and the published
schedules will be communicated to the responsible entities either electronically or telephonically if need
be, for the binding interval, as well as any non-binding informational intervals after the binding interval as
determined by the NPCC to be necessary. The results of each SCED run, including all of the advisory runs,
dispatch instructions, scheduling levels, marginal pricing for each run, and any other pertinent information
will be stored electronically by the SO and will be made available to other entities to allow for planning
analyses, financial settlement etcetera.
The timing of the runs, the run horizon of each SCED run, the nature of the binding and advisory
instructions, and the method of communication, will all be specified by the NPCC in its Standard Operating
Procedure for SCED under CTBCM. This SOP will be public and available on the NPCC website.
In addition, the System Operator will initiate a public website on which it will publish pertinent data relating
to prices, quantities, congestion analysis etcetera. No less often than once a year the NPCC will solicit
public comments on its publication procedures and it will take and address comments that are submitted
and publish a record of the comments received and addressed.
The responsibility of the NPCC will be to implement the new SCED associated with the CTBCM, capture all
information submitted and used by the SO to populate the SCED, the SCED results, and any other relevant
data points that are necessary to ensure that dispatch occurs according to the agreed upon rules, and that
settlement by other entities is possible. Data capture, storage and transmission will be the direct
responsibility of the System Operator. Any data points that are either discarded or overwritten must be
captured in the SOP of the NPCC and published to adjacent entities so that other entities that are
dependent on the activities of the SO for their own procedures know exactly what data is available and
what data is not being kept.
5. Price Validation
The SCED algorithm will produce marginal prices for every hour of every day. This price will not influence
all settlement as much of the settlement pricing is based on contract pricing not market pricing. In some
cases, however, such as the Contract Balancing Mechanism operated by the CPPA-G, this price may be
relevant. The NPCC will publish initial prices at its discretion for every hour and will assist other entities in
validating those prices after-the-fact. Any changes to published marginal prices must occur within seven
calendar days of operation.
6. Manual Dispatch
It is likely there will be occasions when the SCED instructions will not be able to account for grid conditions
due to forced outages or other grid events. In these cases, the System Operator will issue manual
dispatches immediately, and will, as soon as practicably possible, adjust the parameters of the SCED
algorithm so that it reflects the new grid conditions. The manual dispatches will be transmitted to the
relevant entities electronically and the System Operator will record the pertinent details, such as the
quantities, reason, and time in the System Log (SysLog). The System Log will be made available to all
entities that have a demonstrable need, such as the CPPA-G, and all changes to the System Log will be
captured as revisions, not deletions for audit purposes.
7. Method of Payment
When the SCED is running on a regular basis, the NPCC will not directly participate in the financial
settlement function; however, it will be responsible for providing information and data to wholesale entities
and adjacent governmental institutions to ensure correct settlement.
8. Interaction between the Independent Auction Administrator and the NPCC
The Independent Auction Administrator will be responsible for centralized procurement of new capacity
until such stage as the DISCOs can perform this function independently. The NPCC will assist by;
SDC-1 380
Provide the long-term least cost based indicative generation capacity expansion plan and the least cost
transmission system expansion plan, as well as any other plans and complementary reports needed for the
centralized procurement.
9. NTDC and the Planning Function
Under CTBCM the planning functionality will migrate to the System Operator (NPCC) specifically, rather
than the NTDC more broadly. The Planner will be responsible for the preparation of the long-term, least-
cost, Indicative Generation Capacity Expansion Plan (IGCEP) and the development of the least-cost
Transmission System Expansion Plan, which will be mandatory in contents and timing. These plans will
take due consideration of power plants under construction and with signed PPAs, international
interconnections and demand information provided by DISCOs, K-Electric and Bulk Power Consumers. The
Planner will produce annual updates of both expansion plans concerning congestion, optimal location
analysis, effect on dispatch costs and supply, delays in investment, system security constraints, and
measures to address delays and unforeseen events. The IGCEP and the TSEP will be publicly posted once
approved by NEPRA.
End of SDC 1
SDC-1 381
SCHEDULING AND DISPATCH CODE NO. 2 (SDC 2)
CONTROL SCHEDULING AND DISPATCH
CONTENTS
SDC 2.2 OBJECTIVE.................................................................................................... 389
SDC 2.3 SCOPE.......................................................................................................... 389
SDC 2.4 PROCEDURE................................................................................................. 390
SDC 2 -APPENDIX A- Dispatch Instructions for CDGUs................................................. 400
SDC-1 382
SDC 2 CONTROL SCHEDULING AND DISPATCH CODE NO. 2
CONTROL SCHEDULING AND DISPATCH
In the daily functioning of the National Transmission and Dispatch Company's business,
scheduling, dispatch and control of generation facilities shall be performed by the
System Operator. The Control Scheduling and Dispatch Code (SDC 2) defines the
roles and responsibilities of the System Operator and Code Participants in the
dispatch and control scheduling of Available generation facilities, and operation
and management of a secure bulk Transmission System of NTDC.
SDC 2.1.1 Scheduling and Dispatch Code No. 2 ("SDC 2") sets out the procedures for the
System Operator to issue dispatch instructions to Generators in respect of their
CDGUs (in relation to their Unit Nominations) as per "Final Generation Schedule"
concluded in SDC 1. This sub-code is supplemental to SDC 1 and SDC 3.
SDC 2.1.2 CTBCM Provisions

(a) This Scheduling and Dispatch Code No. 2 ("SDC2") forms part of the
Sections under Common Governance of the Grid Code. The Sections
under Common Governance are those parts of the Grid Code which are
under common governance in both the Grid Code and the Other Grid
Code.
(b) The form of this SDC2 is similar to the SDC2 in the Other Grid Code.
Differences relate to references to relevant power systems and related
terms. Where there is a difference between a provision in this Grid Code
and an equivalent provision in the Other Grid Code, the wording in
question is shaded in grey. In addition, those parts of this SDC2 that are not
part of the Other Grid Code are shaded in grey in this SDC2. Differences
between the form of this SDC2 and the SDC2 in the Other Grid Code are
summarised in Annex 1 to this SDC2.
(c) This SDC2 is intended to work in conjunction with other documents,
including the CTBCM Design Report (“CTBCM_DR”). The provisions of
the Grid Code and the Other Grid Code will take precedence over the
CTBCM_DR.
(d) Where stated in this SDC2, the obligation to submit data in relation to some
of the information required to be provided to the SO by this SDC2 may be
fulfilled by Users where such information submitted under the CTBCM_DR
by a User or by an Intermediary on behalf of Users is then provided to
the SO by the Market Operator in accordance with the CTBCM_DR, as
further provided in this SDC2. The SO may require Users to verify or
update data received by it via the Market Operator (MO).
(e) Dispatch Instructions issued pursuant to this SDC2 may be utilised for
settlement in respect of Generating Units, Controllable Solar, Wind &
ESGUs, Pumped Storage Plant Demand, Energy Storage Power
Station Demand, Demand Side Unit, Aggregated Generating Unit
and/or Interconnector which have been registered in accordance with the
CTBCM_DR.
(f) Further provisions dealing with the Sections under Common
Governance are contained in the General Conditions.
SDC 2.1.3 SDC2 sets out the procedure for the SO to issue Dispatch Instructions to:
(a) Generators in respect of their CDGUs (which for the avoidance of doubt
comprise, Generating Units subject to Central Dispatch, CCGT
Installations, Hydro Units, Pumped Storage Generation and
Controllable Solar, Wind & ESGUs);
SDC-1 383
(b) Pumped Storage Generators in respect of their Pumped Storage
Plant Demand;
(c) Energy Storage Generators in respect of their Energy Storage Power
Station Demand;
(d) Interconnector Owners in respect of their Interconnectors;
(e) Demand Side Unit Operators in respect of their Demand Side Units;
and
(f) Generator Aggregators in respect of their Aggregated Generating
Units.
Controllable Solar, Wind & ESGUs are not currently subject to
Dispatch Instructions. However, remote signals sent by the SO to
Controllable Solar, Wind & ESGUs in order to limit Active Power
Output may be utilised by the SO as Dispatch Instructions in
accordance with the CTBCM_DR.
SDC 2.2 OBJECTIVE
The Objectives of the Control Scheduling and Dispatch Code (SDC 2) are to establish the
process, guidelines and procedures for:
(a) Principles and criteria for dispatch

(b) Minimizing overall cost of supply
(c) Steps to be taken to prepare a dispatch algorithm
(d) Accounting for bilateral contracts
(e) Establishment of a Merit Order Ranking
The procedures for the issuance of dispatch instructions to Generating Units,
Storage Power Station Demand, Demand Side Unit, Aggregated Generating
Unit and/or Interconnector by the System Operator is intended to enable (as far
as possible) the System Operator to match continuously, utilising the Merit Order
and "Final Indicative Operation Schedule" derived pursuant to SDC 1, and the
factors to be taken into account listed in SDC 1 (SDC 1.4.3.3), CDGUs and/or
Controllable Solar, Wind & ESGUs and/or Pumped Storage Plant Demand
and/or Demand Side Units and/or Energy Storage Power Station Demand and/or
Aggregated Generating Units output to NTDC total system demand, taking into
account any power transfers over any External Interconnections, DISCOS,
Provincial and SPTLs companies, and non-CGDU output together with an
appropriate Operating Margin whilst maintaining the integrity and security of the
NTDC's System coupled with the requirements of adequacy and quality of power
supply as provided in this Grid Code.
The Security Constrained Economic Dispatch (SCED) algorithm is sed to process

the information and fulfilled the five SDC2 criteria. SCED is described in Appendix
H.
SDC 2.3 SCOPE
SDC 2 applies to the System Operator, and to the Code Participants with regard to their
Generating Plants.
(a) Generators with regard to their CDGUs;

(b) Pumped Storage Generators with regard to their
Pumped Storage Plant Demand;
(c) Energy Storage Generators with regard to their
Energy Storage Power Station Demand;
(d) Interconnector Owners with regard to their Interconnectors;
(e) Demand Side Unit Operators in relation to their Demand Side Units;
and
SDC-1 384
(f) Generator Aggregators in respect of their Aggregated Generating
Units.
Each of which (other than the SO) is a “User” under this SDC2.
SDC 2.4 PROCEDURE
SDC 2.4.1 Information Used

SDC 2.4.1.1 The information which the System Operator shall use in assessing as to which
CDGU, Demand Side Unit, Interconnector transfers, Pumped Storage Plant
Demand and/or Energy Storage Power Station Demand and/or Aggregated
Generating Units to Dispatch, to dispatch, shall be the followings:
a) Availability Notice;
b) Unit Nominations;
c) Merit Order as derived under SDC 1;
d) Other factors to be taken into account as listed in SDC 1 (SDC 1.4.3.3);
e) Generation Scheduling and Dispatch Parameters
(GSDPs);
f) Operating Reserve Characteristics, and;
g) Other Generation Relevant Data in respect of that CDGU, Demand Side
Unit, Interconnector transfers, Pumped Storage Plant Demand and/or
Energy Storage Power Station Demand and/or Aggregated Generating
Units, supplied to it under SDC 1 (and any revisions under SDC 1 and this
SDC 2 to the date).
SDC 2.4.1.2 Subject as provided below, the factors used in the dispatch phase in assessing
which CDGU, Demand Side Unit, Interconnector transfers, Pumped Storage
Plant Demand and/or Energy Storage Power Station Demand and/or
Aggregated Generating Units to dispatch in conjunction with the Merit Order
as derived under SDC 1, and the other matters identified in SDC 1.4.3, SDC
1.4.3.3 and SDC 1.4.3.5 and SDC 1.4.3.6 shall be those used by the System
Operator to compile the Generation Schedule under SDC 1.
SDC 2.4.1.3 Additional factors which the System Operator shall, however, also take into
account are those CDGU, Demand Side Unit, Interconnector transfers,
Pumped Storage Plant Demand and/or Energy Storage Power Station
Demand and/or Aggregated Generating Units:
a) who have not complied with dispatch instructions or;
b) "special actions requests" which the System Operator has (in its absolute
discretion) granted for the early synchronisation of a CDGU, Demand Side
Unit, Interconnector transfers, Pumped Storage Plant Demand and/or
Energy Storage Power Station Demand and/or Aggregated Generating
Units to the NTDC System;
c) requests which System Operator has made and to which the CDGU,
Demand Side Unit, Interconnector transfers, Pumped Storage Plant
Demand and/or Energy Storage Power Station Demand and/or
Aggregated Generating Units has agreed to for an early or late
synchronisation of a CDGU, Demand Side Unit, Interconnector transfers,
Demand and/or Aggregated Generating Units to the NTDC's National
Power System; and
d) variation between forecasted and actual NTDC system demand, as these
can have an impact on the overall dispatch. T
e) the need by System Operator to account for dispatching of CDGU,
Aggregated Generating Units for monitoring, testing or investigation
purposes under OC 11, or for testing at the request of a User, under OC
11.2.
SDC-1 385
SDC 2.4.1.4 In the event of two or more CDGU, Demand Side Unit, Interconnector
transfers, Pumped Storage Plant Demand and/or Energy Storage Power
Station Demand and/or Aggregated Generating Units having the same
"Merit Order Price Set", the System Operator not being able to differentiate on
the basis of the factors identified in SDC 1.4.3.2, SDC 1.4.3.3 and SDC 1.4.3.4,
the System Operator shall select for dispatch both Units as the case may be,
as input in the Security Constrained Economic Dispatch (SCED) procedure.
SDC 2.4.1.5 Following Final Generation Schedule, Users may no longer submit or amend
Physical Notifications, Interconnector Schedule Quantities or Commercial
Offer Data in respect of Imbalance Settlement Periods for which the Final
Generation Schedule has occurred (subject to SDC1.4.4.6(d)). Notwithstanding
SDC1.4.7, the SO will continue to rerun the scheduling process and issue
Indicative Operations Schedules.
SDC 2.4.2 Dispatch instructions

SDC 2.4.2.1 Introduction
Dispatch instructions relating to the Schedule Day shall normally be issued at any time during
the period beginning immediately after the issuance of the Day Ahead
Notification preferably with effect from 00.01 hrs (midnight). In respect of that
Schedule Day. The System Operator may, however, at its discretion, issue
dispatch instructions in relation to a CDGU, Demand Side Unit,
Interconnector transfers, Pumped Storage Plant Demand and/or Energy
Storage Power Station Demand and/or Aggregated Generating Units prior
to the issuance of the Day Ahead Notification which includes that CDGU,
Demand and/or Energy Storage Power Station Demand and/or Aggregated
Generating Units.
SDC 2.4.2.2 Issue of Dispatch Instructions
The System Operator shall issue dispatch instructions direct to:
(a) the Generator for the Dispatch of each of its CDGUs.

(b) the Generator Aggregator for the Dispatch of its Aggregated
Generating Units.
(c) the Energy Storage Generator for the Dispatch of its Energy Storage
Power Station Demand.
(d) the Demand Side Unit Operator and the Pumped
Storage Demand User in respect of each of their
Demand Side Units and Pumped Storage Plant
Demand respectively.
(e) the Interconnector Owner for the Dispatch of the
Interconnector transfers.
(f) The SO may issue Dispatch Instructions for any CDGU, Demand Side Unit,
Storage Power Station Demand and/or Aggregated Generating Units which
has been declared Available in an Availability Notice even if that CDGU,
Demand Side Unit, Interconnector transfers, Pumped Storage Plant Demand
and/or Energy Storage Power Station Demand and/or Aggregated
Generating Units was not included in an Indicative Operations Schedule at
the Day ahead Notification.
SDC 2.4.2.3 Scope of Dispatch Instructions for CDGUs

In addition to instructions relating to the dispatch of Active Power, dispatch instructions
(unless otherwise specified by the System Operator at the time of giving the
SDC-1 386
dispatch instructions) shall be deemed to have included an automatic
instruction of Spinning Reserve, and voltage/reactive support, the level of
which is to be provided in accordance with Declared Spinning Reserve
Availability under the SDC1 and the Ancillary Service Agreement.
SDC 2.4.2.4 In addition to instructions relating to the dispatch of Active Power, dispatch
instructions in relation to CDGU, Demand Side Unit, Interconnector transfers,
Demand and/or Aggregated Generating Units. may include:
a) Target (at instructed MW level) voltage levels at the Points of Connection

or the individual reactive power output at the Generating Units terminals
which shall be maintained by the CDGU, Demand Side Unit,
Storage Power Station Demand and/or Aggregated Generating Units .
b) The issue of dispatch instructions for Active Power at the Generating Unit
terminals shall be made with due regard to any resulting change in
reactive power capability, and may include instruction for reduction in
Active Power generation to increase reactive power capability.
c) In the event of a sudden change in the System Operator's system
voltage, a Generator must not take any action in respect of any of its
CDGU, Demand Side Unit, Interconnector transfers, Pumped Storage Plant
Aggregated Generating Units to override automatic MVAr response
unless instructed otherwise by the System Operator or unless immediate
action is necessary to comply with voltage/stability limits. A Generator
may take such action, as is in its reasonable opinion necessary, to avoid
an imminent risk of injury to persons or material damage to property
(including the CDGU, Demand Side Unit, Interconnector transfers,
Demand and/or Aggregated Generating Units );
d) The Fuel in a Thermal Plant:
1. Where the declared fuel to be used by the Generator in operating
the Thermal plant CDGU units must be declared by the Generator
ahead of scheduling.
2. In the case of a CDGU capable of firing on different fuels, the
dispatch instruction may also specify the designated fuel to be
used by the Generator. If no declared fuel and/or, where relevant,
Designated Fuel is contained in the dispatch instruction, then the
most recently instructed Dispatched Fuel and/or, where relevant,
designated fuel shall apply. The part of a dispatch instruction which
specifies a change in the dispatched fuel and/or, where relevant,
designated fuel to be burned by the Generator shall be known as a
"Dispatched Fuel Notice". The System Operator may, however, use
a separate dispatched fuel notice and which may be issued
separately from any dispatch instruction, containing the above
information.
3. In the case of an existing CDGU only, the Generator may (subject to
the following provisions of this paragraph, in complying with a
dispatch instruction) burn a fuel other than the Declared Fuel
and/or, where relevant, the Designated Fuel specified in the
dispatch instruction.
e) A reference to any implications for future dispatch requirements and the

security of the NTDC's National Transmission System, including
arrangements for change in output to meet post-fault security
requirements;
SDC-1 387
f) Special Protection scheme: An instruction to switch into or out of service
a "System to CDGU" lntertripping scheme;
g) Time to synchronise: Notice and changes in notice to synchronise or de-
synchronise CDGUs CDGUs and, where appropriate Demand Side Units
and/or Energy Storage Power Stations in relation to Energy Storage Power
Station Demand and/or Pumped Storage Plants in relation to Pumped
Storage Plant Demand and time to react for Demand Side Units in a
specific time scale;
h) Instructions relating to abnormal conditions, such as adverse weather
conditions, or high or low NTDC System voltage;
i) An instruction for a change in Generator step-up transformer tap
positions;
j) An instruction for a CDGU to operate in synchronous compensation mode;
k) An instruction in relation to the carrying out of testing, monitoring or
investigations as required under OC 11, or testing at the request of a
User under OC 11.2.
l) Peak Instruction: In the case of a Gas Turbine PPA CDGU, an instruction
requiring it to generate at a level in excess of its Availability but not
exceeding its temperature adjusted peak capability which may only be
given if, at the time of issue of the instruction, the CDGU is dispatched to
an output equal to its Availability, and provided that the limit on the
number of hours for which such instructions may be given during the year
(as agreed with the relevant Generator) is not thereby exceeded. Such an
instruction shall be identified as a "peak instruction". When the System
Operator gives a dispatch instruction which is in excess of the Availability
of the gas turbine, the CDGU which is not designated a "peak instruction",
the Generator must inform the System Operator immediately that the
dispatch instruction is so in excess in order that the System Operator can
so designate the dispatch instruction as a "peak instruction" or withdraw
the instruction completely. The Generator shall not then be obliged to
comply with the dispatch instruction unless and until the System
Operator notifies it that the instruction is designated as a "peak
instruction".
m) Cycle Operating Mode: in the case of a CCGT Installation, an instruction
specifying the Cycle Operating Mode and/or an instruction to Dispatch a
CCGT Installation in Open Cycle Mode. The Generator must then ensure
that the CCGT Installation achieves the new Dispatched Operating Mode,
without undue delay, in accordance with the CCGT Installation’s declared
Availability and declared Technical Parameters. Dispatch Instructions in
relation to Cycle Operating Modes issued by the SO shall reflect the
applicable Availability Notice and Technical Parameters;
n) Pumped Storage: mode changes for Pumped Storage Plants, where
contracted, in relation to Pumped Storage Plant Demand;
o) Energy Storage Power Station: mode changes for ESPS, where contracted,
in relation to Energy Storage Power Station Demand;
p) Dispatch Instruction Test Flags: Dispatch Instruction Test Flags shall be
applied to Dispatch Instructions in respect of new or amended test
proposals submitted by a Generator after Final Generation Schedule has
already occurred for the relevant Imbalance Settlement Periods (since
Final Physical Notifications cannot be amended) and the Generator
could not have reasonably foreseen the need for the new or amended test
request before Final Generation Schedule for the relevant Imbalance
Settlement Period. The Dispatch Instruction Test Flag shall be applied
to the portion of the Dispatch Instruction which diverges from Physical
Notifications submitted by a Generator in respect of a test proposal which
has been approved by the SO. The part of a Dispatch Instruction subject
SDC-1 388
to the flag will not be deemed to be a Dispatch Instruction for settlement
purposes;
SDC 2.4.2.5 Reactive Support for Voltage Control
Reactive support for necessary voltage control shall be provided by each CDGUs, Generator
Aggregators and, where appropriate Demand Side Units and/or Energy
Storage Power Stations in relation to Energy Storage Power Station
Demand and/or Pumped Storage Plants in relation to Pumped Storage
Plant Demand and time to react for Demand Side Units with due regards to
manufacturer's specifications of design characteristics of the individual
aforementioned Unit. In addition to instructions relating to the Dispatch of
Active Power, Dispatch Instructions in relation may include:
(a) Mvars: the individual Reactive Power output from Generator

Aggregators and, where appropriate Demand Side Units and/or
Energy Storage Power Stations in relation to Energy Storage Power
Station Demand and/or Pumped Storage Plants in relation to Pumped
Storage Plant Demand and time to react for Demand Side Units at the
Units Terminals or Voltage levels (at instructed MW level) at the
Connection Point which will be maintained by the CDGUs and, where
appropriate Demand Side Units and/or Energy Storage Power
Stations in relation to Energy Storage Power Station Demand and/or
Pumped Storage Plants in relation to Pumped Storage Plant
Demand and Demand Side Units and Interconnectors.
(b) The issue of Dispatch Instructions for Active Power will be as at the
Connection Point and will be made with due regard to any resulting
change in Reactive Power capability and may include instruction for
reduction in Active Power generation to increase Reactive Power
capability, according to Addenda 1, 2 and 3 and Other technical Codes.
(c) In the event of a sudden change in System voltage a Generator,
Generators Aggregators, Demand Side Units, Energy Storage
Power Stations in relation to Energy Storage Power Station and/or
Pumped Storage Plants and Demand Side Units must not take any
action in respect of any of their Units to override automatic Mvar response
unless instructed otherwise by the SO or unless immediate action is
necessary to comply with stability limits. A Generator may take such
action as is in its reasonable opinion necessary to avoid an imminent risk
of injury to persons or material damage to property (including the CDGU).
SDC 2.4.2.6 Form of Instruction

(a) Instructions may be given by telephone, by facsimile transmission, by
instructor or by radio/telephone. These may be given electronically where
a relevant communication system has been established between the
System Operator and a Generator, Generators Aggregators, Demand
Side Units, Energy Storage Power Stations, Pumped Storage Plants
and Demand Side Units . In the case of a In the case of a Special
Protection Scheme, a Low Frequency Relay or any other automatic
Primary Frequency Control scheme (excluding governor response) low-
frequency relay initiated response from a Gas Turbine CDGU, Demand
Side Unit, and/or Pumped Storage Plant in relation to Pumped Storage
Plant Demand and/or Energy Storage Power Station in relation to
Energy Storage Power Station Demand, the instruction shall be deemed
to be given at the moment that the low frequency relay operates.
(b) The reduction by a Generator, Generators Aggregators, Demand Side

Units, Energy Storage Power Stations, Pumped Storage Plants and
SDC-1 389
Demand Side Units of the output of one of its Generator, Generators
Aggregators, Demand Side Units, Energy Storage Power Stations,
Pumped Storage Plants and Demand Side Units under SDC 3.6.1 shall
be deemed to have followed a dispatch instruction issued by the System
Operator.
(c) In addition, the System Operator may notify a Generator, Generators

Pumped Storage Plants and Demand Side Units that in certain
circumstances it requires the Generator to operate in accordance with a
Standing Instruction, which shall be deemed to be given when the
circumstances arise. These Standing Instructions may include instructions
on how to operate if the System Operator loses the ability to direct the
operation and management of the NTDC's Transmission System
temporarily, in the circumstances envisaged under OC 8 where the
System Operator or the Control Centre (NPCC) is incapacitated for any
reason pending the transfer of system operations to a temporary Control
Centre. The System Operator shall not, by means of a Standing
Instruction, require any of the Generator, Generators Aggregators,
Demand Side Units, Energy Storage Power Stations, Pumped Storage
Plants and Demand Side Units to be dispatched in a manner in which
the System Operator would not have access or be able to exercise option
to require such units to be dispatched by means of a dispatch instruction
issued in accordance with this SDC 2.
(d) The de-synchronisation of a Generator, Generators Aggregators,

Plants and Demand Side Units following the operation of an interim
scheme selected by the System Operator shall be deemed to have
happened as a result of a dispatch instruction issued by the System
Operator.
SDC 2.4.2.7 Target Frequency

(a) Dispatch instructions given by telephone, by facsimile transmission or
electronically shall generally indicate the target MW (at Target System
Frequency) to be provided at the Generator terminals (or where provided
in the relevant Connection Agreement, on the energy sent out basis) and
to be achieved in accordance with the respective CDGU's Technical
Parameters and/or parameters as provided in the Additional Grid Code
Characteristics Notices provided under SDC1 or this SDC2, or such rate
within those parameters as is specified by the SO in the Dispatch
Instructions
(b) Dispatch instructions given by the SO shall indicate the target MW (at
Target System Frequency) to be provided at the Generator terminals of
the each Generator Generating Unit, Generators Aggregator, each
Demand Side Units, each Energy Storage Power Stations, each Pumped
Storage Plants to which the operator relates (or where provided in the
relevant Connection Agreement, on energy sent out basis), in the case of
a Power Plant which has an Operator for each Generator Generating Unit,
Generators Aggregator, each Demand Side Units, each Energy Storage
Power Stations, each Pumped Storage Plants .
(c) Dispatch instructions deemed to be given upon the Operation of a low
frequency relay shall be deemed to indicate the target MW (at System
Target Frequency), which may either be at full load or at some lower
output (as previously specified by the System Operator), to be provided at
the Generator terminals which reflects; and is in accordance with the
SDC-1 390
GSDPs of Gas Turbine CDGUs GSDPs given as under or revised in
accordance with SDC 1 or SDC 2.
(d) Dispatch instructions deemed to be given upon the activation of a
Standing Instruction shall be deemed to indicate the target MW (at Target
System Frequency), which may either be at full load or at some lower
output {to be provided at the Generator terminals (or where provided in
the relevant Connection Agreement, on the energy sent out basis) as set
out in the Standing Instruction notified by the System Operator from time
to time; to be achieved in accordance with the respective GSDPs given
under ( or as revised in accordance with) SDC 1 or this SDC 2, or such rate
within those parameters as is specified in the Standing Instruction.
SDC 2.4.2.8 The form, manner, and the terms to be used by System Operator in issuing
dispatch instructions together with their meanings are set out in the attached
appendices.
(a) Subject only to SDC 2.4.2.8, and as provided below in the SDC 1 and SDC
2, dispatch instructions shall not be inconsistent with the Availability, Unit
Nominations, Contracted GSDPs, and Other Generation Relevant Data
notified to the System Operator under SDC 1 (and any revisions under
SDC 1 or this SDC 2 to that data).
(b) A dispatch instruction may be subsequently cancelled or varied (including
an instruction for a cancelled start) at any time.
(c) The dispatch instructions may, however, be inconsistent with the
Availability and/or Unit Nominations and/or GSDPs and/or Other
Generation Relevant Data so notified to the System Operator for the
purposes of carrying out a test at the request of the relevant Generator
under OC 12.3 or a system test at the request of the relevant Generator
under OC 11.2, to the extent that such dispatch instructions are
consistent with the procedures agreed (or otherwise determined) for
conducting the test or system test (as the case may be).
(d) For the avoidance of doubt, any dispatch instructions issued by the
System Operator for the purposes of carrying out a test at the request of
the relevant Generator under OC 12.3 or a system test at the request of
the relevant Generator under OC 11.2 shall not be deemed to be dispatch
instructions given pursuant to SDC 2 4 .2 .10.
(e) The De-Synchronisation of a CDGU following the operation of a Special
Protection Scheme selected by the SO shall be deemed to have happened
as a result of a Dispatch Instruction issued by the SO.
SDC 2.4.2.9 To preserve the NTDC's Transmission System integrity under emergency
circumstances where licence standards and obligations cannot be met, the
System Operator may, however, issue dispatch instructions to change CDGU
output even when this is an outside parameter so registered or so amended.
This may, for example, be an instruction to trip a CDGU or to part-load a CDGU.
The instruction shall be stated by the System Operator to be one in relation to
emergency circumstances under SDC 2.4.2.10.
SDC 2.4.2.10 Communication with Generators

i. A Generator must, at the beginning of each shift at its Power Station,
contact the System Operator by telephone; and the Operator at the Power
Station and the System Operator must exchange names in order to
identify each other. If during the shift at the Power Station, the Operator
changes, the Person whose Operator has changed must notify the other
accordingly.
ii. Dispatch instructions whether given by telephone, by facsimile
transmission or by Operator must be formally acknowledged immediately
SDC-1 391
by the Generator at the Power Station by telephone, by return facsimile
transmission or by acceptance of the dispatched signal, given in the
manner agreed between the Generator and the System Operator or a
reason must be given as soon as possible for non-acceptance, which may
(subject to SDC 2.4.2.10) only be to avoid, in the Generator's reasonable
opinion, an imminent risk of injury to persons or material damage to
property (including the CDGU) or because they are not in accordance with
the applicable Availability Notice, or GSDPs or do not reflect "Other
Generation Relevant Data" submitted by the Generator pursuant to SDC 1.
iii. In the event that in carrying out the dispatch instructions, an unforeseen
problem arises, leading to a possibility of, in the Generator's reasonable
opinion, to an imminent risk of injury to persons or material damage to
property (including the CDGU), the System Operator must be notified as
soon as possible by telephone.
iv. When issuing Notice to Synchronise to Generators in respect of their
Generating Units, the SO shall recognise the applicable heat state of each
relevant Generating Unit at the proposed Synchronisation effective time
and facilitate the synchronous start up time applicable to that heat state as
indicated by the Generator in the Technical Parameters supplied for the
Generating Unit.
SDC 2.4.2.11 Action Required from Users

(a) Each Users shall comply in accordance with SDC 2.4.2.13 and their Power
Purchase Agreement (PPA) or Power Station Operation & Dispatch
Agreement (PSODA) as applicable with all dispatch instructions properly
given by the System Operator unless the Generator, Generators
Aggregators, Demand Side Units, Energy Storage Power Stations, Pumped
Storage Plants and Demand Side Units has given a notice to System
Operator under the provisions of SDC 2.4.2.10 regarding non-agreement
of dispatch instructions.
(b)A Users shall not, however, be in default in complying with the dispatch
instructions, if, subsequent to the issuance of the dispatch instruction, the
Users and the System Operator agree on an early or late synchronisation,
and the Users synchronises the relevant Generator, Generators
Aggregators, Demand Side Units, Energy Storage Power Stations, Pumped
Storage Plants and Demand Side Units in accordance with that
agreement.
(c) Where the SO issues a Synchronising time to a Generator for a specific
CDGU, Generators Aggregators, Energy Storage Power Stations, Pumped
Storage Plants and Demand Side Units and the Generator identifies that
such CDGU will not be Synchronised within -15/+15 minutes of the
instructed time, the Generator must immediately (at the time the
discrepancy is identified) inform the SO of the situation and estimate the
new Synchronising time.
(d)When complying with Dispatch Instructions for a CCGT Installation a Generator
will operate its CCGT Units in accordance with the applicable CCGT
Installation Matrix.
SDC 2.4.2.12 Implementation of Instructions by Users
The Generators shall immediately respond to dispatch instructions properly given by the
System Operator without any delay in accordance with the instructions,
including those·dispatch instructions issued pursuant to SDC 2.4.2.10.
Instructions indicating· a target MW and Voltage/MVARS at that MW level and
an Output at the System Target Frequency shall be complied with by
Generators notwithstanding. any tolerance bands set out in their PPAs/PSODA.
It shall react by responding to that Dispatch Instruction given by the SO within
SDC-1 392
10 seconds. This set point must be reached in a time no greater than 10 seconds
plus the ramp rate for the Generation Unit, including those Dispatch
Instructions issued pursuant to SDC2.4.2.9. A tolerance will apply to the Dispatch
Instruction.
SDC 2.4.2.13 Manual local measures shall be allowed in cases where the automatic remote
control devices are out of service. The Active Power set point must be reached
within 1 hour. When a User has received a Dispatch Instructions for Mvars it will
respond to that Dispatch Instruction given by the SO within two minutes of the
instruction.
SDC 2.4.2.14 Subject to the exception set out below in thi·1s SDC 2.:4.2.14. the Generators
shall only synchronise or de-synchronise CDGUs to t1he dispatch instructions
of the System Operator or unless it occurs automatically as a result of intertrip
schemes or low-frequency relay operations.
SDC 2.4.2.15 De-synchronisation may otherwise only take place without the System
Operator's prior agreement if it is done to avoid, in the Generator's reasonable
opinion, an imminent risk of injury to persons or material damage to property
(including the CDGU) exists. It 1hatIf that happens, the System Operator must
be informed that it has done so within ten (10) minutes of the de-
synchronization of the Unit.
SDC 2.4.2.16 The System Operator may suspend the issuance of the dispatch instructions to
a particular Generating Unit in a plant in accordance with the Merit Order
(having taken account of and applied the factors referred to in SDC 1.4.3.3 to
the extent that the conditions in SDC 1.4-3.5 arise. When necessary, the
System Operator shall issue dispatch instructions for a Black Start.
SDC 2.4.2.17 User Plant Changes

(a) Each User at its control facility with multiple Generating Units shall,
without delay, notify the System Operator by telephone or by facsimile
transmission of any change or loss (temporary or otherwise) to the
operational capability of the Power Plant including any changes to the
Generation Scheduling and Dispatch Parameters (GSDPs) of each CDGU
(in the case of Generation Scheduling and Dispatch Parameters, by the
submission of a GSDP Revision Notice) indicating (where possible), the
magnitude and the duration of the change. In the case of CDGUs already
synchronised to the NTDC's Transmission System, the User at its Power
Plant must also state whether or not the loss was instantaneous.
SDC 2.4.2.18 Each Generator at its Power Plant shall operate its synchronised CDGUs with
AVRs and VAR limiters in service at all times (where required pursuant to
generator control arrangements contained in PPA/PSODA or Connection Code)
unless released from this obligation in respect of a particular CDGU by the
System Operator.
SDC 2.4.2.19 Minimum Demand Regulation ("MDR")
Synchronised centrally dispatched Generating Units must at all times be capable of reducing
Output sufficient to allow a sufficient Operating Margin for adequate frequency
control. The System Operator shall monitor the output data of the Indicative
Operation Schedule against forecasted NTDC's total system demand to see
whether the level of MDR for any period is insufficient; and may take any
shortfall into account in altering the dispatch.
SDC 2.4.2.20 Special Actions
The System Operator, may as part of the issuance of dispatch instructions, issue instructions
for special actions (either pre- or postfault) to a Generator in respect of any of
SDC-1 393
its CDGU, Generators Aggregators, Demand Side Units, Energy Storage
Power Stations, Pumped Storage Plants in the event that System Operator,
in its reasonable opinion, believes that such instructions are necessary in order
to ensure that the licence standards and obligations are met. Special actions
shall generally involve a Load change or a change in required Notice to
synchronise within a specific timescale on individual or groups of CDGU,
Generators Aggregators, Demand Side Units, Energy Storage Power
Stations, Pumped Storage Plants . They may also include selection of
"System to CDGU" intertrip schemes for stability or thermal reasons.
Instructions for special actions shall always be within Generation Scheduling
and Dispatch Parameters (GSDPs).
SDC-1 394
SDC 2 -APPENDIX A- Dispatch Instructions for CDGUs
SDC 2.A.1 Form of Dispatch Instruction

SDC 2.A.1.1 All loading/de-loading rates shall be assumed to be in accordance with
Generation Scheduling and Dispatch Parameters (GSDPs). Each dispatch
instruction shall, wherever possible, be kept simple, drawing as necessary from
the following forms and SDC 2.4.2.
SDC 2.A.1.2 (a)The dispatch instruction given by telephone, electronically or facsimile
transmission shall normally follow the form:
(i) The specific CDGU to which the instruction applies;
(ii) The Output to which it is instructed;
(iii) If the start time is different from the time the instruction is issued, the start
time shall be included;
(iv) Where specific loading/de-loading rates are concerned, a specific target time;
(v) The issue time of the instruction;
(vi) The Designated Fuel and/or declared fuel (or fuel), as the case may be;
(iii) In the case of a gas turbine CDGU, if the instruction is designated as a "Peak
Instruction", this shall be stated.
(b) The dispatch instruction given by Instructor shall normally follow the form:
(i) The specific CDGU to which the instruction applies, if the Instructor is on a unit
basis or the group of CDGUs to which the instruction applies;
(ii) The Output to which it is instructed.
Any dispatch instruction relating to the Designated Fuel and/or Declared Fuel, (or fuel) as the
case may be, shall be given by telephone, electronically or by facsimile
transmission.
SDC 2.A.2 Dispatching a Synchronised CDGU to Increase or Decrease Output

SDC 2.A.2.1 If the time of the dispatch instruction is 1400 hours, the unit is unit 1 and the
Output to be achieved is 205 MW, the relevant part of the instruction would be,
for example:
"Time 1400 hours. Unit 1 to 205 MW"
SDC 2.A.2.2 If the start time is 1415 hours, it would be, for example:
"Time 1400 hours. Unit 1·to 205 MW, start at 1415 hours"
SDC 2.A.2.3 Loading and de-loading rates are assumed to be in accordance with Generation
Scheduling and Dispatch Parameters (GSDPs) unless otherwise stated. If
different loading or de-loading rates are required, the time to be achieved shall
be slated, for example:
"Time 1400 hours. Unit 1 to 205 MW by 1420 hours"
SDC 2.A.3 Dispatching a CDGU to ·synchronise/de-Synchronise

SDC 2.A.3.1 CDGU Synchronising
SDC 2.A.3.1.1 In this instance, for CDGUs, the dispatch instruction issue time shall always
have due regard for the synchronising lime declared to System Operator by
the Generator as a GSOP.
The instruction shall follow the form, for example:
Time 1300 hours. Unit 1, Synchronise at 1600 hours"
SDC-1 395
In relation to an instruction to synchronise, the start time referred to in SDC
2.A.1.2(a) shall be deemed to be the time at which synchronisation is to take
place.
SDC 2.A.3.1.2 Unless a loading programme is also given at the same time it shall be assumed
that the CDGU(s) are to be brought to minimum generation level and on the
Generator reporting that the Generating Unit has been synchronised, a further
dispatch instruction shall be issued.
SDC 2.A.3.1.3 When a dispatch instruction for a CDGU to synchronise is cancelled (i.e. a
cancelled start) before the unit is synchronised, the instruction shall follow the
form, for example:
"Time 1400 hours. Unit 1, cancel synchronising instruction"
SDC 2.A.3.2 CDGUs De-Synchronising

SDC 2.A.3.2.1 The dispatch instruction shall normally follow the form, for example:
"Time 1300 hours. Unit 1, Shutdown".
If the instruction start time is for 1400 hours the form shall be. for example:
"Time 1300 hours. Unit 1, Shutdown, start at 1400 hours"
Both the above assume de-loading rate al declared Generation Scheduling

and Dispatch Parameters (GSDPs). Otherwise the message shall conclude
with, for example:
" .. and se-synchronise at 1 500 hours"
SDC 2.A.4 Frequency Control

SDC 2.A.4.1 All the above dispatch instructions shall be deemed to be at "Target System
Frequency" (50 Hz), i.e. where a CDGU is in the Frequency Sensitive Mode,
instructions refer to target Output at Target System Frequency. Target System
Frequency changes shall always be given to the Generator by telephone and
shall normally only be 49.95, 50.00, 50.05Hz (at an interval of 0.05 Hz).
SDC 2.A.4.2 CDGUs required to be frequency insensitive shall be specifically instructed as
such. The dispatch instruction shall be of the form for example:
"Time 2100 hours. Unit 1, to Frequency Insensitive mode"
SDC 2.A.4.3 Frequency control instructions may be issued in conjunction with, or separate
from, a dispatch instruction relating to Output.
SDC 2.A.5 Emergency Lo ad Drop
The dispatch instruction shall be in a pre-arranged format and normally follow the form, for
example:
"Time 2000 hours. Emergency load drop of "X"MW in "Y" minutes"
SDC 2.A.6 Voltage Control Instruction
In order that adequate NTDC Transmission System voltage limits as specified in OC 4 are
maintained under Normal and (N-1) conditions, a range of voltage control
instructions shall be utilised from time to time, for example:
(a) Operate to Nominal System Voltage as specified in OC 4.9;
(b) Maximum generation of reactive power (at current instructed MW output);
(c) Increase reactive output by 10MVAr (at current instructed MW output).
SDC 2.A.7 Instruction to change dispatched fuel
When the System Operator wishes to instruct a Generator to change the fuel being burned in
the Operation of one of its CDGUs from one Dispatched Fuel (or fuel) to
SDC-1 396
another (for example from 1 % sulphur oil to 3% sulphur oil), the dispatch
instruction shall follow the form, for example:
"Time 1500 hours. Unit 2 change to 3% Fuel at 1700 hours".
SDC 2.A.8 Instruction to change Designated Fuel for a Dual Firing CDGU
When the System Operator wishes to instruct a Generator to change the fuel being burned in
the operation of one of its CDGUs which is capable of firing on two different
fuels (for example, coal or oil), from one Designated Fuel (or fuel) to another
(for example, from coal to oil), the instruction shall follow the form, for
example:
"Time 1500 hours. Unit 1 generate using oil at 1800 hours".
SDC 2.A.9 Peak Instruction to Gas Turbine COG Us
When the System Operator wishes to instruct a Generator t\o operate its Gas Turbine PPA
CDGU at a level in excess of its Availability in accordance with SDC 2.4.2.4(j),
the instruction shall follow the form, for example:
"Peak Instruction. Time 1800 hours. Unit GT2 to 58MW.·
End of SDC 2
SDC-1 397
SCHEDULING AND DISPATCH CODE NO. 3 (SDC 3)
FREQUENCY CONTROL
CONTENTS
SDC 3.2 OBJECTIVE.................................................................................................... 404
SDC 3.3 SCOPE.......................................................................................................... 404
SDC 3.4 PROCEDURE................................................................................................. 404
SDC 3.5 ACTION REQUIRED BY GENERATORS IN RESPONSE TO LOW FREQUENCY..........406
SDC 3.6 ACTION REQUIRED BY GENERATORS IN RESPONSE TO HIGH FREQUENCY..........406
SDC 3.7 ELECTRIC TIME............................................................................................. 406
SDC-1 398
SDC 3 SCHEDULING AND DISPATCH CODE NO. 3
FREQUENCY CONTROL
All Generators (with/without Bilateral Contracts) shall have an obligation to meet their due
share of ancillary services including voltage and frequency control, operating
reserve both (spinning and non-spinning reserve), reactive support, load
imbalance services, black-start, system restoration, and load following
requirements. The different technical restrains for different types of power
plants shall be taken into consideration.
SDC 3.1.1 SDC 3 sets out the procedure by which the System Operator shall use to direct
frequency control. The NTDC System Frequency shall be controlled by:
(a) Automatic response from CDGUs operating in "Frequency Sensitive

Mode", including "Unit Load Controller Operation";
(b) The dispatch of CDGUs; and
(c) Load demand control.
SDC 3.1.2 The requirements for frequency control are determined by the consequences
and effectiveness of generation scheduling and dispatch; and by the effects of
power transfers across any External Interconnection; and therefore, SDC 3 is
supplemental to SDC 1 and SDC 2.
SDC 3.2 OBJECTIVE
The procedure for the System Operator to direct frequency control is intended to enable (as
far as possible) the System Operator to meet the requirements of frequency
control as contained in this Grid Code and NEPRA Transmission Performance
Standards.
SDC 3.3 SCOPE
SDC 3 applies to the System Operator, NTDC, Distributors, Generators with regard to their
Generating Units, Transmission-connected Consumers, and Externally-
connected Parties and Consumers.
SDC 3.4 PROCEDURE
SDC 3.4.1 Automatic Response from Generating Plant

(a) All CDGU, Generators Aggregators, Demand Side Units, Energy Storage
Power Stations, Pumped Storage Plants must, if technically possible, be
capable of operating at all times in Frequency Sensitive Mode (including,
where applicable, with the Unit Load Controller in Operation) which means
an automatic incremental or decremental generation response (Primary
Response) tlo contain the initial system frequency change together with a
sustained generation and load response (Secondary Response) which can
contribute to correcting and containing the system frequency within the
requirements for frequency control contained in this Grid Code and NEPRA
Transmission Performance Standards Rules.
(b) All synchronised CDGU, Generators Aggregators, Demand Side Units,
Energy Storage Power Stations, Pumped Storage Plants must, if
technically possible,, unless relieved of the requirement by the System
Operator, operate at all times in the Frequency Sensitive Mode (including,
where applicable, with the Unit Load Controller in Operation) except where,
in the Generator's reasonable opinion, it is necessary to cease operation in
Frequency Sensitive Mode in order to avoid an imminent risk of injury to
persons or material damage to property (including the CDGU, Generators
G&D 399
Pumped Storage Plants ) with the consent of the System Operator.
(c) The detailed instructions for droop settings and participation factor would
be given by the System Operator separately to the CDGU, Generators
Pumped Storage Plants for contribution towards frequency corrections. A
System Frequency induced change in the Active Power Output of CDGU,
Stations, Pumped Storage Plants which assists the recovery to Target
System Frequency must not be manually overridden by a Generator except
where it is necessary, in the Generator's reasonable opinion, to avoid an
imminent risk of injury to persons or material damage to property (including
the CDGU, Generators Aggregators, Demand Side Units, Energy
Storage Power Stations, Pumped Storage Plants ) with the consent of
SDC 3.4.1.1 Notwithstanding 3.4.1. (a), (b) and (c), changes must comply with technical
performances according to Addenda 1, 2 and 3 or the Contractual Agreement
with CDGU, Generators Aggregators, Demand Side Units, Energy Storage
Power Stations, Pumped Storage Plants
SDC 3.4.2 System operator's dispatch instructions

SDC 3.4.2.1 When the System Operator determines it is necessary, by having monitored the
NTDC System Frequency, it shall, as a part of the procedure set out in SDC 2,
issue dispatch instructions including the instructions for Spinning Reserve, in
order to regulate the NTDC System Frequency to meet the requirements for
frequency control as contained in the Grid Code, and NEPRA Transmission
Performance Standards Rules. The CDGU, Generators Aggregators, Demand
Side Units, Energy Storage Power Stations, Pumped Storage Plants to be
selected by the System Operator for Unit Load Controller Operation shall be
instructed by the System Operator to operate at the NTDC Target System
Frequency, which shall be 50.00 Hz.
SDC 3.4.2.2 Any dispatch instruction to CDGU, Generators Aggregators, Demand Side
Units, Energy Storage Power Stations, Pumped Storage Plants shall refer
only to the required CDGU, Generators Aggregators, Demand Side Units,
Energy Storage Power Stations, Pumped Storage Plants output al the
Target System Frequency.
SDC 3.4.3 Low frequency relay initiated response from Gas Turbine PPA CDGUs.
SDC 3.4.3.1 The System Operator may allocate a part of the requirements for Operating
Reserve to Gas Turbine PPA CDGUs or any other Generators Aggregators,
Plants with the capability of low frequency relay initiated response for start-
up to a pre-determined output level which have not been scheduled for
dispatch in accordance with SDC 1, although the System Operator may, in the
event, decide to issue a dispatch instruction in respect of any of such CDGU,
Stations, Pumped Storage Plants in accordance with SDC 2. Alternatively,
Gas Turbine PPA CSGUs of this type may be scheduled for dispatch by the
System Operator in accordance with SDC 1.
SDC 3.4.3.2 The System Operator shall periodically specify, within the range established
pursuant to the Connection Agreement, low frequency relay settings to be
applied to the CDGU, Generators Aggregators, Demand Side Units, Energy
Storage Power Stations, Pumped Storage Plants pursuant to SDC 3.4.3.1
and shall instruct the low frequency relay initiated response to be placed in
and out of service.
G&D 400
SDC 3.4.3.3 All Generators and Users/Code Participants shall comply with System Operator's
instructions issued under SDC 3.4.3.2 for low frequency relay settings. The
Generators, Generators Aggregators, Demand Side Units, Energy Storage
Power Stations, Pumped Storage Plants shall not alter such low frequency
relay settings or take low frequency initiated response out-of-service without
the System Operator authorization, except where necessary, in the CDGU,
Stations, Pumped Storage Plants 's reasonable opinion, to avoid an
imminent risk of injury to persons or material damage to property (including
the CDGU) with the authorization of the System Operator.
SDC 3.5 ACTION REQUIRED BY GENERATORS IN RESPONSE TO LOW FREQUENCY
SDC 3.5.1 If the NTDC System Frequency falls to or below 49.8 Hz, each Generator at its
Power Plant shall be required to check that each of its CDGU, Generators
Pumped Storage Plants is achieving the required levels of response
including that required from the Unit Load Controller, where applicable, in
order to contribute to containing and correcting the low System Frequency.
SDC 3.5.2 In order that the System Operator can deal with emergency conditions
effectively, it needs as much up-to-date information as possible and
accordingly, the System Operator shall be informed of the action taken as soon
as possible after the fall in the System Frequency directly by telephone from
the Power Plant.
SDC 3.6 ACTION REQUIRED BY GENERATORS IN RESPONSE TO HIGH

FREQUENCY
SDC 3.6.1 If the NTDC System Frequency rises to or above 50.2 Hz, each CDGU,
Stations, Pumped Storage Plants at its Power Plant shall be required to
ensure that each of its CDGU, Generators Aggregators, Demand Side Units,
Energy Storage Power Stations, Pumped Storage Plants s has responded
in order to contribute to correcting and containing the high System Frequency
by automatically or manually reducing output by a minimum amount of 2%
and by a maximum amount of 5% of Power Plant output per 0.1 Hz deviation of
the NTDC's System Frequency from declared or Target System Frequency.
SDC 3.6.2 This reduction shall have to be made without reference to the System Operator:
and must be maintained until the NTDC System Frequency has returned to
Target System Frequency or receipt of revised dispatch instructions from the
System Operator under SDC 2. In order that the System Operator can deal with
the emergency conditions effectively, it needs as much up-to-date information
as possible and accordingly, the System Operator must be informed of the
action taken as soon as possible after the rise in System Frequency directly by
telephone from the generating plant.
SDC 3.6.3 Notwithstanding 3.5 and 3.6, actions will be limited according to Addenda 1, 2
and 3 and/or any Contractual Agreement.
SDC 3.7 ELECTRIC TIME
SDC 3.7.1 The System Operator shall endeavour (in so far as it is able to) control electric
clock time to within plus or minus 10 seconds of Standard Time by specifying
changes to target the NTDC's System Frequency, and by dispatch taking into
account Merit Order and forecast Power Plant/Load Demand margins. Errors
greater than plus or minus 10 seconds may be temporarily accepted at the
System Operator's reasonable discretion. The System Operator shall give 15
minutes notice to each generator of variation in Target System Frequency.
G&D 401
End of SDC
G&D 402
GLOSSARY AND DEFINITIONS
The Terms Not Contained here have been Defined in Various Applicable Documents of NEPRA and
listed as Annexure-A (attached).
ITEM Sub-Code DEFINITION
24 Hour Recall SDC An Agreement [Power Purchase Agreement (PPA)/

Power Station Operation & Dispatch Agreement
(PSODA)] between NTDC and a Generator whereby a
CDGU subject to a Notified Unplanned Outage may be
recalled by NTDC upon giving a 24 hours Notice to the
Generator.
Active Energy PMC 2.1 The electrical energy produced, flowing or supplied by
an electrical circuit during a time interval, being the
integral with respect to time of the instantaneous
power, measured in units of watt- hours or standard
multiples thereof, i.e.:
1000Wh = 1 kWh
1000 kWh = 1 MWh
1000 MWh = 1 GWh
1000 GWh = 1 TWh
Active Load Limiter SDC 3 Device that does not allow a Generator to increase its
active power higher than established.
Active Power SDC 3.4.1.2 The product of voltage and the in-phase component of
alternating current measured in units of watts and
standard multiples thereof, i.e.:
1000 Watts = 1 kW
1000 kW = 1 MW
1000 MW = 1 GW
1000 GW = 1 TW
ASRAR OC Annual System Reliability & Assessment Report
Apparatus CC 5.4 Code All electrical equipment, conductor installed on the
Management electrical power system.
Apparent Power OC 4 The product of voltage and of alternating current
Appendix 7 measured in units of Volt-amperes and standard
multiples thereof, i.e.:
1000 VA = 1 kVA
1000 kVA = 1 MVA
Aggregated Demand Site A group of Individual Demand Sites represented by a
Demand Side Unit Operator, which together are
capable of a Demand Side Unit MW Capacity equal to or
above 10 MW (and which is therefore subject to Central
Dispatch from the TSO). Each Individual Demand Site
comprising an Aggregated Demand Site shall be in one
currency zone and shall have a Demand Side Unit MW
Capacity of no greater than 10 MW. Unless otherwise
specified, information submitted in respect of an
Aggregated Demand Site shall always be at an
aggregated
level.
G&D 403
A group of Generating Units represented by a

Generator Aggregator, each of which must not have a
Registered Capacity greater than 10 MW. An
Aggregated Generating Unit with a total Registered
Aggregated Generating Capacity of 4 MW or more shall be subject to Central
Unit Dispatch, but one with a total Registered Capacity of
less than 4 MW may be subject to Central Dispatch
subject to agreement with the TSO. Unless otherwise
specified by the TSO or otherwise in the Grid Code,
information submitted in respect of an Aggregated
Generating
Unit shall always be at an aggregated level.
In the case of a Generator Aggregator, the aggregated
Aggregated Maximum value (in MW, MVA, kW and/or kVA) provided in each
Export Capacity Connection Agreement (or connection agreement to the
Distribution System, as the case may be) for the
Generating Units for which
the Generator Aggregator is responsible.
Aggregators PC 1.1 and Either a Generator Aggregator or a Demand Side Unit
followings Operator in respect of an Aggregated Demand Site.
Automatic Generation OC 4 The mechanism, and equipment installed on a
Control (AGC) SDC 1 & 2 Generator to process and monitor the system
frequency, and contribute in stabilizing and
maintaining the system frequency within permissible
limits included. in the Grid Code and NEPRA
Performance Standards (Transmission) Rules.
Automatic Load CC 5.4 A load shedding scheme, utilized by NTDC, to prevent
Shedding OC 4 frequency collapse or other problems, and to restore
the balance between generation output and toad
demand on the NTDC system,
Automatic Voltage SDC 2 A continuously acting automatic excitation control
Regulator (AVR) system to control the voltage of a Generator measured
at the Generator terminals.
Auxiliaries OC 12 Any item of Plant or and/or Apparatus not directly a
part of the boiler plant or Generator's, but required for
the boiler plant's or Generator's functional operation.
Auxiliary Diesel Engine SDC A diesel engine driven electric generator used to
Generator provide emergency electric power for auxiliary power
supply. Plants with sufficiently large auxiliary diesel-
generator could have Black Start capability.
Availability Notice SDC The Notice for each CDGU, must state the Availability
in a whole number of MW and, for each CDGU, state
the Availability in MW to one decimal place.
Available Power SDC 1.4.1 Effective power from the Generator available in the
bulk power transmission system for load dispatch.
Back-up Protection PMC Protection equipment or system which is intended to
operate when a system fault is not cleared in due time
because of failure or inability of the primary or main
protection scheme to operate or in case of failure to
operate a circuit-breaker other than the associated
circuit-breaker. Also known as secondary protection.
Balancing Code (BC) OC & SDC That part of the Grid Code which details the Balancing
Mechanism.
G&D 404
Balancing OC & SDC A balancing arrangement for the purpose of bilateral

Mechanism contracts for dispatching Generators, access to
additional generation for system needs, and establish
a price for each operating time period at which
differences between contractual and real time
operations are settled.
Bilateral Contracts SDC 1.4.2.7 A direct contract, (without NTDC having to purchase
power on behalf of the Buyer}, between the Power
Producer (Seller) and Purchaser (Buyer) for the
purchase of electric power and energy.
Black Start OC 1.2 The procedure necessary for a recovery from a Total
SDC 2 Shutdown or Partial Shutdown.
Black Start Capability OC For a designated Black Start Station, the ability for at
least one of the generating units of a Generator to
Start- Up from Shutdown; and to energize a part of the
System and/or be synchronized to the System on the
instructions of NTDC, without any external electrical
power supply
Black Start Station OC Black start stations are Generators with Black Start
capability. An emergency auxiliary (station service)
supply, such as auxiliary diesel-electric generator
capable of supplying auxiliary power to the station is
provided.
Black Start Test OC 11 A test carried out by a Generator to the instructions of
NTDC to demonstrate that the designated Black Start
Station has a Black Start Capability.
BM Participant OC & SDC A Person who is respon5'ble for and controls one or
more Generators. For the avoidance of doubt, it does
not imply that they must be active in the Balancing
Mechanism.
Bulk Power Supply PMC The commercial agreement (PPA) between a Generator
Agreement and a purchaser of electric power for the delivery
and/or use of the electric power.
Bulk Power PMC The commercial agreement between the NTDC and a
Transmission Code Participant for the provision of transmission
Agreement services.
Schedule as stated in SDC 1.4.3.4) for simultaneous
transmission purposes of electric power.
G&D 405
Central Dispatch The process of Scheduling and issuing Dispatch

Instructions directly to a Control Facility by the TSO
pursuant to the Grid Code.
All Dispatchable Wind, Solar,, Interconnectors, Pumped

Storage Plant Demand, Battery Energy Storage Units,
Demand, Demand Side Units, and Aggregated
Generating Units are subject to Central Dispatch.
In relation to all other Generation Units, thresholds

apply as follows:
 all other Generation Units with a Registered
Capacity of 10 MW or more are subject to
Central Dispatch;
Capacity of 5 MW or more and less than 10 MW
are not subject to Central Dispatch unless
required by the TSO; however, such Generation
Units can elect to be subject to Central
Dispatch;
Capacity of less than 5 MW are not subject to
Central Dispatch unless required by the TSO;
 any Power Station, which has an aggregate
Registered
Aggregated Generating Unit;

 all Generation Units with a Registered
Capacity of less than 10 MW can elect whether
to comply with
SDC1.4.4.5 relating to the submission of Commercial
Offer Data.
Activities involved in undertaking the Commissioning
Test or implementing the Commissioning Instructions
pursuant to the terms of the Connection Agreement or
as the context requires the testing of any item of users
equipment required pursuant to this Grid Code prior to
Commissioning connection or re-connection in order to determine that
it meets all requirements and standards for connection
to the Transmission System. It also includes activities
that determine the new values of parameters that apply
to it following a material alteration or modification and
in addition those activities involved in undertaking the
Commissioning Tests or implementing the
Commissioning
Instructions as the context requires.
Commissioning A step-by-step test procedure for a Commissioning Test.
Instructions
G&D 406
Testing of a CDGU, Controllable PPM, Pumped Storage

Plant Demand, Demand Side Units, Aggregated
Generating Units, Interconnector or an item of User's
Equipment required pursuant to the Connection
Conditions prior to connection or re-connection in order
Commissioning Test to determine whether or not it is suitable for connection
to the System and also to determine the new values of
parameters to apply to it following a material alteration
or modification of a CDGU, Controllable PPM, Pumped
Storage Plant Demand, Demand Side Units, Aggregated
Generating Units, Interconnector or of an item of User's
Equipment and the term “Commissioning Testing”
shall
be construed accordingly.
Congestion Condition OC 1 A constraint resulting from overloading of transmission
line and/or transformer which could jeopardize the
system security and integrity.
Connection CC 4 An Agreement between NTDC and or User setting out
Agreement CC 4 the terms and conditions relating to a Connection to
and/or use of its bulk power transmission system.
Connection Charges SDC NTDC's charges to Users for Connection to the NTDC
System.
Connection Point SDC 1 A point at which a User's or Code Participant's Plant
and /or Apparatus connects to the bulk power
transmission system of NTDC.
Connection Site CC 5.4 A site containing a Connection Point.
CC Appendix A
CC Appendix B
Constrained Group A group of Generating Units located within a constrained
part of the System as determined by the SO.
Consumer DRC A power generating plant installed at the consumer's
Generating Plant premises by the Consumer.
Consumption PMC Is the use of electrical energy by a licensee or Bulk
Power Consumer, in a period of time that has been
previously established
Contingency Reserve SDC The margin of generation over forecast load demand,
which is required in the period from 24 hours ahead, to
be available within 30 minutes of the contingency
event; down to real time to cover against uncertainties
in generation availability and mismatch between load
and generation, and against both weather forecast and
demand forecast errors.
Contracted Capacity SDC 1 In relation to a CDGU with a PPA, the Normal Full Load
(NFL) Capacity of the CDGU which is set out in the
Power Purchase Agreement (PPA)/Power Station
Operation & Dispatch Agreement (PSODA) for that
CDGU, as that Normal Full Load (NFL) Capacity which
may be amended from time to time in accordance with
the Power Purchase Agreement (PPA)/Power Station
Operation & Dispatch Agreement (PSODA).
Contracted Capacity SDC In relation to a gas turbine PPA CDGU, the figure
(Peak) (expressed in MW) specified as such in the relevant
Power Purchase Agreement (PPA)/Power Station
Operation & Dispatch Agreement (PSODA).
G&D 407
Contracted Generation SDC 1 In relation to a CDGU with a PPA. the values of GSDPs
Scheduling and which are identical to those parameters set out in a
Dispatch Parameters Schedule to the Power Purchase Agreement
(GSDPs) (PPA)/Power Station Operation & Dispatch Agreement
(PSODA) for that CDGU, which are those referred to as
"Contracted Operating Characteristics", as those
values, which can be amended from time to time in
accordance with the Power Purchase Agreement
(PPA)/Power Station Operation & Dispatch Agreement
(PSODA). In the case of an EC CDGU (Externally
Contracted the values of GSDPs which are identical to
the parameters set out in the relevant Inter-connection
Agreement and
Cycle Operating Mode The Open Cycle Mode or combine cycle Operating Mode
of a CCGT Installation which may need to be specified
pursuant to a Dispatch Instruction under SDC2.4.2.4(j).
A facility which consumes electrical energy and is
Demand Facility(ies) connected at one or more Connection Points to the
Transmission System. The Distribution System and/or
auxiliary supplies of a
Generation Unit do not constitute a Demand Facility.
Demand Facility Owner A person who owns a Demand Facility.
Demand Side Operator A person who operates a Demand Side Unit, with an
aggregated Demand Side Unit MW Capacity not less
than 10
MW.
An Individual Demand Site or Aggregated Demand Site
Demand Side Unit with a
Demand Side Unit MW Capacity of at least 4
MW. The Demand Side Unit shall be subject to Central
Dispatch.
The four Demand Side Unit Profiles from one day to
eighty- four days prior to the Dispatch Instruction,
Demand Side Unit Best offset to minimise the average absolute error across all
Correlated Profile the Meter periods comprising the Demand Side Unit
Profile when compared to the Demand Side Unit Profile
which finishes with the Dispatch period, resulting in the
four smallest average absolute errors,
averaged.
The estimated total Energy requirement for an
Individual Demand Site or aggregated consumption for
Demand Side Unit Energy each Individual Demand Site which form part of an
Profile Aggregated Demand Site for each Imbalance
Settlement Period in the following Trading Day and
which must be submitted to the TSO in the
Availability Notice under SDC1.4.4.2.
The value of the quarter-hour Demand Side Unit
Demand Side Unit Performance Monitoring Baseline less the sum of the
Calculated MWh quarter-hour Meter readings of all the Individual
Response Demand Sites that comprise the
Demand Side Unit aligned to a quarter-hour Meter
period.
which must be submitted by the User to the TSO in an
Demand Side Unit MW Availability Notice under SDC1.4.1.2.
Availability
G&D 408
The maximum change in Active Power that can be

achieved by a Demand Side Unit on a sustained basis
Demand Side Unit MW for the duration of the Demand Side Unit’s Maximum
Capacity Down Time by totaling the potential increase in on-site
Active Power Generation and the potential decrease in
on-site Active Power Demand at each
Individual Demand Site.
The proportion (in MW) of the Demand Side Unit MW
Demand Side Unit MW Capacity that is delivered at a given time following a
Response Dispatch Instruction from the TSO. This value will be zero
unless dispatched by the
TSO.
The time as specified by the Demand Side Unit
Demand Side Unit MW Operator in the Technical Parameter and is the time it
Response Time takes for the Demand Side Unit Operator to be able to
implement the Demand Side Unit MW Response from
receipt of the Dispatch
Instruction from the TSO.
The equivalent Energy in a quarter-hour Meter period of
Demand Side Unit MWh a
Response Demand Side Unit MW Response requested in a
The time as specified by the Demand Side Unit
Operator in the Technical Parameter and is the time it
Demand Side Unit Notice takes for the Demand Side Unit to begin ramping to the
Time Demand Side Unit MW Response from receipt of the
Dispatch Instruction from
the TSO.
A person who operates a Demand Side Unit, with an
Demand Side Unit aggregated Demand Side Unit MW Capacity not less
Operator than 4
MW.
An Energy value for each quarter-hour Meter period
Demand Side Unit while a Demand Side Unit is Dispatched. It is the
Performance Monitoring Demand Side Unit Best Correlated Profile excluding the
Baseline first forty-eight quarter-
hour Meter periods.
Demand Side Unit The absolute value of the Demand Side Unit Calculated
Performance MWh
Monitoring Error Response less the Demand Side Unit MWh Response.
Demand Side Unit The absolute value of the Demand Side Unit Calculated
Performance Monitoring MWh Response less the Demand Side Unit MWh
Percentage Error Response divided
by the Demand Side Unit MWh Response.
Consecutive aggregated Meter readings of all Individual
Demand Sites that comprise a Demand Side Unit for
each of the full quarter-hour Meter periods in a twelve-
hour period plus the duration of Dispatch. If the
Demand Side Unit was Dispatched during the period
the Demand Side Unit Calculated MWh Response in the
Demand Side Unit Profile same quarter-hour Meter periods are added, except in
the case of the Dispatch being monitored. In this case
the accumulated Energy calculated from Demand Side
Unit MW Response from Generation operating in
Continuous Parallel Mode or Shaving Mode signal
(CC.12.2 (l)) plus the Demand Side Unit MW Response
from avoided Demand consumption and Generation
operating
in Lopping Mode, Standby Mode or Automatic Mains
Failure Mode signal (CC.12.2 (m)) are added.
G&D 409
The time it takes for a Demand Side Unit to ramp to the

Demand Side Unit Ramp Demand Side Unit MW Response. It is equal to the
Time Demand Side Unit MW Response Time less the Demand
Side Unit Notice Time.
The Demand Side Unit Calculated MWh Response less
the accumulated Energy calculated from Demand Side
Unit MW Response from Generation operating in
Demand Side Unit Continuous Parallel Mode or Shaving Mode signal
SCADA Error (CC.12.2 (l) plus the Demand Side Unit MW Response
from avoided Demand consumption and Generation
operating in Lopping Mode, Standby Mode or Automatic
Mains Failure Mode signal (CC.12.2 (m)) in the
same quarter-hour Meter period.
The Demand Side Unit Calculated MWh Response less
Demand Side Unit the accumulated Energy calculated from Demand Side
SCADA Percentage Error Unit MW Response from Generation operating in
Continuous Parallel Mode or Shaving Mode signal
(CC.12.2 (l) plus the Demand Side Unit MW Response
from avoided Demand consumption
An instruction given by the TSO to a CDGU, Demand
Side Unit, Interconnector and/or Pumped Storage Plant
Demand to that User’s approved Control Facility to
Dispatch Instruction
change the output, fuel or manner of operation of the
CDGU, Demand Side Unit, Interconnector and/or
Pumped Storage Plant Demand.
“Instruct” and “Instructed” shall be construed
accordingly.
The flag indicating that a Dispatch Instruction will not
be deemed to be a Dispatch Instruction for settlement
purposes, used when the TSO approves new or
amended test proposals submitted by a User after Gate
Dispatch Instruction Test Closure 2 (or there is insufficient time for the TSO to
Flag evaluate and approve the test proposal before Gate
Closure 2) and as a result, the Dispatch Instructions
issued by the TSO diverge from the Final Physical
Notifications.
Embedded Generating Generating Units within a Power Station which are
Plant directly connected to a Distribution System or the
system of any other User , such connection being either
a direct connection or a connection via a busbar of
another User but with no other Connection to the
Transmission System
Embedded Generating Protection designed to disconnect Generation Units
Plant Interface Protection from the Distribution, Provincial & SPTLs System during
abnormal system conditions by tripping a dedicated
circuit breaker or recloser located as close as
practically possible to the interface between the DSO,
Provincial & SPTLs, and Demand Customer equipment
and the Distribution System.
The forecasted maximum amount of Energy that can be
Energy Limit generated by an Energy Limited Generating Unit within
the Trading Day.
Energy Limited A Generating Unit with a limit on the Energy it can
Generating Unit deliver in a specified time period.
Energy Storage any Energy Storage Unit working in as Generator
Generating Unit (ESGU)
Energy Storage A Generator which owns and/or operates any Energy
Generator Storage Power Plant
Energy Storage Power A site containing at least one ESU can automatically act
G&D 410
Plant (ESPP) upon a remote signal from the TSO to change its Active
Power output.
Energy Storage Power An Energy Storage Power Plant in its operation of
Plant (ESPD) consuming Energy.
Demand
Energy Storage Unit A Generation Unit(s) using generic storage devices to
(ESU) generate and consume electricity.
Battery Energy Storage A Generation Unit(s) using battery storage devices to
Unit (BESU) generate and consume electricity
Apparatus for the transmission of electricity to
External Interconnection
(from) the
Transmission System or the Other Transmission System
from (to) a transmission or distribution system located
outside the Pakistan Borders
In relation to an External System Operator means the
transmission or distribution system which is located
External System outside the Pakistan and any Apparatus or Plant which
connects that system to the External Interconnection and
which is owned or operated by such External System
Operator.
A person who operates an External System which is
External System connected to the Transmission System or the Other
Operator Transmission System by an External Interconnection.
The operator of an electrical transmission or distribution
Externally system outside the Pakistan borders which is connected to
Interconnected Party the Transmission System by an External Interconnection.
Frequency Control SDC The control of the frequency on the NTDC System by
Frequency Deviation SDC A measure of frequency error, from the
declared/Target System Frequency, accumulated over
a period of time.
Frequency SDC The, mechanism through which the system's frequency
Regulation is maintained within the allowable limits as specified in
the Grid Code (OC 4.8) and NEPRA Performance
Standards (Transmission)-Rules.
Frequency Sensitive OC 4.8 The operation of a Generator whereby its generation
Mode level is varied automatically to compensate for
variations in the frequency of the NTDC System in the
Frequency Sensitive Mode (49.8-50.2 Hz).
Frequency Transient SDC For the purposes of Operating Code and Metering &
Protection Code, a period when the NTDC System
Frequency is below 49.5 Hz (Tolerance Frequency
Band).
Fuel Rate SDC 1 Has the meaning ascribed to that term in the relevant
Generator's Power Purchase Agreement (PPA)/Power
Station Operation & Dispatch Agreement (PSOOA) as
applicable.
Full Load SDC Highest value of load specified for rated conditions of
operation.
Fully Available CC 5.4 In relation to a CDGU or a Range, means Available to
the CDGU's Contracted Capacity (or full output in the
case of an EC CDGU).
Generating Plant SDC 1 A Power Plant subject to Central Dispatch
Generating Unit SDC 1 One of the Units of a Generator in a Generating
G&D 411
CC Plant/Station producing electric power and energy.

Generating Unit Work SDC 1 Auxiliary consumption of an individual Generating Unit
Unit of a Generator.
Generation Offer Prices SDC A set of prices submitted by a Generator in respect of
each of its dispatch units specifying.
1. A Start-up Price (expressed in Rupees)
2. A No-Load Price (expressed in Rupees per Hour)
3. A Maximum Generation Price (a positive value
expressed in Rupees per MWh).
Generation Prices SDC A set of prices for each CDGU with PPA calculated by
relevant division of NTDC from the relevant Power
Purchase Agreement (PPA) and the Fuel Rate
calculated in accordance with the Power Purchase
Agreement (PPA).
Generator CC An Entity who is involved in generation business under
SDC 1, 3 a Generation License granted by NEPRA.
Generator SDC 1 A diagram which shows the MW and MVAr capability
Performance Chart Appendix A limits within which a Generator is expected to operate
under steady-state conditions in the format set out in
the Grid Code.
Generator SDC The main transformer for a CDGU through which power
Transformer passes from the Generating Unit to the NTDC System.
Governor CC 5.4 A mechanical device used to automatically regulate
the speed of a turbine of electric generator.
Governor Droop SDC 1 In relation to the operation of the governor of a
Appendix A & B Generating Unit, the percentage droop in system
frequency which would cause the Generating Unit
under free governor action to change its output from
zero to full load.
Grid Code Test A test that is to be mutually agreed, with agreement not
to be unreasonably withheld, and conducted in
accordance with Grid Code.
Grid Entry Point SDC A point at which a Generator connects to the NTDC
System.
Grid Exit Point SDC A point at which electricity may be delivered from the
NTDC System to a Bulk Power Consumer, Distribution
Company or to a Tie-line or to Externally-connected
Parties/Consumers.
GSDP Notice SDC 1 A Notification given by a Generator to NTDC stating the
Appendix B GSDPs of a CDGU to apply for the next following
Schedule Day which, if given by not later than the
Notice Submission Time, shall be in the form set out in
Appendix B to SDC 1 or in such other for as
NTDC/System Operator may reasonably notify to each
Generator from time to time, and which, if given after
the Notice Submission Time, shall be in the form set
out in Appendix C to SDC 1 (which is headed "GSDP
Revision Notice") or in such other form as NTDC may
reasonably notify each Generator from time to time.
Half Hour OC 4 Means any 30-Minute period ending on the Hour or
Half Hour
Hot Standby SDC A condition of readiness to be able to synchronize and
attain an instructed output in a specified time period
that must be maintained by Generator.
IGCEP OC Indicative Generation Capacity Expansion Plan
G&D 412
Incidents OC 8 An event of external or internal origin, affecting

equipment or the supply system, and which disturbs
the normal operation of the System.
Incremental Price SDC 1 The marginal price (i.e. incremental price for each
Appendix G MWh produced) between zero and Normal Full Load
(NFL) Capacity of a Generator.
Independent SDC A Generator not owned by any public sector entity
Generating Plant which may or may not be subject to Central Dispatch.
Independent Power PC 3 A private power generating company not owned/
Producer (IPP) controlled by any public sector organization but
subject to Central Dispatch.
Indicative A schedule prepared by the TSO in conjunction with the
Operations Other TSO pursuant to SDC1.4.8.1.
Schedule
A programme of Outages of the Generator’s Generation
Indicative Units or Interconnectors prepared by the TSO pursuant
Outage
to OC2 and covering years 4-7 ahead.
Programme
Initial Response SDC The device by which NTDC can issue a signal by way of
Instructor dispatch relating to the loading of CDGUs from the
National Power Control Centre (NPCC) to the
Generators.
Instrument Transformer SDC A transformer intended to transmit an information
signal to measuring instruments, meters and
protective or control devices. The term "instrument
transformer" encompasses both current transformer
and voltage transformers.
The Interconnector Operating Protocol is a protocol for
specific operating conditions of the Interconnector
which may exist between the Interconnector Operator,
the TSO and the External TSO. The Interconnector
Operating Protocol shall be agreed as appropriate by all
Interconnector Operating parties before operation of the Interconnector. The
Protocol Interconnector Operating Protocol shall include but is
not limited by the following; planned outage
coordination, Operating Procedures, Interconnector
Instructions, Interconnector Faults, Emergency Power
Functionality, Operational Liaison, System Testing,
Operational
and Safety Switching.
A person who operates an Interconnector and is subject
Interconnector Operator to the
Grid Code pursuant to any agreement with the TSO or
otherwise.
A person who owns an Interconnector. For the
Interconnector Owner avoidance of doubt the Interconnector Owner shall be
responsible for all Grid Code requirements concerning
the Interconnector
Operator in relation to the Interconnector.
Interconnector Ramp The maximum rate of increase or decrease of the power
Rate transferred, in either flow direction, by an Interconnector.
The rate of decrease of an Interconnector. Ramp-down
Interconnector Ramp- Capabilities apply over the bi-directional range from its
down Capability Interconnector Registered Import Capacity to its
Interconnector Registered Export Capacity.
G&D 413
The rate of increase of an Interconnector. Ramp-up

Interconnector Ramp-up Capabilities apply over the bi-directional range from its
Capability Interconnector Registered Export Capacity to its
Interconnector Registered Import Capacity.
The maximum Capacity, in either flow direction,
expressed in whole MW, that an Interconnector can
Interconnector deliver on a sustained basis, without accelerated loss of
Registered Capacity equipment life, at the
Connection Point. This figure shall include transmission
power losses for the Interconnector.
The maximum Capacity, expressed in whole MW that
Interconnector an Interconnector may export (transfer energy from the
Registered Export Power System to a remote network) on a sustained
Capacity basis, without
accelerated loss of equipment life, as registered with the
TSO.
The maximum Capacity, expressed in whole MW that
Interconnector an Interconnector may import (transfer energy from a
Registered Import remote network into the Power System) on a sustained
Capacity basis, without
accelerated loss of equipment life, as registered with the
TSO.
The quantities of Active Power which have been
Interconnector Schedule scheduled on
Quantities an Interconnector as a result of trading in day ahead
and/or intraday markets and submitted by a Scheduling
Agent.
A transformer whose principal function is to provide the
Interconnector interconnection between the Interconnector and the
Transformer Network and to transform the Interconnector voltage to
the Network
voltage.
An Interconnector subject to Central Dispatch which will
include appropriate control and response of each
Interconnector’s Plant converter station and Apparatus upon Dispatch
Instruction issued by the TSO. It shall consist of all
aspects of the technology including, converter station,
DC cable filter banks etc. up to the
Connection Point.
Inter tripping Scheme The tripping of circuit-breaker(s) by signals initiated
from protection at a remote location independent of
the state of the local protection.
Isolation Device PMC A device for achieving electrical Isolation.
Load SDC 1 The Active, Reactive or Apparent Power as the context
CC 4.2.5.4 requires to be generated, transmitted or distributed.
Load Curve SDC The curve that represents the behavior of the MW load
during a particular study period.
Load Curves of Daily SDC The graphical representation of daily peak MWs of an
Peaks electric power entity over a given study period.
Load Factor SDC Is the relation between the average Load Demand of
an established period with regard to the maximum
Load Demand for the same period.
Loss of load probability PC 4 Loss of Load Probability, the percentage of time that
(LOLP) the system capacity is inadequate to meet load
demand.
G&D 414
Low Frequency SDC The process, a part of load reduction or management,

Disconnection of load disconnection (manually or automatic) under
low frequency system conditions.
Low Frequency Initiated SDC A capability of a Generator to respond to low system
Response Frequency Transient to initiate its Primary and
Secondary responses to help correct and maintain
permissible system frequency limits as contained in
the Grid Code (0C 4.8 of Operating Code) and
approved by the Authority.
Major Event SDC An Event which either:
(a) was notified by a User To NTDC which NTDC
considers that has had a or may have had a
significant effect on the NTDC Transmission
System, and NTDC requires the User to report that
Event in writing and notifies the User accordingly;
or
(b) was notified by NTDC to a User, and which that
User considers that has had or may have had a
significant effect on that User's system, and that
User requires NTDC to report that Event in writing
and notifies NTDC accordingly.
Maximum Continuous CC, PC, SDC The normal Full Load MW Capacity of a Generator,
Rating (MCR) which can be sustained on a continuous basis under
specified conditions.
Maximum Demand PC Appendix A Maximum electrical power (MW and MVAR) used and
registered in a specified time period.
Merit Order Price Set SDC 1 A price set consisting of an Incremental Price and No-
load Price in relation to a particular designated
declared fuel.
Merit Order Ranking SDC The order at which all the Generators participating in
the Central Dispatch are ranked by the System
Operator based on their Merit Order Price Set for the
purpose of Scheduling and Dispatch. The ranking order
is from lowest to the highest cost, the lowest cost
being the first ones to be dispatched.
Metering Data SDC Information on measured electrical quantities recorded
in the meter register, such as energy, demand and
power factor, including time and date.
Metering Equipment SDC Ensemble of instruments for the purpose of measuring
electrical quantities which includes Meter, CTs and PTs.
Meter Registration Meter Registration System The unit of NTDC, the
System Operator (MRSO) Distribution, Provincial and SPTLs Companies which which
fulfills licensee metering obligations and acts as Relevant
Data Provider for NTDC, the Distribution, Provincial and
SPTLs Companies as the case may be.
Minimum Generation SDC 1 The minimum MW output, which a Generator can
Appendix A generate continuously, registered with NTDC under
SDC1 as a Generating Station Dispatch Parameter
(GSDP).
Minimum Demand SDC 1 Means minimum level of Active Power of a Generator,
Regulation or MOR which is sufficient to provide an adequate regulating
margin for necessary Frequency Control.
Monitoring Notice SDC A Notice issued by NTDC to a Generator informing the
Generator that NTDC is monitoring one of its CDGUs.
Multiple Connection CC More than Single Connection Point, interconnected to
G&D 415
Point each other through the User's System.

Network Operator CC 5.4 An Entity, which operates and manages an electrical
power (transmission or distribution) network.
NFL Capacity SDC The Normal Full Load (NFL) Capacity of a CDGU
(expressed in MW and stated, where relevant, in
relation to a Designated Fuel) to generate electricity
(using, where relevant, the Designated Fuel),
determined at the Generator terminals.
No-Load Price SDC 1 That component of the generation prices of a CDGU
(expressed in Rupees/hour of operation of the CDGU)
which relates to the operation of the CDGU at "No
Load: but which is applicable to all levels of output of
that CDGU.
Nominal or Nameplate SDC The rated power output specified by the manufacturer
Power of a given electrical equipment.
Nominal System OC 4 As defined in NEPRA Rules on Performance Standards
Voltage (Rated Voltage) (Distribution) or other NEPRA applicable documents.
Notice to Synchronize SDC The amount of time (expressed in minutes) that is
declared by a Generator in relation to a dispatch unit
to enable it to be synchronized following the receipt of
an Instruction to synchronize with the NTDC system.
Notification SDC The daily submission Notice of Availability by
Generators to the System Operator for dispatch
purposes.
NTDC Calendar Year Grid Code 1 January-31st December of a given year.
NTDC Site CC 4.5 & 5.4 Means a site of inter-connection owned by NTDC or by
a User but occupied and managed by NTDC.
NTDC System Demand PC i. The amount of electricity to be supplied from the
Appendix A Grid Supply Points (Entry or Exit) plus to be
supplied by Embedded Generating Plant plus NTDC
Transmission System Losses less the output of
directly-connected Independent Generating Plants.
ii. Demand on the Total System less the output of
Independent Generating Plants.
Open Access CC 5.4 Provision of connection and non-discriminatory "Use"
of the transmission, sub-transmission and distribution
network of a licensee.
Operating Margin SDC 1 & OC 5 Sum of Contingency Reserve and Operating Reserve as
defined in OC 5.2.
Operating Reserve SDC The additional output from Generators which must be
realizable in real-time operations to respond in order to
contribute to correcting and containing any
system frequency fall to an acceptable level after the
loss of generation or loss of import from an External
Interconnection or mismatch between generation and
Load Demand.
Operational Tests Tests carried out by the TSO in order to maintain and
develop operational procedures, to train staff and to
acquire information in respect of Transmission System
behaviour under abnormal System conditions, and also
tests carried out by other Users for similar purposes in
respect of their Plant.
Optimum Dispatch SDC The dispatch with due regard to both economic and
(Final Dispatch) technical conditions represents the optimum dispatch.
Out of Band VAR SDC Reactive power supplied by a Generator operating
G&D 416
outside of its rated power factor.

Outage SDC 1 a. In relation to a CDGU/Generator, a total or partial
Appendix B reduction in Availability in connection with the
repair or maintenance of the CDGU or any
associated power plant equipment, or resulting
from a breakdown or failure of the CDGU or any
associated power plant equipment.
b. In relation to NTDC, the removal for repair or
maintenance, or as a result of failure or breakdown,
of any part of the NTDC System.
C. Means the state of a component when it is not
available to perform its intended function due to
some event directly associated with that
component. An outage may or may not cause an
interruption of service to customers, depending on
system configuration.
Outage Notice SDC A Notice submitted by a Generator under OC4 notifying
NTDC of an Outage.
Output CC 5.4 The actual output at the main generator terminals of a
SDC1 CDGU (in MW) derived from data measured pursuant
Appendix A to this Grid Code.
Overburn Contracted SDC In relation to a CDGU, which is capable of firing one or
Capacity two different Designated Fuels, the figure expressed in
MW, measured at the Generator terminals identified in
a Schedule to the relevant Power Purchase Agreement
(PPA)/Power Station Operation & Dispatch Agreement
(PSODA) as "Overburn Contracted Capacity".
Part load SDC A Generator which is loaded but is not _running at its
declared Availability.
Partial Collapse SDC Breakdown of the electrical system due to a failure or
contingency that affects a particular area or region of
the country and is limited to that area or region only.
Partial Shutdown SDC 1 The situation existing when all generation has ceased
in a particular part of the Total System: and ·there is
no electricity supply from External Interconnections or
other parts of the Total System to that particular part
of the Total System and, therefore, that particular part
of the Total System is shutdown; with the result that it
is not possible for that particular part of the Total
System to begin to function again without NTDC
directions relating to a Black Start.
Peak Capability SDC In relation to a gas turbine CDGU, the capacity of the
CDGU (expressed in MW) to generate electricity in
excess of its Contracted Capacity determined in
accordance with the relevant Power Purchase
Agreement (PPA)/Power Station Operation & Dispatch
Agreement (PSOOA).
Peak Instruction In the case of a Gas Turbine PPA CDGU, an instruction
requiring it to generate at a level in excess of its
Availability but not exceeding its temperature adjusted
peak capability
Plant CC 4.4 & 5.4 Fixed and movable equipment used in the generation,
SDC 1 transmission and distribution of electricity.
Appendix A
Plant Factor DRC The relation of the total actual generation to the
G&D 417
generation that may have been produced if the unit

had operated in a continuous manner to its Normal Full
Load (NFL) Capacity.
Point of Connection CC 5.4 An electrical Connection Point between the NTDC bulk
power transmission system and a User's/Code
Participant System as defined in OC 4.2 of the Grid
Code.
Power Line Carrier (PLC) OC 6 Communications system of radio frequency generally
under 600 kHz, which transmits information using high
voltage transmission lines.
Power Plant SDC 1 An installation comprising one or more Generating
Appendix A & B Units owned and controlled by the same Generator.
CC 1
Power Purchase SDC 1 Power Purchase Agreement is between the Seller
Agreement (PPA) ("Generator" in this case) and the Buyer [licensed
distribution companies, Bulk Power Consumers
whether directly or indirectly connected to the NTDC's
bulk transmission system and other Persons as stated
in DRC 1.2 (d)], other externally-connected Parties and
Consumers, for the purpose of purchase of electric
power and energy.
The Power Purchase Agreement may contain
operational, control, dispatch, outage and
maintenance procedures and requirements of the
power station, technical limits, GSOPs, Generation
Performance Charts, and other Generator data
requirements stated in various sub-codes of this Grid
Code or it may refer to the Grid Code for such
requirements.
Power Station SDC 1 Notwithstanding anything contained in the PPA
Operation & Dispatch between a Generator and Purchaser of electric power
Agreement (PSODA) and energy, each Generator having a bilateral contract
shall have in place, at all times, a Power Station
Operation & Dispatch Agreement (PSODA) with NTDC
for the purposes as follows:
The PSODA shall contain operational, control, dispatch,
outage and maintenance procedures and requirements
of the power station, technical limits, GSDPs,
Generation Performance Charts, and other Generator
data requirements stated in various sub-codes of this
Grid Code.
Power Station SDC 1 Power Station means Power Plant in this Grid Code.
Power System Stabilizer CC Equipment controlling the exciter output via the
(PSS) voltage regulator in such a way that power oscillations
of the synchronous machines are dampened. Input
variables may be speed, frequency or power (or a
combination of these).
Preventive OC 4, SDC 1 The periodic maintenance performed on the equipment
Maintenance to avoid the occurrence of possible unplanned failure
or outages.
Primary Response SDC The automatic response to NTDC system frequency
changes released increasingly with time over the
period 0-3 seconds and 3-10 seconds from the time of
frequency change, and fully available within these time
scales and achieving its maximum value within 10
G&D 418
seconds following a frequency fall and subject to the

agreed Unit Load Controller adjustment where
applicable and must be sustainable for up to 30
seconds.
Protection and Control PMC The provisions for detecting faults or other abnormal or
emergency conditions in a power system. For enabling
fault clearance, for terminating abnormal or
emergency conditions, and for initiating signals or
indications.
Provincial Company
Reactive Compensation
Equipment
Reactive Power CC 5.4 The product of voltage and current and the sine of the
SDC 1 phase angle between them measured in units of volt-
amperes reactive and standard multiples thereof i.e.
1000 Var = 1 kVAr
1000 kVAr = 1 MVAr
1000 MVAr = 1 GVAr
Reactive Reserve SDC The MVAR reserve on the on-line Generators
(difference between MVAR capability at the output MW
level at a given time and actual MVAR produced).
Real Time Operation OC 4 Operation performed by NTDC through the SCADA
monitoring system.
Reference Load Dispatch The Load Dispatch Center of a National Transmission
Center Company(NTC) assuming the role of interface between
the DCO and all the NTCs
Registered Capacity PC The Normal Full Load (NFL) Capacity of a Generator in
Appendix A MW measured at the Generator terminals.
Regulating Margin SDC The margin of generating capacity over Demand which
is required in order to maintain frequency control.
Relevant Meter Operator The entity obliged under the Trading and Settlement
Code or obliged under Licence, issued by the
Commission, to operate and provide for the installation,
testing and calibration of a defined set of metering points.
The Relevant Meter Operators are NTDC, DISCOs,
Provincial & SPTLs Companies.
Remedial Actions Special Action Those actions described in SDC2, which the Operator
undertakes in case of emergency.
Remote Terminal Unit OC 6 A part of the SCADA system. It is a set of electronic
(RTU) devices that collects and transmits data to, and
receives and executes the commands from the master
unit.
Reserve Characteristics SDC The MW level of reserve required at any given MW
output of a CDGU as set out in the Sustained Load
Diagram which is a part of the Grid Code or Power
Purchase Agreement (PPA)/Power Station Operation
and Dispatch Agreement (PSODA).
Revenue Metering SDC 1 Metering used to measure the demand and energy at a
specific point in the system upon which an invoice will
be prepared and payments shall be made between
power supplier and User.
Safety Coordinator CC A Person or Persons nominated by NTDC and each User
to be responsible for the co-ordination of Safety
Precautions at each Connection Point when work
(which includes testing) is to be carried out on a
G&D 419
System which necessitates the provision of Safety

Precautions on HV Apparatus.
Schedule Day SDC 1 The period from 0000 hours until 2400 hours on the
Appendix A same day.
Scheduling SDC The process of compiling a Generating Schedule as set
out in SDC 1, and the term "Scheduled" and like terms
shall be construed accordingly.
Second-tier Users CC The Users having bilateral contracts with another
licensee through the NTDC transmission system for
acquiring power.
Secondary Response CC 3 It is the increase in active power output of the online
generators or reduction in active load demand that can
be increasingly applied in the short-term following the
fall in frequency available within the time scale of 10-
30 seconds after achieving its maximum value within
30 seconds following the fall in frequency, subject to
agreed Unit Load Controller Adjustments where
applicable, and must be sustainable for 30 minutes
following the fall in frequency.
Short Term Planned SDC An Outage designated as an STPM Outage, the

Maintenance Outage or duration of which shall not, unless NTDC in its absolute
STPM Outage discretion agrees, exceed 72 hours but not including
any overrun of such Outage.
Significant Test An Operational Test with a total duration of equal to or
greater than 6 hours, or where the Active Energy
produced during the total duration of the test is equal
to or greater than:
(i) 3 times the Active Energy which would be
produced by the Test Proposer’s Plant
during 1 hour of operation at the Plant’s
Registered Capacity; or 500 MWh;
Single Line Diagram PC Appendix A Schematic representations of a three-phase network in
which the three phases are represented by single lines.
The diagram shall include (but not necessarily be
limited to) bus bars, overhead lines, underground.
Cables, power transformers, and reactive
compensation equipment. It shall also show where
Generating Plant is connected, and the points at which
Demand is supplied.
Single Point of CC A single Point of Connection, with no interconnection
Connection through the User's System to another Point of
Connection.
Site Common Drawings CC 4.4 Drawings prepared for each Connection Site which
incorporate Connection Site layout drawings, electrical
layout drawings, common protection/ control drawings
and common service drawings.
Special license
Transmission Company
Spinning Reserve SDC 1 As defined in OC 5.2 of this Code which is available
within 10 minutes of the initial frequency fall.
Standing Instruction SDC An Instruction for a specified action notified to a
Generator in advance by NTDC whereby, when the
specified circumstances arise, the Generator will take
the specified action as though a valid Instruction had
G&D 420
been issued by NTDC. This shall include:

a) The date on which an Outage is to begin.
b) The time at which an Outage is to begin.
Start-Up SDC 1 The action of bringing a Generator from shutdown to
Appendix A synchronous speed.
Start-up Price SDC That element of the generation prices for a CDGU
which relates to the start-up of the CDGU.
Station Transformer PC 2.1 A transformer supplying electrical power to the
auxiliaries of a Generator, is not directly connected to
the Generator terminals.
Subsequent Schedule SDC 1 A Schedule prepared subsequent to the Generation
Schedule following a re-optimization of that Generation
Schedule or another Subsequent Schedule, within the
applicable Control Phase time scale.
Sustained Load SDC 1 A Schedule setting out the Sustained Response
Diagram Capability of a CDGU annexed to the Power Purchase
Agreement (PPA)/Power Station Operation & Dispatch
Agreement (PSODA) for that CDGU and submitted to
NTDC pursuant to the Planning Code.
System Grid Code Bulk power transmission system of NTDC.
System Constrained PC Appendix A That portion of transmission capacity which is not
Capacity available due to a system or transmission constraint.
System Energy OC 2 Total MWhr requirements of the entire NTDC system
Requirements which is based on summation of all the measured
energy on all the Connection Points of the NTDC
system with its Users consuming electric power.
System Fault PMC A measure of the ability of Protection to initiate
Dependability Index successful tripping of circuit breakers, which are
(DP) associated with a faulty item of Apparatus. It is
calculated using the formula:
DP = 1 - F1/A Where:
A = Total number of system faults
F1 = Number of system faults where there
was a failure to trip a circuit breaker.
System Operating OC 4.9 Bus Voltage as a percentage of the Nominal System
Voltage Voltage of the Total System during normal system
operation (including both normal and contingency
operating conditions but excluding transient and
abnormal system conditions).
System Margin OC 5 The Margin in any period between (i) Offered
Availability and (ii) The sum of Forecast Demand and
the Operating Margin, for that period.
System Test Tests which involve simulating conditions, or the
controlled application of irregular, unusual or extreme
conditions, on the System, or any part of the System,
but which do not include Commissioning or
recommissioning tests or any other tests of
a minor nature.
System or Transmission OC, PC, SDC 1 A limitation on the Use of Transmission System due to
Constraint lack of transmission capacity or other system
conditions.
Target System OC 4 Frequency Levels of the NTDC bulk transmission
Frequency system as stated in this Grid Code for the normal
steady-state operation of the NTDC bulk supply
transmission system as contained in the Operating
G&D 421
Code (OC 4.8).

Target Voltage Levels OC 4.9 Voltage limits for the normal and contingency
operation of the NTDC bulk supply transmission system
as contained in the Operating Code (OC 4.9).
Technical Parameters Code Such parameters which define the design and
Management operation of the electrical system and its facilities that
are owned/operated by NTDC.
Telemetering OP 6, OP 7, CC A process in which measurements are made at some
remote location and the results are transmitted
through telecommunication facilities. The transmission
of the values of measured variables using
telecommunication techniques is also called
telemetering.
Temperature Adjusted SDC In relation to a gas turbine CDGU, the Peak Capability
Peak Capability adjusted by the temperature correction factor in
accordance with Schedule to the relevant Power
Purchase Agreement (PPA)/Power Station Operation &
Dispatch Agreement (PSODA).
Test Proposer The User submitting proposal for a test under OC8.
Testing Testing carried out by the TSO pursuant to OCxx and/or
CC and
the term “Test” shall be construed accordingly.
Thermal Efficiency SDC 1 Is the quantity of BTU's required for the fuel to
generate a kWh of electrical energy.
Thermal Loadings OC 4 Electrical loadings (MW/MVAR) of the electrical
transmission facilities of NTDC bulk supply system.
Thermal Power Plant A Generating Units that transform thermal energy into
electricity
Tolerance Frequency SDC & OC 4 Protected periods of operation of the system at the
Band frequency in the range of 49.5 Hz - 50.5 Hz as defined
in OC 4.8.
Total Collapse OC 8 Breakdown of the national interconnected electrical
system due to a failure or severe contingency that
causes the interruption of the electrical services of the
entire system.
Total Harmonic CC The departure of a waveform from sinusoidal shape,
Distortion that is caused by the addition of one or more
harmonics to the fundamental, and is the square root
of the sum of the squares of all harmonics expressed
as a percentage of the magnitude of the fundamental.
Total Shutdown OC 8 The situation existing when all generation of the
system has ceased resulting in the: shutdown of the
power system, that it is not possible for the power
system to begin to function again without NTDC
directions relating to a Black Start.
Total System Grid Code Bulk power transmission system of NTDC.
Transmission CC 1 & CC 5.4 A consumer receiving electricity directly from the
Connected Consumers NTDC Transmission system irrespective of the supplier
of electrical power and energy.
Transmission SDC A point at which a User's or Code Participant's Plant
Connection Point and /or Apparatus connects to the bulk power
transmission system of NTDC.
TSEP OC Transmission System Expansion Plan
Unit Control Board SDC A switchboard through which electrical power is
supplied to the auxiliaries of a Generator and which is
G&D 422
supplied by the station transformer. It may be

interconnected with the station main control board.
Unit Load Controller SDC A device which regulates the generation level when
the Generator is operating in Frequency Sensitive
Mode to ensure (as far as possible) that it does not
exceed or fall short of acceptable limits as set in the
Grid Code (OC 4.8) and NEPRA Performance Standards
(Transmission)-Rules.
Unit Load Controller SDC The time constant expressed in units of seconds, of the
Response Time power output increase that occurs in response to a
Constant step change in system frequency.
Unit Nomination SDC 1 In relation to a Generator means the Unit Nomination
Appendix G and covered in SDC 1.4.2.3.C submitted day ahead by
each Generator.
User CC 1 A term used to refer to the Code Participant or Person
to whom the Grid Code applies; who is directly or
indirectly connected and using the bulk transmission
network of NTDC for the purposes of acquisition,
transmission, distribution, and/or consumption of
electrical power and energy.
User Site CC 4.4 A site owned (or occupied pursuant to a lease, licence
or other agreement) by a User in which there is a
Connection Point. For the avoidance of doubt, a site
owned by NTDC but occupied by a User as aforesaid, is
a User Site.
User System CC 1 Any system owned or operated by a User comprising:
(i) Generator; or (ii) Electrical systems consisting
(wholly or mainly) of electric facilities used for the
transmission or distribution of electricity from
Connection Points onwards.
The User system includes any sub-transmission assets
operated by such User or other Person, and any plant
and/or apparatus and meters owned or operated by
the User or other Person in connection with the
transmission, distribution and delivery of electric
power but does not include any part of the NTDC bulk
power transmission system.
Voltage Regulation OC 4.9 Is the process that is used to control the System
Operating Voltage, and maintain it within the tolerable
limits as specified in OC 4.9 of the Grid Code.
Warning Notice SDC A Notice issued by NTDC to a Generator pursuant to
the Operating Code informing the Generator that it has
failed to comply with a Dispatch Instruction.
G&D 423
Sr. Item Definition Reference
No
.
1 Act Means the Regulation of Generation, Application and
Transmission and Distribution Electric Power Modification
Act, 1997 (XL of 1997). Procedure Rules-
1999
2 Affiliate In relation to any person, means any person Licensing Rules
who owns or controls, or is owned or (Distribution) 1999
controlled by, or is under common ownership
or control with, the person, and for that Licensing Rules
purpose of this definition. (Generation) 1999
(a) Control Transmission

Means the right, power or ability to influence Licence to NTDC
or Transmission Licence to determine any
decision in respect of the conduct of NTDC
affairs of the person under control.
(b) Ownership
Means the ownership or the right to own the
shares or voting securities of the persons
owned.
3 Agreement and Means the fuel Supply Agreement, the Generation licence
Agreements Implementation Agreement, the Power to IPP
Purchase Agreement and any or all them.
• Security Package
• Project Co-ordination Agreement
4 Ancillary Services Means the services ancillary o incident to the Licensing Rules
safe, reliable, stable and efficient availability (Generation) 1999
and utilisation of electrical energy and net
capacity and include without limitation, the Transmission
following, namely: Licence to NTDC
(a) energy imbalance service;
(b) spinning reserve service;
(c) supplemental reserve service;
(d) reactive supply voltage control service;
and
(e) regulation and frequency response
service.
5 Applicable Means the distribution licence, the second-tier Licensing Rules
Documents supply authorisation, NERPA rules and (Distribution) 1999
regulations. the grid code, the distribution
code and any documents issued under any of Licensing Rules
the foregoing or pursuant to the exercise of (Generation) 1999
the Authority's powers under the act, in each
case of a binding nature applicable to the Transmission
Licensee or where applicable, to its affiliates Licence to NTDC
and to which the Licensee or any of ·its
affiliates may be subject.
Feel Rules 2002
Means the rules and regulations issued in
pursuance of the Act by the Authority, from
time to time, relating to the generation,
distribution and transmission licenses, the grid
and distribution codes and any documents,
G&D 424
No
.
instruments, approvals or authorizations
issued or granted by the Authority in exercise
of its power under the Act
6 Applicant Means any person who applies for a Eligibility Criteria for
distribution licensee for provision of electric Consumers of
power service or modification thereof. Distribution
Companies 2003
7 Application Means an application made by a person in Application and
accordance with the provisions of these Modification
regulations and shall, where the context so Procedure Rules-
admits, include the documents in support, and 1999
application" shall be construed
accordingly.
8 Auditors Means the licensee's auditors for the time Licensing Rules
/being holding office in accordance with the (Distribution) 1999
requirements of the Companies Ordinance,
1984 (XLVII of 1984), or such other auditors as Licensing Rules
may be appointed in respect of the licensee (Generation) 1999
by the Authority from time to time in
accordance with these or the
distribution/generation licence.
9 Authorised/ Means in relation to any mailer, authorised in Licensing Rules
Authorized writing by the Authority. (Distribution) 1999
10 Authorised Electricity Means any person other than the Licensee, Transmission
Operator who is Transmission Licence to authorised by Licence to NTDC
the Authority through a licence or NTDC
otherwise for the purpose of using the
Licensee's
11 Authority Means the National Electric Power Regulatory Transmission
Authority constituted under section 3 of the Licence to NTDC
Act.
12 Authority Proposed Means a modification to a licence proposed by Application and
Modification the Authority. Modification
Procedure Rules-
1999
13 Authorized Officer Means the authorized by the Authority to NEPRA Service
perform functions under these Regulations. Regulations 2003
14 Available Means a generating unit or tie-line transfer Transmission
that is both (a) available in accordance with Licence to NTDC
the Grid Code and (b) declared as available for
the generation of electricity.
15 Average Energy For the purpose of Article 23 means energy Transmission
Charge charges to calculated on the basis of the Licence to NTDC
average of the month uniformly for the 24
hour period of each day of the month.
16 Balancing Services For the purpose of Article 8 means services to Transmission
be Licence to NTDC
rendered under a balancing arrangement for
the purpose of bilateral contracts for
dispatching plants, access to additional
generation for system needs and establish a
price for each operating time period at which
G&D 425
No
.
differences between contractual and real time
positions are settled.
17 Bulk Power Consumer Means in respect of and within the Service Licensing Rules
(BPC) Territory, such consumer who receives or (Distribution) 1999
purchases, electric power in the amount,
voltage level and frequency equal o or greater
than the characteristics of supply set out in
the distribution licence, provided that, the
Authority may change he characteristics o
supply for bulk-power consumers located
within the Service Territory at the time and in
the manner set out in the distribution licence.
Means a-consumer who purchases or receives NEPRA Act 1997

electric power, at one premises, in an amount
of one megawatt or more or in such other
amount and voltage level and with such other
characteristics as the Authority may
determine and the Authority may determine
different amounts and voltage levels and with
such other characteristics for different areas.
18 Capacity Charge For the purpose of Article 23 means monthly Transmission
capacity charge for the distribution Licence to NTDC
companies, proportional to the maximum
demand recorded al each metering
19 Common Distribution Means the distribution system as defined in Eligibility Criteria for
System the Consumers
distribution licence other than the dedicated Distribution
distribution system. Companies 2003
20 Communication Means any information, comment, Tariff Standards and
representation, pleadings, correspondence, or Procedures Rules
evidence filed with the Registrar, the presiding 1998
officer or the Authority in connection with any
proceedings.
21 Competent Authority Means the Authority, the appointing authority NEPRA Service
or any officer/senior employee of NEPRA who Regulations 2003
is designated by the Authority to exercise the
powers of the Competent Authority.
22 Competitive Market Means a date on which the first competitive Transmission
Operation Date trading period of a bilateral contracts market Licence to NTDC
(CMOD) shall commence.
23 Concession Territory Means the territory outside the Service Distribution licence
Territory of the licensee defined by the
administrative/geographical boundaries as
delineated in Schedule-I to this Licence.
Means the territory outside the Service Eligibility Criteria for

Territory of the distribution licensee defined Consumers of
by the administrative/geographical boundaries Distribution
as delineated in a distribution licence. Companies 2003
24 Connecting Point For the purposes of this Consumer Eligibility Eligibility Criteria for
Criteria means the point where the dedicated Consumers of
distribution system of the applicant is Distribution
G&D 426
No
.
connected with the existing common Companies 2003
distribution system.
25 Connection Means the provision of electric power supply Performance
services. Standards
(Distribution) Rules
2003
26 Connection Charges Means the charges made or levied or to be Licensing Rules
made or levied for the carrying out of works (Distribution) 1999
and provisions and installation of electrical
plant, electric lines and circuits and ancillary
distribution system together with charges in
respect of maintenance and repair of such
items in so far as not otherwise recoverable as
use of system charges and in respect of
disconnection and the removal of electrical
plant, electric lines and circuits, and ancillary
meters following disconnection, or such, other
charges as may be specified in or pursuant to
the distribution licence.
Licensing Rules
Means the charges made or levied or to be (Generation) 1999
made or levied for carrying out works for the
installation and maintenance of licensee
interconnection facilities.
27 Consents Means all permissions or approvals required Licensing Rules
from any public sector entity. (Distribution) 1999
Transmission licence
to NTDC
Means all permissions, approvals or consents Licensing Rules

required Licensing Rules by the licensee from (Generation) 1999
any public sector entity for the (Generation)
1999 purposes of the distribution business.
28 Consumer Means a person or his successor-in-interest NERPA Act 1997
who purchases or receives electric power for
consumption and not for delivery or re-sale to
others, including a person who owns or
occupies a premises where electric power is
supplied.
29 Consumer Eligibility Means the criteria for the eligibility of Licensing Rules
Criteria consumers to obtain supply of electric power (Distribution) 1999
developed by the Authority.
30 Consumer Service Means the manual of instructions developed Licensing Rules
Manual by the. licensee and approved by the (Distribution) 1999
Authority detailing instructions and guidance
to the consumers other than bulk-power
consumers occupying domestic, agricultural,
industrial or commercial premises for
obtaining electric power distribution services,
as more fully described in rule 9.
31 Core Business Means each of the transmission business and Transmission
tie-line business. Licence to NTDC
32 Cost per Unit of For the purpose of Article 20 means the cost Transmission
G&D 427
No
.
Energy per kilo watt-hour (kWh) of electricity as Licence to
determined and verified by an independent NTDC
assessor.
33 Dedicated Means that part of the distribution system, Eligibility Criteria for
Distribution System required to supply power for the sole Consumers of
consumption of an applicant and not for Distribution
supplying power to any other consumer and Companies 2003
shall comprise of the distribution system from
the connecting point upto the interconnection
point of the applicant including the metering
and service wire and such other connection
arrangements.
34 Dispatch Means the issuance of instructions to the Licensing Rules
licensee by the national grid company, the (Generation) 2000
relevant national power control center or any
other entity established under the pooling and
settlement arrangement, as may by be
decided from time to time in this regard the
Authority, to schedule and control the
operation of the generation facilities in order
to make available or commence, increase,
decrease or cease the delivery of electric
power or the ancillary services, in accordance
with the applicable documents.
35 Distribution Means the ownership, operation, management NEPRA Act 1997
or control of distribution facilities for the
movement or deliver or sale to consumers of
electric power but shall not include the
ownership, operation, management and
control of distribution facilities located on
private property and used solely to move or
deliver electric power to the person owning,
operating, managing and controlling those
facilities or to tenants thereof.
36 Distribution Business Means the business of distribution of electric Licensing Rules
power carried on or to be carried on by the (Distribution) 1999
licensee pursuant to and in accordance with
the terms of the distribution licence granted to
the licensee.
37 Distribution Code Means the distribution code referred to in rule Licensing Rules
15. (Distribution) 1999
38 Distribution Company Means a person engaged in the distribution of NEPRA Act 1997
electric power.
39 Distribution Facilities Means electrical facilities operating at the NEPRA Act 1997
distribution voltage and used for the
movement or delivery of electric power.
40 Distribution System Means the distribution facilities situated within Licensing Rules
the Service Territory owned or operated by (Distribution) 1999
the licenses for distribution of electric lined or
circuits, electric plant, meters,
interconnections facilities or other facilities
operating at the distribution voltage, and shall
also include any other electric lines, circuits,
G&D 428
No
.
transformers, sub-stations, electric plant,
interconnection facilities or other facilities
determined by the Authority as forming part of
the distribution system, whether or not
operating at the distribution voltage.
41 Distribution Voltage Means the any distribution voltage. below the NEPRA Act 1997
minimum transmission voltage.
42 Document-in-Support Means the documents to be provided with the Application and
application for the licence of subsequently, in Modification
accordance with regulation 3. Procedure Rules-
1999
43 Economic Dispatch Means system of establishing economic Transmission
precedence of electric power from available Licence to NTDC
generating units or tie-line transfers directed
by the Licensee or any other entity
established under competitive trading
arrangements.
Licensing Rules
Means the allocation of demand to individual (Generation) 1999
generation plants or units to effect the most
economical production of electricity for
optimum system economy, security and
reliability with due consideration of
incremental generation costs, incremental
power purchase costs, incremental
transmission and distribution losses, load flow
considerations and other operational
considerations as determined solely by the
national grid company, the relevant national
power control center or any other entity
established under the pooling and settlement
arrangement, as the Authority may, from lime
to lime in this regard, decide.
44 Electric Power Means electrical energy or the capacity for the NEPRA Act 1997
production of electrical power.
45 Electric Power Means the generation, transmission or NEPRA Act 1997
Services distribution of electric power and all other
services incidental thereto.
46 Emergency Means cases where the patient requires NEPRA Service
immediate medical attention and any delay Regulations 2003
may be detrimental to his/her health.
47 Encumbrance Means any mortgage, charge, right of Transmission
possession, Transmission Licence to Licence to NTDC
assignment by way of security, right of
possession or NTDC
other form of security interest.
48 Energy Imbalance Means the provision of electrical energy for Licensing Rules
Service any hourly Licensing (Generation) Rules19 (Generation) 1999
or half-hourly mismatch between the supply
and 99 demand at any given point of delivery.
49 Financial Year Means a consecutive period of twelve calendar Fee Rules 2002
months Fee Rules 2002 commencing on the
first day of July o any year and ending on the
G&D 429
No
.
301n day of June of the following year.
50 Fuel Supply Means the Fuel Supply Agreement dated _____ Generation Licence
Agreement as IPP Generation Licence to mentioned, to IPP
modified, updated, revised or restated
between the Licensee and the Fuel Supplier
thereof(i)
51 Generation Means the ownership, operation, management NERPA Act 1997
or control of generation facilities for delivery
or sale of electric power and not solely for
consumption by the person owning, operating,
managing, and controlling those facilities.
52 Generation business Means the business of availability and Licensing Rules
provision of electric power or ancillary services (Generation) 2000
or other related business through the
construction, ownership, management, control
or operation of the generation facilities or the
licensee interconnection facilities carried out,
or to be carried out, by the licensee, whether
itself or through an agent or sub-contractor
approved in this behalf by the Authority,
pursuant to and in accordance with the terms
of the generation licence granted to the
licensee and, where applicable, includes the
second-tier supply business carried out by the
licensee.
53 Generation company Means a person engaged in the generation of NEPRA Act 1997
electric power.
54 Generation facility Means the electrical facility used for the NEPRA Act 1997
production of electric power.
55 Glossary of Standards Means as provided in Schedule-I of Performance
Performance Standards (Distribution) Rules Standards
2003. (Distribution) Rules
2003
56 Grid Code Means the grid code prepared by the national licensing
grid company or in the absence of the national (Distribution) Rules
grid company by the transmission licensees 1999
pursuant to the transmission licenses and
approved by the Authority, as from time to
time revised with the approval of the
Authority.
Means the grid code prepared by the national licensing

grid company with the approval of the (Generation) Rules
Authority. 1999
57 Hydro licensee Means a generation licensee constructing, licensing Rules
owning, operating or managing hydel (Generation) 1999
generation facilities.
58 Implementation Means the Implementation Agreement dated Generation licence
Agreement ___ as amended, modified, updated, revised or to IPPs
restated between the Licensee and the
President of Pakistan. (ii)
59 Incremental Means the additional cost that would be licensing
generation cost incurred by producing the next available unit (Generation) Rules
G&D 430
No
.
of electrical energy. 1999
60 Information Includes documents, accounts, reports, Application and
records, data, returns or estimates of any Modification
description. Procedure Rules-
1999
61 Information direction Means a direction issued by the authority or Tariff, Standards
the presiding officer to any person to provide and Procedures
information to the Authority. 1998
62 Interconnection Point Means the point where the metering Eligibility Criteria for
installation and protection apparatus of the Consumers of
consumer is connected to the dedicated Distribution
distribution system. Companies 2003
63 Interconnection Means the equipment, including, without licensing
Facility/Facilities limitation, electrical lines or circuits, (Distribution) Rules
transformers, switchgear, safety and 1999
projective devices, meters or electrical plant,
used for interconnection services.
Means plant and equipment, including the

electrical lines or circuits, transformers, Licensing Rules
switchgears, safety and protective devices or (Generation) 1999
meters used for interconnection services.
DRC
64 Inter-connection Means the connection of one company's NEPRA Act 1997
service electrical facilities to another company's
electrical facilities.
65 Intervention request Means an intervention request filed under rule Tariff, Standards
6. and Procedures
2002
66 KESC Means the Karachi Electric Supply Corporation, NEPRA Act
a public limited company, incorporated under
the Companies Act, 1913.
67 kV Means kilovolts or 1,000 volts. Performance
Standards
2003
68 Laws Include all statutes, rules and regulations licensing Rules
made pursuant thereto, judicial decisions, (Distribution) 1999
administrative practices or direction having
the force of law in Pakistan, in each case as licensing Rules
may be applicable to the Licensee or its (Generation) 1999
affiliates.
Transmission licence
to NTDC
69 Licence Means a licence issued for generation, NEPRA Act 1997
transmission or distribution under this Act.
70 Licensee Means a holder of a licence NERPA Act 1997
71 Licensee Means the interconnection facilities Licensing Rules
interconnection constructed, owned, operated or managed by (Generation) 1999
the licensee.
72 Licensee proposed Means a modification to the licence proposed Application and
modifications by the licensee. Modification
Procedure Rules-
G&D 431
No
.
1999
73 Licensee's Means the licensee's investment programme Licensing Rules
investment referred to in rule 17. (Distribution) 1999
programme
74 Licensee's power Means the licensee's power acquisition Licensing Rules
acquisition programme referred to in rule 12. (Distribution) 1999
programme
75 Load Shedding Means the process of deliberately removing Performance
either manually or automatically pre-selected Standards
consumer's load demand from the power (Distribution) Rules
system as per scheduled programme on a 2003
rotating and proportionate basis for each class
of consumers notified earlier by the DISCOs.
76 Long Duration Power Means loss of electric supply to one or more Performance
Supply Interruption consumers for a duration of more than three Standards
minutes. (Distribution) Rules
2003
77 Metering Installation Means the metering and associated Eligibility Criteria for
equipment required to be installed for Consumers of
recording consumption/usage of electric Distribution
power of an applicant. Companies 2003
78 Minimum Means sixty-six kilovolts or such other voltage NEPRA Act 1997
transmission voltage that the Authority may determine to be the
minimum voltage al which electrical facilities
are operated when used to deliver electric
power in bulk.
79 Motion Means any oral or, if so directed by the Tariff, Standards
Authority, written application in relation to any and Procedures
matter of procedure under these rules. 1998
80 National grid Means the person engaged in the transmission NEPRA Act 1997
company of electric power and granted a licence under
section 17.
81 NEPRA (Fees and Means the rules developed by the Authority in Application and
Penalties) rules respect of the payment of fees by the Modification
licensees and the procedure for imposition Procedure Rules-
and payment of fines and penalties levied by 1999
the Authority.
82 NEPRA rules and Means the relevant rules and regulations Licensing Rules
regulations made by the Authority under the Act. (Distribution) 1999
licensing Rules
(Generation) 1999
83 Net capacity Means the aggregate of the maximum rating licensing Rules
of the generation facilities constructed, (Generation) 1999
owned, managed, controlled or operated by
the licensee under its generation licence,
modified for ambient limitations, which is
established in the manner specified in the grid
code, the generation licence or a power
acquisition contract entered into by the
licensee, less the capacity used to supply the
auxiliary needs.
84 NTDC Means National Transmission and Dispatch Performance
G&D 432
No
.
Company Standards
(Distribution\ Rules
2003
85 Operator Means a person authorized by the distribution Performance
company to operate its electrical facilities. Standards
2003
86 Ordinance Means the Companies Ordinance, 1984. Application and
Modification
Procedure Rules-
1999
87 Penalty Means a penalty, which may be imposed NEPRA Fee and Fine
under these Regulations. Rules 2002
88 Person Shall include an association of persons, NEPRA Act 1997
concern, company, firm or undertaking.
89 Petition Means a petition made to the Authority for the Tariff, Standards
determination, modification or revision of and Procedures
tariff. 1998
90 Planned Power Means planned or scheduled outage of Performance
Supply Interruption electrical supply to one or more consumers. In Standards
the event of Planned Power Supply (Distribution) Rules
Interruption, notice shall be served to all 2003
affected consumers at least forty-eight hours
in advance of any such planned outage
excluding defence establishments where
Planned Power Supply Interruptions will only
be taken through mutual agreement.
91 Pleadings Means the petition, the replies to the petition Tariff, Standards
and rejoinders to replies. and Procedures
1998
92 Point of Outage Means the point in the distribution system of a Performance
distribution company beyond which electric Standards
service is interrupted including without (Distribution) Rules
limitation: Grid station, 11 kV feeders, 2003
400/230 volts line, and transformer.
93 Pooling and Means any arrangements implemented by or Licensing Rules
settlement under the directions of the Authority for the (Distribution) 1999
arrangements spot or market-based sales and purchases of
electric power through an electric power
exchange or other means.
Means the arrangements for establishing or Licensing Rules

implementing a wholesale market for the sale (Generation) 1999
and purchase of electrical energy, net
capacity or ancillary services under the
relevant NEPRA rules and regulations.
94 Power acquisition Means a contract or other arrangement for the Licensing Rules
contract acquisition by the licensee, whether through (Distribution) 1999
sale and purchase for consideration or
otherwise, of electric Licensing Rules power Licensing Rules
including, where applicable a contract for (Generation) 1999
(Generation) 1999 purchase of electric
power .on the basis of difference in prices of
G&D 433
No
.
electric power between the rates pursuant to
the pooling and settlement arrangements and
the rates determined according to the method
stated in such contract.
95 Power Purchase Means the Power Purchase Agreement dated Generation Licence
Agreement ___ as amended, modified, updated, revised or to IPPs
restated between the Licensee and the power
purchaser thereof. (iii)
96 Power Supply Means loss of electric supply to one or more Performance
Interruption consumers. Standards
2003
97 Prescribed Means prescribed by rules made under this NERPA Act 1997
Act.
98 Presiding Officer Means the presiding officer appointed by the Tariff, Standards
Authority Tariff. Standards and under sub-rule and Procedures
(5) of rule 9 and, for the purpose of 1998
Procedures 1998 these rules, where the
context so admits, shall also mean the
Authority.
99 Proceedings Means the entire process commencing from Tariff, Standards
the date of Tariff, Standards and filing of and Procedures
petition with the Registrar or, where the 1998
Procedures 1998 authority initiates the
process of determination of tariff, the date of
such initiation by the Authority, and ending on
the date the Authority makes its final
determination on a petition, and shall include
any stage during the proceedings.
10 Prospectus Means a report prepared by the applicant Application and
0 setting out: Modification
i) a brief introduction of the applicant Procedure Rules-
ii) the salient features of the facility 1999
iii) the facility or the system in respect of
which the licence is sought;
iv) the proposed investment; and
v) the social and environmental impact of the
proposed facility or system in a non-
technical and commonly understood
language.
10 Prudent utility Means the practices of an operator of an Licensing Rules
1 practices electric power undertaking seeking in good (Distribution) 1999
faith to perform its obligations and in the
conduct of its undertaking exercising that
degree of skill, diligence, prudence and
foresight which would reasonably be expected
from a skilled and experienced operator and
complying with the relevant Laws and codes.
Means the practices of an operator of an Licensing Rules

electric power undertaking seeking in good (Generation) 1999
faith to perform its obligations and in the
conduct of its undertaking exercising that
G&D 434
No
.
degree of skill, diligence, prudence and
foresight which would reasonable be expected
from a skilled and experienced operator
complying with the Laws an applicable
documents.
10 Public conveyance Means a plane, train, or other mode of NEPRA Regulations
2 conveyance used for travel and is not owned Service 2003
by the employee.
10 Public sector entity Means any authority, agency, division or Licensing Rules
3 instrumentality of the Federal or Provincial (Distribution) 1999
Government or a local authority but does not
include the Authority. Licensing Rules
(Generation) 1999
Transmission
Licence to NTDC
10 Public sector project Means generation, transmission or distribution NEPRA Act 1997
4 facilities NEPRA Act 1997 constructed, owned,
managed or controlled by the Federal
Government, a local authority or anybody
owned or controlled by any such Government
or Authority.
10 Reactive supply and Means the provision of reactive power through Licensing Rules
5 voltage control changes to the generator reactive output to (Generation) 1999
service maintain transmission line or distribution line
voltage.
10 Regulation and Means the provision for moment-to-moment Licensing Rules
6 frequency response variations in the demand or supply for (Generation) 1999
service maintaining scheduled interconnection
frequency.
10 Regulations Means regulations made under this Act. NEPRA Act 1997
7
10 Rules Means the National Electric Power Regulatory Transmission
8 Authority rules made under section 46 of the Licence to NTDC
Act.
Licensing Rules
Means the National Electric Power Regulatory (Generation) 1999
Licensing Rules Authority Licensing
(Generation) Rules, 2000, as (Generation)
1999 amended from time to time.
10 Rural Area Means the area falling within the jurisdiction of Performance
9 all rural local bodies, including without Standards
limitation union councils, tehsil councils and (Distribution) Rules
zila councils. 2003
11 Sale period For the purpose of Article 23 means the period Transmission
0 of a month, day, 4 hour, hour or half an hour Licence to NTDC
during which the generation charges for all
the power stations are averaged out on a
weighted average basis to determine. the sale
rate and transfer price for sale to distribution
companies or other entities receiving electric
power through central power purchasing
agency.
G&D 435
No
.
11 Schedule Means the Schedule to these rules. Fee Rules 2002
1
11 Second-tier Supplier Means any licensee authorized to carry out Licensing Rules
2 the second-tier supply business. (Distribution) 1999
11 Second-tier supply Means an authorization to engage in the Licensing Rules
3 authorization second-tier supply business. (Distribution) 1999
11 Second-tier supply Means the authorised business, if any, of the Licensing Rules
4 business licensee or any of its affiliates as a supplier, (Distribution) 1999
whether or not carried out pursuant to a
power acquisition contract, of electric power
to one or more bulk-power consumers within
or without the Service Territory.
Means the authorized business, if any, of the Licensing Rules

licensee or any of its affiliates as a supplier of (Generation) 1999
11 Separate business Means each of the transmission business of Transmission
5 the Licensee, tie-line business of the Licensee, Licence to NTDC
the provision of settlement services and any
other business of the Licensee, undertaken
separately.
Licensing Rules
Means-each of the distribution business, the (Distribution) 1999
second- tier supply business or any other
business taken separately from one another
and from any other business of the licensee or
any affiliate of the licensee.
Licensing Rules
Means each of the generation business, the (Generation) 1999
second- tier supply business, the provision of
ancillary services or any other business taken
separately from one another and from any
other business of the licensee or any affiliate
of the licensee.
11 Service territory Means the area specified in the distribution Licensing Rules
6 licence within which the licensee is authorised (Distribution) 1999
to conduct the distribution business and,
subject to the provisions of rule 7, the second-
tier supply business.
11 Short Duration Power Means loss of electric supply to one or more Performance
7 Supply Interruption consumers for a duration of three minutes or Standards
less excluding momentary interruptions of (Distribution) Rules
duration less than one second. 2003
11 SHYD0 Means the Sarhad Hydel Development NEPRA Act 1997
8 Organization, established under the Sarhad
Hydel Development Orqanization Act, 1993
(NWFP Act No. 1 of 1993).
11 Small Power Means owner of a generation facility of below Transmission
9 Producers 100 MW gross capacity, who was engaged in Licence to NTDC
generation and sale of electric power as on
22nd April, 2000 and who has not signed any Distribution Licence
power purchase agreement with WAPDA or
KESC or an implementation agreement with
the Government of Pakistan.
G&D 436
No
.
12 Spinning reserve Means the provision of additional capacity Licensing Rules
0 service from generating units that are on-line, loaded (Generation) 1999
to less than their maximum output, and
available to serve system demand
immediately should be contingency occur.
12 Step Potential Means difference of voltage between the steps Performance
1 of an operator, human being or animal coming Standards
in contract or operating electrical facilities of (Distribution) Rules
the distribution company. 2003
12 Supplemental Means the provision of additional capacity Licensing Rules
2 reserve service from generating units that can be used to (Generation) 1999
Interruption Duration respond to a contingency within the period
Index (SAIDI) defined in this behalf in the grid code.
12 System Average Means the average duration of consumer Performance
3 Power Supply Interruptions per consumer Standards
occurring in a given year. SAIDI is the average (Distribution) Rules
time the consumers of a distribution company 2003
who remained without power. It is determined
by dividing the aggregated sum of all
consumers power supply interruption
durations in minutes by the total number of
consumers served by a distribution company
in a given year.
12 System Average Means the average frequency of consumer Performance
4 Interruption Power Supply Interruptions per consumer Standards
Frequency Index occurring in a given year. SAIFI is calculated (Distribution) Rules
(SAIFI) by dividing the total annual number of 2003
consumer Power Supply Interruptions by the
total number of consumers served by a
distribution company in a given year.
12 Tariff Means the rates, charges, terms and Tariff. Standards
5 conditions for generation of electric power, and Procedures
transmission, interconnection, distribution 1998
services and sales of electric power to
consumers by a licensee
12 Technical limits Means the limits and constraints relating to Licensing Rules
6 the operation, maintenance and dispatch of a (Generation) 1999
generation facility, as agreed to between an
applicant for a licence and the Authority at the
time of grant of the generation licence or
subsequently as determined by the Authority,
or between the licensee and any purchaser,
procurer or recipient of electric power or
ancillary services from the licensee, consistent
with the technical functional specifications set
out in the schedule to the generation licence
pursuant to sub-rule (2) of the rule 3, the grid
code and any applicable distribution code and
not inconsistent with the applicable
documents.
12 Tie-line Means interconnection facility for the transfer Transmission
7 of electric power between the Licensee and Licence lo NTDC
other utilities not governed by the Act.
G&D 437
No
.
12 Total system Means the Licensee's transmission system and Transmission
8 the transmission and distribution systems of Licence lo NTDC
all authorised electricity operators located in
Pakistan.
12 Transmission Means the ownership, operation, management NEPRA Act 1997
9 of control of transmission facilities.
13 Transmission Means the business of transmission of electric Transmission
0 Business power carried on or to be carried on by the Licence to NTDC
Licensee pursuant to and in accordance with
the terms or this Licence in planning,
development, construction and maintenance
of the Licensee's transmission system and
operation of such system for the transmission
and dispatch of electric power including the
balancing services and inter-connection
services.
13 Transmission Means electrical transmission facilities NEPRA Act 1997
1 facilities including electrical circuits, transformers and
sub-stations operating at or above the
minimum transmission voltage but shall not
include:
a. electrical circuits forming the immediate
connection between generation facilities
and the transmission grid to the extent
that those circuits are owned by a
generation company and are directly
associated with that company's generation
facilities; and
b. specified facilities operating at or above
the minimum transmission voltage which
the Authority, upon an application by a
licensee under section 20 determines, shall
be owned and operated by a distribution
licensee.
13 Transmission System Means one or more systems comprising Licensing Rules
2 electrical facilities including. without (Distribution) 1999
limitation, electrical wires or circuits, electrical
plant, transformers, sub-stations, switches, Licensing Rules
meters, interconnection facilities or other (Generation) 1999
facilities operating at or above minimum
transmission voltage constructed, owned, Transmission
managed, controlled or operated by the Licence lo NTDC
Licensee or by one or more special purpose
transmission licensees and used for
transmission of electric power from the
generation facility to sub-stations or to or from
other generation facilities or between sub-
stations or to or from any interconnection
facilities or from the distribution facilities of
one licensee to the distribution facilities of
another licensee or from a generation facility
to a distribution facility or a bulk-power
consumer
G&D 438
No
.
13 Unit commitment Means turning-on and bringing up to speed Licensing Rules
3 any one or more of the generation units (Generation) 1999
comprised in the generation facilities of the
licensee and synchronizing and connecting
such units to the transmission system for the
delivery of electric power or ancillary services
and, where the context so admits, includes the
process by which the determination as to
which units are to be committed is made.
13 Urban area Means the area falling within the jurisdiction of Performance
4 all urban local bodies or development Standards
authorities, including without limitation, town (Distribution) Rules
committees, municipal committees, municipal 2003
corporations, metropolitan corporations and
cantonment boards.
13 Use of system Means the use of the distribution system for Licensing Rules
5 the transport of electric power by and for and (Distribution) 1999
on behalf of the licensee and, in relation to a
second-lier supplier other than the licensee,
for and on behalf of such second-lier supplier.
Means the use of the transmission system or Licensing Rules

one or more distribution systems for the (Generation) 1999
transport or deliver of electric power or
ancillary services.
13 Use of system The charges made or levied or to by made or Licensing Rules
6 charges levied by the licensee for the use of the (Distribution) 1999
system for the purpose of the distribution
business or the second-tier supply business or
in respect of the use of the distribution system
by a second-tier supplier but shall not include
connection charges.
Licensing Rules
The charges made or levied by the national (Generation) 1999
grid company, a special purpose transmission
licensee or a distribution licensee, as the case
may be, for the use by the licensee of their
respective systems for the purposes of its
generation business.
13 WAPDA Means the Pakistan 1Nater and Power NEPRA Act 1997
7 Development Authority established under the
Pakistan Water and Power Development
Authority Act, 1958 (W.P. Act XXXI of 1958).
13 WAPDA relevant The instructions, manuals or guidelines used Licensing Rules
8 manuals by WAPDA in relation to the matters to which (Distribution) 1999
such instructions, manuals or guidelines
relate. Licensing Rules
(Generation) 1999
13 Year Means a financial year. NEPRA Service
9 Regulations 2003
14 Year or Annual For the purpose of these Rules means the Performance
0 period of twelve months beginning on 1st July Standards
and ending on 30th June. (Distribution) Rules
G&D 439
No
.
2003
NTDC Grid Code Addendum No. 1

(Revision-1)
G&D 440
for Grid Integration of Wind Power
Plants (WPP)
DNV GL EDIT
G&D 441
Contents
1. General 449
2. Definitions 449
3. Wind Turbine Generator Technology Requirements 451
4. Generator Data Requirements 451
5. Black Start and Islanded Operation Requirements 451
6. Synchronization / De-Synchronization 451
7. Transmission System Frequency ranges: 451
7.1 Active Power Control 452
7.2 Frequency Response 452
8. Transmission System Voltage requirements 455
8.1 Transmission System Voltage ranges 455
9. LVRT/HVRT Requirements 461
10. Power Quality Requirements 464
11. Signaling and Control 465
12 Power Generation Capability Forecasting Requirements 465
13. Limitation on Total Grid Connected Wind Power Capacity 466
Appendix-I 467
G&D 442
1. General
(i) This addendum is applicable only to grid-connected wind power plants
(ii) This addendum becomes part of the Grid Code with immediate effect.
(iii) All other clauses of Grid Code, which are not covered by this addendum, if otherwise
applicable as such, shall be applicable to Grid connected Wind Power Plants.
(iv) All relevant clauses of Grid Code, which are covered through this addendum, shall be
treated as amended as per this addendum.
(v) Any provisions of this addendum which have not been previously provided in the Grid
Code, shall now form part of the Grid Code, applicable to Wind Power Plants including
already Grid-connected wind power plants.
(vi) NEPRA may approve any subsequent modification to this addendum proposed by NTDC
through the Grid Code Review Panel (GCRP). However, a Grid-connected Wind Power Plant
may operate, for its full EPA term, in compliance to the Grid Code prevailing at the time of
its financial closing.
(vii) Notwithstanding anything contained in this Grid Code Addendum No. 1 (Revision-1) for
Wind Power Plants, the Regulator may review, amend, modify or change the Addendum
from time to time.
2. Definitions
2.1 Black Start
As defined in the Grid Code
2.2 Fixed Speed WTG

A WTG, whose rotor speed depends on wind speed with no arrangements to vary thus
determined speed.
2.3 Energy Purchase Agreement

The agreement, along with all schedules and annexures attached therewith, by and
between the seller and the purchaser, for the purposes of sale and purchase of electrical
energy from a power project.
2.4 Financial Closing

As defined in the relevant Energy Purchase Agreement (EPA).
2.5 Forecasting Error Rebate

This is the rebate that Seller would pay to purchaser against the error of forecasted Net
Delivered Energy for a specified period as percentage of the Energy Payment invoiced by
the Seller for the same period
2.6 Grid Connected Power Plant

A power plant which can deliver electrical energy to the National Grid System / DISCO
Systems.
2.7 High Voltage Ride Through (HVRT)

The capability of a generator to withstand the impact of high voltage swell, for a certain
transient time, to remain connected to grid without being damaged, in case of external
fault conditions
2.8 Hybrid Generating System

A generating system in which the power plant utilizes more than one input power
resources in order to overcome deficiencies in one or all resources.
2.9 Islanded Operation
G&D 443
Operational mode of a power plant in which it stands alone in generating electrical
power and feeding a particular load with no other generator running in parallel.
2.10 Low Voltage Ride Through (LVRT)

The capability of a generator to withstand the impact of low voltage dip, for a certain
fault conditions.
2.11 Net Delivered Energy

This is the net energy delivered to the grid at the Point of Common Coupling
2.12 Pitch Control

The control which is capable of varying angle of blades of WTG thus changing energy
perceived by WTG resulting in change of rotor speed.
2.13 Point of Common Coupling (PCC)

The point of connection for off-take of power from a Wind Power Plant to the network of
Transmission / Distribution Company. It may also be termed as Point of Connection (POC).
2.14 Purchaser
As defined in Energy Purchase Agreement (EPA)
2.15 Ramp Rate

Upper limit of a generator in terms of rate of increase of real power (MW/min).
2.16 Regulator
National Electric Power Regulatory Authority (NEPRA) established under Section 3 of
NEPRA Act.
2.17 Retained Voltage

The value of voltage, normally in percentage of normal rated voltage, which persists at a
particular point of a grid system in case of fault conditions.
2.18 Seller
2.19 Strategic Generation Expansion Plan
Strategic Generation Expansion Plan covering all types and technologies of generation
including all renewable resources and considering overall energy policies/priorities of
Government.
2.20 Stuck Breaker Case

A case of fault condition at a grid system, in which the fault is not cleared by operation of
the concerned breaker, being stuck, and is therefore cleared by the breaker(s) at zones
other than faulty zone.
2.21 Term
The total period of Energy Purchase Agreement for sale and purchase of electrical energy.
2.22 Variable Speed WTG

A WTG having arrangements to vary its rotor speed.
2.23 Wind Farm Controller

Master controller of entire Wind Farm having supervisory control on all WTGs’ local
controllers and also controls all outputs/inputs to/from the Grid at Point of Common
Coupling as shown in Figure-1
G&D 444
Figure 9
2.24 Wind Power Plant (WPP)

An installation including equipment and devices attached therewith, with the
capability of converting kinetic energy of wind into electrical energy.
2.25 Wind Turbine Generator (WTG)

A set of turbine, generator and other devices, capable of converting kinetic energy of
wind into electrical energy.
3. Wind Turbine Generator Technology Requirements

The criteria of Wind Turbine Generator (WTG) selection shall be based on compatibility with the National
Grid System/DISCO Systems, improved operating performance, and optimal efficiency.
4. Generator Data Requirements

A grid-connected WPP shall be required to provide "Generator Data" applicable to the type of the Wind
Turbine Generator (WTG) being installed. In addition, the WPP shall provide Standard Planning Data as
outlined in the Grid Code to the extent applicable.
5. Black Start and Islanded Operation Requirements

A WPP is exempted from Black Start and Islanded Operation for full term of Energy Purchase Agreement.
6. Synchronization / De-Synchronization
A WPP shall, through appropriate necessary equipment be capable of managing, without feeling jerk(s)
on the National Grid System / DISCO Systems, the following:
(a) Smooth synchronization
(b) Smooth de-Synchronization
7. Transmission System Frequency ranges:

WPP shall have the capability to:
(a) Operate continuously at normal rated output at Transmission System Frequencies in the range
49.5 Hz to 50.5 Hz;
(b) Remain connected to the Transmission System at Transmission System Frequencies within
the range 47.5 Hz to 52.0 Hz for a duration of 60 minutes;
G&D 445
(c) Remain connected to the Transmission System at Transmission System Frequencies within
the range 47.0 Hz to 47.5 Hz for a duration of 20 seconds required each time the Transmission
System Frequency;
(d) Remain connected to the Transmission System for a Rate of Change of Frequency up to and
including 0.5-1 Hz per second as measured over a rolling 500 milliseconds period. Voltage dips may
cause localized ROCOF values in excess of 1 Hz per second for short periods, and in these cases, the
Fault-Ride Through clause supersedes this clause. For the avoidance of doubt, this requirement
relates to the capabilities of WPP only, and does not impose the need for Rate of Change of
Frequency protection nor does it impose a specific setting for anti-islanding or loss-of-mains
protection relays.
No additional Generation Unit shall be started while the Transmission System Frequency is
above 50.2 Hz.
WPP1.5.2 Active Power Management

A WPP Control System shall be installed by the WPP to allow for the provision of Active Power
Control and Frequency Response from the WPP. The WPP Control System and Frequency
Response System shall provide the functionality as specified in this section WPP1.5.2.
7.1 Active Power Control

WPP1.5.2.1 Active Power Control
The WPP Control System shall be capable of operating each Generation Unit at a reduced level if
the WPP’s Active Power output has been restricted by the TSO. In this Active Power Control
Mode, the WPP Control System shall be capable of receiving an on-line Active Power Control Set-
point sent by the TSO and shall commence implementation of the set-point within 10 seconds of
receipt of the signal from the TSO. The rate of change of output to achieve the Active Power Control
Set-point should be the Active Power Control Set-Point Ramp Rate setting of the WPP Control
System, as advised by the TSO, as per xxxxxx. The TSO acknowledges that if the Active Power output
of the WPP is initially less than the Design Minimum Operating Level PMIN, and if the WPP is
expected to increase its Active Power output, then it may not be able to achieve the specified ramp
rate at first, due to Generation Units going through a start-up sequence. In such a case, Generation
Units shall start up as quickly as the technology allows, and in any case, not longer than three minutes
from the time the Active Power Control Set-point was received.
7.2 Frequency Response
Frequency Control
(i) Grid-connected WPPs shall be exempted from the responsibility of frequency regulation and
control for the “Frequency Sensitive Mode” which is defined by the range between 49.8Hz and
50.2Hz according to OC 4.8.1 (c, ii) of the Grid Code.
(ii) Above 50.2Hz, when frequency enters “Tolerance Frequency Band”, with upper range defined as
50.5Hz according to OC 4.8.1 (c, iii), of the Grid Code, all the Grid-connected WPPs should
contribute to a frequency stabilization by reducing active power as described in Figure-2 below:
G&D 446
Figure 10
(iii) If the Frequency rises above FD=51.5 Hz, then the Frequency Response System shall act to
reduce the Active Power output of the WPP to its design PMIN before the cut-off value. If the
Frequency rises above FE=52.0 Hz, then the Frequency Response System shall act to reduce the
Active Power output of the WPP to zero. Any Generation Unit which has disconnected shall be
brought back on load as fast as technically feasible, provided the Transmission System Frequency
has fallen below FC=50.5 Hz.
(iv) Droop control shall be within 2 to 10%, depending on TSO request, with default value of 4%, see
Figure-3.
(v) If the Frequency drops below FB=49.5 Hz, the WPP must be capable to keep the Active Power
output constant as a % of the Available Active Power resulting at frequency F B
(vi) For steady state frequency regulation, all Gird connected WPPs, shall be capable of managing the
following, through Pitch Control, disconnection/connection operations of the WTG or any other
control, as per dispatch instructions by System Operator (NPCC/RCC/or Any Licensed Dispatcher):
(a) Load adjustments in the range of zero to 100% of available power subject to
availability of wind speed.
(b) A minimum Ramp Rate of 10% of plant available power per minute subject to
availability of wind speed.
G&D 447
Figure 11- WPP frequency control requirements
(vii) Error: Reference source not found shows the Transmission System Frequency and Active Power
ranges for FB, FC, FD, FE, PA, PB, PC, PD and PE.
Table 7- Reference of frequencies in Figure 3

Transmission Available Active Power (%)
Active Power
System Frequency
Name Registered Capacity ≥ 5 MW
(Hz)
FB 49.5-50 PB
FC 50-50.2 PC 15-100
FD PD 15-100 but not less than PMIN
FE 50.5-52.0 PE 0
If the Transmission System Frequency rises to a level above ‘D’-’E’, as defined by the Power-
Frequency Response Curve in Figure 3, the TSO accepts that Generation Units may disconnect. Any
Generation Unit which has disconnected shall be brought back on load as fast as technically feasible
(provided the Transmission System Frequency has fallen below 50.2 Hz). The Frequency Response
System shall continuously monitor the Transmission System Frequency in order to continuously
determine the WPP appropriate Active Power output by taking account of the WPP Available Active
Power or Controlled Active Power. No time delays, such as moving average frequency filters, other
than those necessarily inherent in the design of the Frequency Response System shall be introduced.
Ramp Rates
The WPP Control System shall be capable of controlling the ramp rate of its Active Power output.
There shall be three ramp rate capabilities, designated Resource Following Ramp Rate, Active Power
Control Set-Point Ramp Rate, and Frequency Response Ramp Rate.
The WPP Control System shall operate the ramp rates with the following order of priority (high to low):
Frequency Response Ramp Rate; Active Power Control Set-Point Ramp Rate; Resource
Following Ramp Rate.
The Resource Following Ramp Rate shall be used during Start-Up, normal operation, and Shutdown.
The TSO shall specify the Resource Following Ramp Rate and the Active Power Control Set-Point
G&D 448
Ramp Rate in percentage of Registered Capacity per minute. The Frequency Response Ramp Rate
shall be the maximum possible ramp rate of the WPP agreed with the TSO and with the characteristics
as set out in WPP1.5.3.1. The TSO acknowledges that rapidly changing resource availability may cause
temporary deviations from the ramp rate settings of the WPP.
8. Transmission System Voltage requirements

8.1 Transmission System Voltage ranges
WPP shall remain continuously connected to the HVAC Transmission System at maximum Available
Active Power or Controlled Active Power and operate within the ranges of the Transmission
System Voltage at the Connection Point, for an unlimited time period, as specified below:
a. 1100 kV system: 1,045 kV to 11,885 kV
b. 765 kV system: 726 kV to 826 kV
c. 500 kV system: 475 kV to 540 kV
d. 220 kV system: 209 kV to 238 kV

e. 132 kV system: 125 kV to 143 kV
Reactive Power and Voltage Control

A WPP Controller must be able to operate in either power factor, reactive power or voltage control as
follows:
(i) Power Factor:

A WPP shall manage at the Point of interconnection the reactive power control to maintain the
power factor within the range of 0.95 lagging to 0.95 leading, over the full range of plant
operation, as per dispatch instructions and/or voltage adjustments/requirements within the above
range of power factor.
(ii) Reactive Power:

A WPP shall manage at the Point of interconnection the reactive power control within the
setpoints of Qmin and Qmax as Per Unit of full output of Plant as shown in Figure-4. The setpoints
of Qmin and Qmax would be as follows:
 Qmin = -0.33 P.U. of Full Output

 Qmax = + 0.33 P.U. of Full Output
Figure 12
(iii)Voltage Control
G&D 449
A WPP must control voltage at POC along a voltage vs. reactive power characteristic as shown in
Figure 5. The following parameters are set as
 Voltage offset: ± 5 % under normal operating conditions and ± 10 % during contingency
conditions.
 Reactive power offset:± 0.33 PU of Full Output of Plant
 Droop (5 % of nominal voltage at max. reactive power)
Figure 13
WPP operating in Power Factor control mode, Voltage Control mode or constant Reactive Power
mode shall be at least capable of operating at any point within the P-Q capability ranges illustrated in
Error: Reference source not found6, as measured at the Connection Point over the normal and
disturbed Transmission System Voltage ranges specified in 8.1;, additional Reactive Power
compensation may be utilised to compensate for the Reactive Power demand of the connection
between the Connection Point and the WPP.
Referring to Error: Reference source not found6:
 Point A represents the maximum Mvar absorption capability of the Controllable WPP at
100% Registered Capacity and is equivalent to 0.95 power factor leading, i.e -0.33*Pn;
 Point B represents the maximum Mvar production capability of the Controllable WPP at
100% Registered Capacity and is equivalent to 0.95 power factor lagging, 0.33*Pn;
 Point C represents the maximum Mvar absorption capability of the WPP at 12% Registered
Capacity and is equivalent to the same Mvar as Point A;
 Point D represents the maximum Mvar production capability of the WPP at 12% Registered
Capacity and is equivalent to the same Mvar as Point B;
 Point E represents the maximum Mvar absorption capability of the WPP at the cut-in speed,
of the individual Generation Units and is equivalent to -0.5*Qmin;
 Point F represents the maximum Mvar production capability of the WPP at the cut-in speed
of the individual Generation Units and is equivalent to 0.5*Qmax;
The TSO accepts that the values of Points E and F may vary depending on the number of Generation
Units generating electricity in a low resource scenario;
The Grid Connected Transformer tap changing range must be capable of ensuring nominal voltage at
the lower voltage side of the grid connected transformer, for any Voltage at the Connection Point
within the ranges specified in 8.1.
G&D 450
Figure 14- WPP Capability Curve
For WPP where the Connection Point is remote from the Grid Connected Transformer, any
supplementary Reactive Power compensation required to offset the Reactive Power demand of the HV
line, or cable, between the Connection Point and the WPP shall be identified during the TSO’s
Connection Offer process.
The total charging of the WPP Collector Network during low load operation (below 12%) shall be
examined during the TSO’s Connection Offer process. If during this examination it is identified that this
charging may cause the voltage on the Transmission System to be outside the Transmission System
Voltage ranges, as specified in 8.1, then the Reactive Power requirements will need to be altered.
Automatic Voltage Regulation
WPP shall have a continuously-variable and continuously acting Voltage Regulation System with
similar response characteristics to a conventional Automatic Voltage Regulator and shall perform
generally as described in XXXXXX NTDC standards, or equivalent European Standards.
Under steady state conditions, the Voltage Regulation System shall be capable of implementing the
following Reactive Power control modes which shall be available to the TSO:
a) The WPP shall be capable of receiving a Power Factor control (PF) set-point to maintain the Power
Factor set-point at the Connection Point; The WPP shall be capable of controlling the Reactive Power
at least within the Reactive Power ranges specified in 8.1, with setting steps no greater than 0.01
p.u.. The Power Factor shall be maintained within a tolerance of ± 0.5 %. The tolerance will be
measured with reference to the maximum Reactive Power at the Connection Point.
b) The WPP shall be capable of receiving a Reactive Power control(Q) set-point to maintain the
Reactive Power set-point at the Connection Point; The WPP shall be capable of setting the
Reactive Power set- point at least within the Reactive Power range specified in 8.1, with setting
steps no greater than 5 Mvar or 5 % (whichever is smaller) of maximum Reactive Power, controlling
the Reactive Power at the connection point to an accuracy within ± 5 Mvar or ± 5 % (whichever is
smaller) of the maximum Reactive Power;
c) The WPP shall be capable of receiving a Voltage Regulation (kV) Set-point for the Voltage at the
Connection Point. The Voltage Regulation System shall act to regulate the Voltage at this point
by continuous modulation of the WPP’s Reactive Power output, without violating the rapid Voltage
change limits as set out in CC.10.13.1.
The WPP shall be capable of contributing to voltage control at the Connection Point by provision of
Reactive Power exchange with the Transmission System with a Voltage Regulation Set-point
covering 0.95 to 1.05 p.u. in steps no greater than 0.01 p.u. The Reactive Power output shall be zero
when the grid voltage value at the connection point equals the Voltage Regulation Set-point.
G&D 451
The speed of response of the Voltage Regulation System shall be such that, following a step change in
Voltage at the Connection Point the WPP shall achieve 90 % of its steady-state Reactive Power
response within 1 second. The Reactive Power must settle at the steady-state Reactive Power
response within 5 seconds, with a steady-state Reactive Power tolerance no greater than 5 % of the
maximum Reactive Power.
Subject to agreement with TSO, the Voltage Regulation Set-point may be operated with or without a
deadband selectable in a range from zero to ±5% of reference 1 p.u. Transmission System
voltage in steps no greater than 0.5%.
A change to the Power Factor (PF) control set-point, Reactive Power (Q) control set- point or Voltage
Regulation (kV) Set-Point shall be implemented by the WPP within 20 seconds of receipt of the
appropriate signal from the TSO, within its reactive power capability range as specified in Figure 6.
One Reactive Power Control mode shall be operational at all times with the facility to toggle between
each of the Reactive Power control modes from NCC. Toggling between Reactive Power controllers
shall be smooth in transfer i.e. the WPP shall calculate and implement an appropriate set-point when
transferring to the new control mode. The set-point calculated for the new control mode shall be
consistent with the Mvar output at that time.
WPP1.6.2.3- The Voltage Regulation System Slope Setting shall be capable of being set to any
value between 1 % and 10 % in steps no greater than 0.5%
The speed of response of the Voltage Regulation System shall be such that, following a step
change in Voltage at the Connection Point the Controllable WPP shall achieve 90 % of its steady-
state Reactive Power response within 1 second. The response may require a transition from maximum
Mvar production to maximum Mvar absorption or vice-versa.
G&D 452
G&D 453
?
G&D 454
WPP 1.6.4 WPP’S Grid Connected Transformer
WPP shall provide on-load tap-changing (OLTC) facilities for all Grid Connected Transformers. All WPP
shall liaise with the TSO on the design specification for the performance of the tap-changing facility of the
Grid Connected Transformer.
(a) WPP 1.6.5.2 The WPP’s Grid Connected Transformers may be connected either: in delta on the
lower voltage side and in star (with the star point or neutral brought out) on the HV side; or
In star on both HV and lower voltage sides with a delta tertiary winding provided.
9. LVRT/HVRT Requirements
(i) A WPP must stay connected for transient short duration low voltage dips with slow recovery i.e.
called Low Voltage Ride Through (LVRT), and short duration high voltage swells i.e. called High
Voltage Ride Through (HVRT).
(ii) A WPP must have the LVRT/HVRT capability as indicated in Figure 15. The WTGs are required to
stay connected in the voltage envelope below the HVRT curve and above the LVRT curve.
Figure 15
(iii) LVRT Requirements:

WTG must stay connected for
a) Zero Voltage i.e. Zero Voltage Ride Through (ZVRT) for the initial duration of 150 ms.
b) Recovered/Retained Voltage of 30 % for the next duration of 0.5s
c) Slow voltage recovery up to 0.9 PU in 3 seconds after occurrence of fault.
d) WTG may disconnect if the voltage dips below these limits for longer durations as
specified in the envelope.
(iv) HVRT Requirements:

WTG must stay connected for:
a) Voltage swell up to 1.2 PU for the duration of 3 s.
b) Voltage recovers to 1.1 PU in 3 seconds after occurrence of fault
c) WTGs may disconnect if the voltage swells higher than this limit or for longer duration as
(v) Active current support during LVRT/HVRT situations:

In order tReo actively support voltage during low voltage situations (LVRT-situations), a WPP must inject
additional reactive current into the grid. Likewise, in order to actively reduce the voltage and help keep
the voltage within reasonable limits during high voltage conditions, a WPP must absorb reactive current
G&D 455
(v.1) During Transmission System Voltage Dips, the WPP shall provide Active Power in proportion
to retained Voltage and provide reactive current to the Transmission System, as set out in Fig.8.
(v.2) The provision of reactive current shall continue until the Transmission System Voltage
recovers to within the normal operational range of the Transmission System as specified in
Connection Code (voltage ranges), or for at least 500 ms, whichever is the sooner.
(v.3)The WPP may use all or any available reactive sources, including installed statcoms or
SVCs, when providing reactive support during Transmission System Fault Disturbances
which result in Voltage Dips.
(vi) (The WPP shall provide at least 90 % of its maximum Available Active Power or Active Power Set-
point, whichever is lesser, as quickly as the technology allows and in any event within 500 ms of
the Transmission System Voltage recovering to 90% of nominal Voltage, for Fault Disturbances
cleared within 140 ms. For longer duration Fault Disturbances, but less than 300 msec, the WPP
shall provide at least 90% of its maximum Available Active Power or Active Power Set-point,
whichever is lesser, within 1 second of the Transmission System Voltage recovering to 90% of the
nominal Voltage.
(vii) During and after faults, priority shall always be given to the Active Power response as defined in
V.3 and V.4. The reactive current response of the WPP shall attempt to control the Voltage back
towards the nominal Voltage and should be at least proportional to the Voltage Dip. The reactive
current response shall be supplied within the rating of the WPP, with a Rise Time no greater than
100ms and a Settling Time no greater than 300ms. For the avoidance of doubt, the WPP may
provide this reactive response directly from individual Generation Units, or other additional
dynamic reactive devices on the site, or a combination of both.
The characteristics of reactive current support are indicated in Figure 16.
Figure 16
G&D 456
According to this diagram, a WTG will inject an additional reactive current (IQ in addition to the pre-fault
reactive current) into the grid if the difference between post-disturbance and pre-disturbance voltage
(U) goes below -10%.
In the case that U goes above 10%, a high voltage condition is identified, and a I will be absorbed in
order to stabilize the voltage.
It is further recommended that I is defined as being in proportion to U (the factor of proportionality is

then named “K”).
Besides this, the definition of reactive current support shall include the following:
a) It applies to both, symmetrical and asymmetrical
b) Voltage and Current means, deviation of positive sequence voltage and currents post-
fault from pre-fault values
c) The support is required at the generator terminals and not at POC because POC is almost
impossible to implement
d) The value of is settable, 0<=K<=10 -> reactive current support can be disabled)
e) Dynamic performance requirement for this support is 60ms, well below minimum fault
clearing times
f) The accuracy of reactive current injection within the tolerance band of +/-20% of the
given value
g) The limitation of this current would be absolute current value to rated current
h) The minimum voltage threshold for the applicability of the reactive current support would
be 10%, meaning that below a retained voltage of 10%, reactive current injection is not
required
(viii) The WPP shall manage active power restoration, after the voltage recovery, at a rate of at
least 20% of nominal output power per second, subject to availability of adequate wind
speed at site. However active power recovery must not be faster than a rate of 50% of
nominal power per second. The active power has to be ramped up to pre-fault level (or
maximum available power), or at least to 90% of pre-fault level.
(ix) The WPP must manage reactive power restoration, after voltage recovery, such that post-fault
reactive power must not be below pre-fault reactive power with a minimum tolerance of 10 % and
maximum delay time of 200 ms after fault clearance.
(x) The WPP shall be capable of providing its transient reactive response irrespective of the reactive
control mode in which it was operating at the time of the Transmission System Voltage Dip.
The WPP shall revert to its pre-fault reactive control mode and setpoint within 500ms of the
Transmission System Voltage recovering to its normal operating range as specified in Connection
Code (voltage ranges).
The Controllable WPP shall revert to its pre-fault reactive control mode and setpoint within 500ms of
the Transmission System Voltage recovering to its normal operating range as specified in Connection
Code (frequency ranges).
For avoidance of doubt, the TSO may seek to reduce the magnitude of the dynamic reactive response of
the WPP if it is found to cause over-voltages on the Transmission System. In such a case, the TSO will
make a formal request to the WPP. The WPP and the TSO shall agree on the required changes, and the
WPP shall formally confirm that any requested changes have been implemented within xxx days of
received the TSO’s formal request.
G&D 457
WPP connected to the Transmission System shall be capable of staying connected to the
Transmission System and continuing to operate stably during Voltage Dips. The voltage recovery
profile, after the fault, specifies the required capability for the minimum voltage and Fault Ride-
Through Time at the Connection Point before, during and after the Voltage Dip. That capability shall
be in accordance with the voltage- against-time profile as specified in Figure 17.
Figure 17- Voltage-against-time profile at the connection point for fault conditions
The TSO specifies the pre-fault and post-fault conditions for the fault-ride- through capability on a case-
by-case base, and where requested by the WPP. The specified pre-fault and post-fault conditions for the
fault-ride-through capability will be made publicly available. This includes:
G&D 458
(i) The calculation of the pre-fault minimum short circuit capacity at the Connection Point
(MVA);
(ii) Pre-fault active and reactive power operating point of the Controllable WPP at the
Connection Point and voltage at the Connection Point; and
(iii) Calculation of the post-fault minimum short circuit capacity at the
Connection Point (MVA).
10. Power Quality Requirements

A WPP shall be compliant with the Contents of the planning code and connection code, in regards the
impact of quality of supply and the compliances.
Notwithstanding Planning and Connection Codes, the WPP shall in particular be compliant with the
followings:
(i) Power quality parameters, of power output of a WPP shall be governed, for full Term of Energy
Purchase Agreement, by latest relevant IEC Standards (IEC61400-21 amended time to time)
prevailing at the time of Financial Closing.
(ii) Power Quality parameters, for implementation of clause 10(i) shall be observed at the Point of
Interconnection of the grid connected WPP with the National Grid System/DISCO Systems.
(iii) For continuous monitoring of power quality parameters, a WPP shall install and maintain
necessary monitoring equipment, at its site.
11. Signaling and Control

A WPP shall establish bi-directional communication link with NPCC which would be interfaced with NPCC
SCADA system.
In order to allow the System Operator to monitor actual and forecasted power outputs of WPPs and for
ensuring that active power can be curtailed for congestion management and plants can be tripped in
emergency situations, bi-directional communication links between the NPCC and the plant operator must
be put in place and interfaced with the NPCC SCADA System.
In addition to active power control signals, voltage/reactive power control modes and setpoints have to be
exchanged. For this purpose, clear standards with regard to communication technology, interfaces with
the System Operator’s system etc. have to be specified in the EPA.
A signalling List is attached as Appendix-1
12 Power Generation Capability Forecasting Requirements

Forecasting of Net Delivered Energy from the WPP would be carried out as follows:
a) For and following the Commercial Operations Date, the Seller shall provide the forecasts of Net
Delivered Energy to the Control Centre and to the Purchaser through the Forecasting
Arrangement using state-of-the-art methodology as follows:
(i) Hourly Forecast: Not later than four (4) hours before the start of each hour, a forecast of
Net Delivered Energy for the said hour, provided, the Seller may revise once, and only once,
the forecast for the said hour no later than three (3) hours prior to the commencement of the
hour for which the forecast is revised;
(ii) Four Hourly Forecast: Not later than eight (8) hours before the start of each four (4)
hour period, a forecast of Net Delivered Energy for such four (4) hour period, provided, the
Seller may revise once, and only once, the forecast for any four (4) hour period no later
than six (6) hours prior to the commencement of the four (4) hour period for which the
forecast is revised;
(iii) Day Ahead Forecast: not later than twelve (12) hours prior to the beginning of each
Day, the Seller shall notify the Purchaser (or revise any such information previously given)
G&D 459
of the estimated net output of the WPP in MWh which is likely to be generated for each hour
of such Day;
(iv) Month Ahead Forecast: Not later than one (1) Week before the beginning of each
Month, the Seller shall notify the Purchaser (or revise any such information previously
given) of the Month ahead forecast of estimated net output of the WPP in MWh which it is
likely to generate for each Week of such Month; and
(v) Year Ahead Forecast: not later than thirty (30) Days before the beginning of each
Agreement Year, the Seller shall notify the Purchaser (or revise any such information
previously given) of the year ahead forecast of estimated net output of the WPP in MWh
which it is likely to generate for each Month of such Agreement Year.
b) The Hourly Forecasts (as may be revised in accordance with Section 12.3-A(a)(i)) shall be
binding on the Seller.
c) The Hourly Forecast Error shall be determined using the following formula:
( Hourly Foreca s t Error h )= ( ( ( NDE h+ X ) −( Forecast Energyh ) )

Contract Capacity ×0.98 ) × 100
where;
Hourly Forecast Errorh = Hourly Forecast Error for the hour “h”
NDEh = Net Delivered Energy for the hour “h”
Forecast Energyh = forecast energy for the hour “h”
X = forecast energy not generated due to Non Project Events
in the hour “h”
d) The Monthly Mean Absolute Error shall be determined using the following formula:
∑ ( Hourly Forecast Errorh )

1
( Monthly Mean Absolute Error m )=
n
where;
( Monthly Mean Absolute Error m ) = Monthly Mean Absolute Error for the Month “m”
( Ho u rly Forecast Error h) = Hourly Forecast Error for the hour “h” during the
relevant Month “m”
n = Number of Hourly Forecast Errorh values during
the relevant month “m”
e) The Annual Mean Absolute Error shall be determined using the following formula:
∑ ( Monthly Mean Absolute Error m )

1
( Annual Mean Absolute Error y )=
n
where;
( Annual Mean Absolute Error y ) = Annual Mean Absolute Error for the
relevant Year “y”
during the relevant Year “y”
n = Number of Monthly Mean Absolute Errorm values
G&D 460
f) Should the Annual Mean Absolute Error exceed fifteen percent (15%) in the first year or the
second year, and thereafter ten percent (10%) in any year in the Term, the Seller shall give a
rebate (“Forecasting Error Rebate”) to the Purchaser in the Seller’s first invoice delivered to the
Purchaser in the year next after the year for which the Forecasting Error Rebate is calculated,
according to the following table:
Annual Mean Absolute Error Range Forecasting Error Rebate as percentage of

the Energy Payment invoiced by the Seller
15% to 25% Ten percent (10%)
25% to 35% 10%, plus 1% for each 1% variation in
excess of 25% upto 35%
Above 35% Thirty percent (30%)
However, Forecasting Error Rebate has to be capped at some level which would be agreed in the EPA.
13. Limitation on Total Grid Connected Wind Power Capacity

a) This addendum allows integration of WPPs to National Grid /DISCO Systems up to a maximum
total power limited to a value that does not deteriorate the overall quality of power of Grid
Systems beyond international IEC Standards.
b) Initially, this upper limit is set to be equal to 5% of the total installed grid-connected installed
power (MW) capacity. The process of future projects integration will be carried out as per
planned capacity of respective future years.
c) A modification to above-mentioned allowable limit of total grid-connected wind power capacity
shall be made in Strategic Generation Expansion Plan to be prepared by NTDC. Until then the
limit as defined in Section 13 (ii) shall prevail.
G&D 461
Appendix-I
Signal List 1 – General
1. The WPP operator shall make the following signals available at a System Operator designated
communication gateway equipment located at the wind site:
a) Actual sent-out (MW) at the POC
b) Active Power Ramp rate of the entire WPP
c) Reactive Power Import/Export (+/-Mvar) at the POC
d) Reactive power range upper and lower limits
e) Power Factor
f) Voltage output
g) Echo MW set point
h) Echo Mvar set point
i) Echo Voltage set point
j) Protection relay operations
k) Alarms, indicators and event updates
Signal List 2 – WPGF Availability Estimates

1. WPP operator shall make available the following signals at System Operator designated
communication gateway equipment located at the WPP site:
a) Available MW and forecast MW for the next 24 hours updated hourly on the hour
(alternatively: 15min).
b) Available range of Mvar capability for the next 24 hours updated hourly on the hour
(alternatively: 15min)
Signal List 3 – WPGF MW Curtailment Data

1. The WPP operator shall make the following signals available at a System Operator designated
communication gateway equipment located at the WPP site:
a) MW Curtailment facility status indication (ON/OFF) as a double bit point. This is a controllable
point which is set on or off by the SO. When set “On” the power plant shall then clarify and
initiate the curtailment based on the curtailment set point value below.
b) Curtailment in progress - digital feedback. This single bit point will be set high by the power
plant while the facility is in the process of curtailing its output.
c) MW Curtailment set point value (MW- feedback).
2. In the event of a curtailment, the SO will pulse the curtailment set point value down. The power
plant response to the changed curtailment value will be echoed by changing the corresponding
echo MW value. This will provide feedback that the power plant is responding to the curtailment
request.
Signal List 4 – Frequency and Voltage response system settings

1. The power plant operator shall make the following signals available at a SO designated
communication gateway equipment located at the power plant site:
a) Frequency Response System mode status indication (ON/OFF) as a double bit point.
b) Voltage control system mode status indication (ON/OFF) as a double bit point
G&D 462
(Revision-1)
for Grid Integration of Solar PV
Power Plants (SPVPP)
DNV GL EDIT
G&D 463
Contents
1 General........................................................................................................ 470
2 Definitions................................................................................................... 470
3 Solar PV Generator Technology Requirements............................................... 472
4 Generator Data Requirements....................................................................... 472
5 Black Start and Islanded Operation Requirements.......................................... 472
6 Synchronization / De-Synchronization............................................................ 472
7 Transmission System Frequency ranges:....................................................... 472

7.1 Active Power Management 473
8 Transmission System Voltage requirements................................................... 476

8.2 Transmission System Voltage ranges and Reactive Capability 476
8.3 LVRT/HVRT Requirements 481
9 Power Quality Requirements......................................................................... 485
10 Signaling and Control................................................................................... 485
11 Power Generation Capability Forecasting Requirements................................. 487
12 Limitation on Total Grid Connected Solar PV Power Capacity..........................488
13 Appendix-I................................................................................................... 489
G&D 464
1 GENERAL
(viii) This addendum is applicable only to grid-connected SolarSolar PV power plants with
photovoltaic (PV) technology
(ix) This addendum becomes part of the Grid Code with immediate effect.
(x) All other clauses of Grid Code, which are not covered by this addendum, if otherwise
applicable as such, shall be applicable to Grid connected Solar PV Solar PV Power Plants.
(xi) All relevant clauses of Grid Code, which are covered through this addendum, shall be
(xii) Any provisions of this addendum which have not been previously provided in the Grid
Code, shall now form part of the Grid Code, applicable to Solar PV Solar PV Power Plants
including already Grid-connected Solar PV power plants.
(xiii) NEPRA may approve any subsequent modification to this addendum proposed by NTDC
through the Grid Code Review Panel (GCRP). However, a Grid-connected Solar PV Power
Plant may operate, for its full EPA term, in compliance to the Grid Code prevailing at the
time of its financial closing.
(xiv) Notwithstanding anything contained in this Grid Code Addendum No. 1 (Revision-1) for
Solar PV Power Plants, the Regulator may review, amend, modify or change the
Addendum from time to time.
2 DEFINITIONS
2.1 Black Start




the Seller for the same period
2.6 Grid Connected Power Plant

A power plant which can deliver electrical energy to the National Grid System / DISCO
Systems.

fault conditions

G&D 465

fault conditions.

This is the net energy delivered to the grid at the Point of Common Coupling

The point of connection for off-take of power from a Solar PV Power Plant to the network
of Transmission / Distribution Company. It may also be termed as Point of Connection
(POC).
2.14 Purchaser
2.15 Ramp Rate

Upper limit of a generator in terms of rate of increase of real power (MW/min).
2.16 Regulator
NEPRA Act.

2.18 Seller
Government.

2.21 Term
2.22 Variable Speed WTG

A WTG having arrangements to vary its rotor speed.
2.23 Solar PV Farm Controller

Master controller of entire Solar PV Farm having supervisory control on all SPVGs local
controllers and also controls all outputs/inputs to/from the Grid at Point of Common
Coupling as shown in Figure-1
G&D 466
Solar Farm
Controller
Figure 18
2.24 Solar PV Power Plant (SPVPP)

An installation including equipment and devices attached therewith, with the
capability of converting kinetic energy of Solar PV into electrical energy.
3 SOLAR PV GENERATOR TECHNOLOGY REQUIREMENTS

The criteria of Solar PV Generator (SPVG) selection shall be based on compatibility with the National Grid
System/DISCO Systems, improved operating performance, and optimal efficiency and accounting for the
SPV technology limitations.
4 GENERATOR DATA REQUIREMENTS

A grid-connected Solar PV Power Plant shall be required to provide "Generator Data" applicable to the
type of the Solar PV Generator (SPVG) being installed. In addition, the Solar PV Power Plant shall provide
Standard Planning Data as outlined in the Grid Code to the extent applicable.
5 BLACK START AND ISLANDED OPERATION REQUIREMENTS

A Solar PV Power Plant is exempted from Black Start and Islanded Operation for full term of Energy
Purchase Agreement.
6 SYNCHRONIZATION / DE-SYNCHRONIZATION
A Solar PV Power Plant shall, through appropriate necessary equipment be capable of managing, without
feeling jerk(s) on the National Grid System / DISCO Systems, the following:
(c) Smooth synchronization
(d) Smooth de-Synchronization
7 TRANSMISSION SYSTEM FREQUENCY RANGES:

SPVPP shall have the capability to:
(e) Operate continuously at normal rated output at Transmission System Frequencies in the range
49.5 Hz to 50.5 Hz;
G&D 467
(f) Remain connected to the Transmission System at Transmission System Frequencies within
(g) Remain connected to the Transmission System at Transmission System Frequencies within
System Frequency
(h) Remain connected to the Transmission System for a Rate of Change of Frequency up to and
cause localised ROCOF values in excess of 1 Hz per second for short periods, and in these cases, the
relates to the capabilities of SPVPP only, and does not impose the need for Rate of Change of
protection relays.
No additional Generation Unit shall be started while the Transmission System Frequency is
above 50.2 Hz.
7.1 Active Power Management
A SPVPP Control System shall be installed by the SPVPP to allow for the of Active Power Control
and Frequency Response from the SPVPP. The SPVPP Control System and Frequency Response
System shall provide the functionality as specified in this section SPVPP 1.5.2.

The SPVPP Control System shall be capable of operating each Generation Unit at a reduced level if
the SPVPP’s Active Power output has been restricted by the TSO. In this Active Power Control
Mode, the SPVPP Control System shall be capable of receiving an on-line Active Power Control
Set-point sent by the TSO and shall commence implementation of the set-point within 10 seconds of
receipt of the signal from the TSO. The rate of change of output to achieve the Active Power Control
Set-point should be the Active Power Control Set-Point Ramp Rate setting of the SPVPP Control
System, as advised by the TSO, as per xxxxxx. The TSO acknowledges that if the Active Power
output of the SPVPP is initially less than the Design Minimum Operating Level PMIN, and if the
SPVPP is expected to increase its Active Power output to achieve the present operating point, then it
may not be able to achieve the specified ramp rate at first, due to Generation Units going through a
start-up sequence. In such a case, Generation Units shall start up as quickly as the technology allows,
and in any case, not longer than three minutes from the time the Active Power Control Set-point was

(viii) Grid-connected Solar PV Power Plants shall be exempted from the responsibility of frequency
regulation and control for the “Frequency Sensitive Mode” which is defined by the range between
49.8Hz and 50.2Hz according to OC 4.8.1 (c, ii) of the Grid Code.
(ix) Above 50.2Hz, when frequency enters “Tolerance Frequency Band”, with upper range defined as
50.5Hz according to OC 4.8.1 (c, iii), of the Grid Code, all the Grid-connected Solar PV Power
Plants should contribute to a frequency stabilization by reducing active power as described in
Figure-2 below:
G&D 468
Figure 19
Droop control shall be within 2 to 10%, depending on TSO request, with default value of 4%, see Figure-
3.
(x) If the Frequency rises above FD=51.5 Hz, then the Frequency Response System shall act to
reduce the Active Power output of the SPVPP to its design PMIN before the cut-off value. If the
Frequency rises above FE=52.0 Hz, then the Frequency Response System shall act to reduce the
Active Power output of the SPVPP to zero. Any Generation Unit which has disconnected shall be
brought back on load as fast as technically feasible, provided the Transmission System Frequency
has fallen below FC=50.5 Hz.
(xi) If the Frequency drops below FB=49.5 Hz, the SPVPP must be capable to keep the Active Power
(xii) For steady state frequency regulation, all Gird connected Solar PV Power Plants, shall be capable
of managing the following, disconnection/connection operations of the SVPP or any other inverter
(c) Load adjustments in the range of zero to 100% of available power subject to
availability of Load in Solar PV plant.
(d) A minimum Ramp Rate of 10% of plant available power per minute subject to
availability of Solar PV plant power.
G&D 469
Controllable SPVPP Active Power Output as % of the
available Active Power
Figure 20- SPVPP frequency control requirements
(xiii) Figure 3 shows the Transmission System Frequency and Active Power ranges for F A, FB, FC, FD,
FE, PA, PB, PC, PD and PE.
Table 8- Reference of frequencies in fig.2bi

System Frequency Active Power
Registered Capacity ≥ 5 MW
(Hz) Name
FB 49.5-50 PB
FC 50-50.2 PC 15-100
FE 50.5-52.0 PE 0
If the Transmission System Frequency rises to a level above ‘D’-’E’, as defined by the Power-
Frequency Response Curve in fig.2bis, the TSO accepts that Generation Units may disconnect. Any
Generation Unit which has disconnected shall be brought back on load as fast as technically feasible
(provided the Transmission System Frequency has fallen below 50.2 Hz). The Frequency Response
System shall continuously monitor the Transmission System Frequency in order to continuously
determine the SPVPP appropriate Active Power output by taking account of the SPVPP Available
Active Power or Controlled Active Power. No time delays, such as moving average frequency filters,
other than those necessarily inherent in the design of the Frequency Response System shall be
introduced.
Ramp Rates
The SPVPP Control System shall be capable of controlling the ramp rate of its Active Power output.
There shall be three ramp rate capabilities, designated Resource Following Ramp Rate, Active Power
Control Set-Point Ramp Rate, and Frequency Response Ramp Rate.
The SPVPP Control System shall operate the ramp rates with the following order of priority (high to
low): Frequency Response Ramp Rate; Active Power Control Set-Point Ramp Rate; Resource
Following Ramp Rate.
G&D 470
shall be the maximum possible ramp rate of the SPVPP agreed with the TSO and with the characteristics
as set out in SPVPP 1.5.3.1. The TSO acknowledges that rapidly changing resource availability may
cause temporary deviations from the ramp rate settings of the SPVPP.
8 TRANSMISSION SYSTEM VOLTAGE REQUIREMENTS

SPVPP shall remain continuously connected to the HVAC Transmission System at maximum Available
f. 1100 kV system: 1,045 kV to 11,885 kV

g. 765 kV system: 726 kV to 826 kV
h. 500 kV system: 475 kV to 540 kV
i. 220 kV system: 209 kV to 238 kV

j. 132 kV system: 125 kV to 143 kV
8.2 Transmission System Voltage ranges and Reactive Capability

A Solar PV Farm Controller must be able to operate in either power factor, reactive power or voltage
control as follows:
(iv)Power Factor:
A Solar PV Power Plant shall manage at the Point of interconnection the reactive power control to
maintain the power factor within the range of 0.95 lagging to 0.95 leading, over the full range of plant
operation, as per dispatch instructions and/or voltage adjustments/requirements within the above range
of power factor.
(v) Reactive Power:

A Solar PV Power Plant shall manage at the Point of interconnection the reactive power control within the
setpoints of Qmin and Qmax as Per Unit of full output of Plant as shown in Figure-3. The setpoints of Qmin
and Qmax would be as follows:

G&D 471
Figure 21
(vi)Voltage Control
A Solar PV SPVPP must control voltage at POC along a voltage vs. reactive power characteristic as shown
in Figure 4. The following parameters are set as
conditions.
Figure 22
SPVPP operating in Power Factor control mode, Voltage Control mode or constant Reactive Power
Error: Reference source not found, as measured at the Connection Point over the normal and disturbed
Transmission System Voltage ranges specified in xxxxxx;, additional Reactive Power compensation
may be utilised to compensate for the Reactive Power demand of the connection between the
Connection Point and the SPVPP.
Referring to 6:
 Point A represents the maximum Mvar absorption capability of the Controllable SPVPP at
100% Registered Capacity and is equivalent to 0.95 power factor leading, i.e -0.33*Pn;
 Point B represents the maximum Mvar production capability of the Controllable SPVPP at
100% Registered Capacity and is equivalent to 0.95 power factor lagging, 0.33*Pn;
 Point C represents the maximum Mvar absorption capability of the SPVPP at 12%
Registered Capacity and is equivalent to the same Mvar as Point A;
G&D 472
 Point D represents the maximum Mvar production capability of the SPVPP at 12%
Registered Capacity and is equivalent to the same Mvar as Point B;
 Point E represents the maximum Mvar absorption capability of the SPVPP at the cut-in
speed, of the individual Generation Units and is equivalent to -0.5*Qmin;
 Point F represents the maximum Mvar production capability of the SPVPP at the cut-in
speed of the individual Generation Units and is equivalent to 0.5*Qmax;
Figure 23- SPVPP Capability Curve
For SPVPP where the Connection Point is remote from the Grid Connected Transformer, any
line, or cable, between the Connection Point and the SPVPP shall be identified during the TSO’s
The total charging of the SPVPP Collector Network during low load operation (below 20%) shall be
SPVPP shall have a continuously-variable and continuously acting Voltage Regulation System
with similar response characteristics to a conventional Automatic Voltage Regulator and shall perform
d) The SPVPP shall be capable of receiving a Power Factor control (PF) set-point to maintain the Power
Factor set-point at the Connection Point; The SPVPP shall be capable of controlling the Reactive Power
G&D 473
e) The SPVPP shall be capable of receiving a Reactive Power control(Q) set-p oint to maintain the
Reactive Power set-point at the Connection Point; The SPVPP shall be capable of setting the
f) The SPVPP shall be capable of receiving a Voltage Regulation (kV) Set-point for the Voltage at
the Connection Point. The Voltage Regulation System shall act to regulate the Voltage at this
point by continuous modulation of the SPVPP’s Reactive Power output, without violating the rapid
Voltage change limits as set out in CC.10.13.1.
The SPVPP shall be capable of contributing to voltage control at the Connection Point by provision of
covering 0.95 to 1.05 p.u. in steps no greater than 0.01 p.u.. The Reactive Power output shall be zero
Voltage at the Connection Point the SPVPP shall achieve 90 % of its steady-state Reactive Power
Regulation (kV) Set-Point shall be implemented by the SPVPP within 20 seconds of receipt of the
appropriate signal from the TSO, within its reactive power capability range as specified in SPVPP 1.6.3.
shall be smooth in transfer i.e. the SPVPP shall calculate and implement an appropriate set-point when
G&D 474
SPVPP 1.6.2.3- The Voltage Regulation System Slope Setting shall be capable of being set to any
change in Voltage at the Connection Point the Controllable SPVPP shall achieve 90 % of its steady-
SPVPP 1.6.4 SPVPP’S Grid Connected Transformer

SPVPP shall provide on-load tap-changing (OLTC) facilities for all Grid Connected Transformers. All
SPVPP shall liaise with the TSO on the design specification for the performance of the tap-changing
facility of the Grid Connected Transformer.
(b) SPVPP 1.6.5.2 The SPVPP’s Grid Connected Transformers may be connected either: in delta on
G&D 475
the lower voltage side and in star (with the star point or neutral brought out) on the HV side; or
8.3 LVRT/HVRT Requirements

(xi) A Solar PV Power Plant must stay connected for transient short duration low voltage dips with
slow recovery i.e. called Low Voltage Ride Through (LVRT), and short duration high voltage swells
i.e. called High Voltage Ride Through (HVRT).
(xii) A Solar PV Power Plant must have the LVRT/HVRT capability as indicated in -Figure 15. The SPVGs
are required to stay connected in the voltage envelope below the HVRT curve and above the LVRT
curve.
Figure 24
(xiii) LVRT Requirements:

Solar PV must stay connected for
e) Zero Voltage i.e. Zero Voltage Ride Through (ZVRT) for the initial duration of 150 ms.
f) Recovered/Retained Voltage of 30 % for the next duration of 0.5s
g) Slow voltage recovery up to 0.9 PU in 3 seconds after occurrence of fault.
h) SPVG may disconnect if the voltage dips below these limits for longer durations as
(xiv) HVRT Requirements:

Solar PV must stay connected for:
d) Voltage swell up to 1.2 PU for the duration of 3 s.
e) Voltage recovers to 1.1 PU in 3 seconds after occurrence of fault
f) Solar PVs may disconnect if the voltage swells higher than this limit or for longer duration
as specified in the envelope.
(xv) Active current support during LVRT/HVRT situations:

In order to actively support voltage during low voltage situations (LVRT-situations), a Solar PV Power Plant
must inject additional reactive current into the grid. Likewise, in order to actively reduce the voltage and
help keep the voltage within reasonable limits during high voltage conditions, a Solar PV Power Plant
must absorb reactive current:
G&D 476
(v.1) During Transmission System Voltage Dips, the SPVPP shall provide Active Power in
proportion to retained Voltage and provide reactive current to the Transmission System, as set
out in Fig.8.
Connection Code (Operational ranges of frequencies) , or for at least 500 ms, whichever is the
sooner.
(V.4)The SPVPP may use all or any available reactive sources, including installed statcoms or
(xvi) The SPVPP shall provide at least 90 % of its maximum Available Active Power or Active Power Set-
point, whichever is lesser, as quickly as the technology allows and in any event within 500 ms of the
Transmission System Voltage recovering to 90% of nominal Voltage, for Fault Disturbances cleared
within 140 ms. For longer duration Fault Disturbances, but less than 300 msec, the SPVPP shall
provide at least 90% of its maximum Available Active Power or Active Power Set-point, whichever is
lesser, within 1 second of the Transmission System Voltage recovering to 90% of the nominal Voltage.
(xvii) During and after faults, priority shall always be given to the Active Power response as defined in
V.3 and V.4. The reactive current response of the SPVPP shall attempt to control the Voltage back
current response shall be supplied within the rating of the SPVPP, with a Rise Time no greater than
100ms and a Settling Time no greater than 300ms. For the avoidance of doubt, the SPVPP may
provide this reactive response directly from individual Generation Units, or other additional dynamic
reactive devices on the site, or a combination of both.
G&D 477
Figure 25
According to this diagram, a Solar PV will inject an additional reactive current (DIq in addition to the pre-
fault reactive current) into the grid if the difference between post-disturbance and pre-disturbance
voltage (DU) goes below -10%.
In the case that DU goes above 10%, a high voltage condition is identified, and a DI will be absorbed in
It is further recommended that DI is defined as being in proportion to DU (the factor of proportionality is

i) It applies to both, symmetrical and asymmetrical

j) Voltage and Current means, deviation of positive sequence voltage and currents post-
k) The support is required at the generator terminals and not at POC because POC is almost
l) The value of is settable, 0<=K<=10 -> reactive current support can be disabled)
m) Dynamic performance requirement for this support is 60ms, well below minimum fault
clearing times
n) The accuracy of reactive current injection within the tolerance band of +/-20% of the
given value
o) The limitation of this current would be absolute current value to rated current
p) The minimum voltage threshold for the applicability of the reactive current support would
required
(xviii) The Solar PV Power Plant shall manage active power restoration, after the voltage recovery, at a
rate of at least 20% of nominal output power per second, subject to availability of adequate Solar PV
speed at site. However active power recovery must not be faster than a rate of 50% of nominal power
G&D 478
per second. The active power has to be ramped up to pre-fault level (or maximum available power),
or at least to 90% of pre-fault level.
(xix) The Solar PV Power Plant must manage reactive power restoration, after voltage recovery, such
that post-fault reactive power must not be below pre-fault reactive power with a minimum tolerance
of 10 % and maximum delay time of 200 ms after fault clearance.
(xx)The SPVPP shall be capable of providing its transient reactive response irrespective of the reactive
control mode in which it was operating at the time of the Transmission System Voltage Dip.
The SPVPP shall revert to its pre-fault reactive control mode and setpoint within 500ms of the
Transmission System Voltage recovering to its normal operating range as specified in Connection
Code (voltage ranges),.
The Controllable SPVPP shall revert to its pre-fault reactive control mode and setpoint within 500ms of
the Transmission System Voltage recovering to its normal operating range as specified in Connection
Code (frequency ranges).
the SPVPP if it is found to cause over-voltages on the Transmission System. In such a case, the TSO will
make a formal request to the SPVPP. The SPVPP and the TSO shall agree on the required changes, and
the SPVPP shall formally confirm that any requested changes have been implemented within xxx days of
SPVPP connected to the Transmission System shall be capable of staying connected to the
Figure 26- Voltage-against-time profile at the connection point for fault conditions
The
TSO specifies the pre-fault and post-fault conditions for the fault-ride- through capability on a case-by-
case base, and where requested by the SPVPP. The specified pre-fault and post-fault conditions for the
fault-ride-through capability will be made publicly available. This includes:
(iv) The calculation of the pre-fault minimum short circuit capacity at the Connection Point
(MVA);
(v) Pre-fault active and reactive power operating point of the Controllable SPVPP at the
(vi) Calculation of the post-fault minimum short circuit capacity at the
G&D 479
Connection Point (MVA).
9 POWER QUALITY REQUIREMENTS
A SPVPP shall be compliant with the Contents of the planning code and connection code, in regards the
Notwithstanding Planning and Connection Codes, the SPVPP shall in particular be compliant with the
followings:
(iv) Power quality parameters, of power output of a Solar PV Power Plant shall be governed, for full
Term of Energy Purchase Agreement, by latest relevant IEC Standards (IEC61400-21 amended
time to time) prevailing at the time of Financial Closing.
(v) Power Quality parameters, for implementation of clause 10(i) shall be observed at the Point of
Interconnection of the grid connected Solar PV Power Plant with the National Grid System/DISCO
Systems.
(vi) For continuous monitoring of power quality parameters, a Solar PV Power Plant shall install and
maintain necessary monitoring equipment, at its site.
10 SIGNALING AND CONTROL
A Solar PV Power Plant shall establish bi-directional communication link with NPCC which would be
interfaced with NPCC SCADA system.
In order to allow the System Operator to monitor actual and forecasted power outputs of Solar PV power
plants and for ensuring that active power can be curtailed for congestion management and plants can be
tripped in emergency situations, bi-directional communication links between the NPCC and the plant
operator must be put in place and interfaced with the NPCC SCADA System.
G&D 480
11 POWER GENERATION CAPABILITY FORECASTING
REQUIREMENTS
Forecasting of Net Delivered Energy from the Solar PV Power Plant would be carried out as follows:
g) For and following the Commercial Operations Date, the Seller shall provide the forecasts of Net
Delivered Energy to the Control Centre and to the Purchaser through the Forecasting
Arrangement using state-of-the-art methodology as follows:
(i) Hourly Forecast: Not later than four (4) hours before the start of each hour, a forecast of
Net Delivered Energy for the said hour, provided, the Seller may revise once, and only once,
the forecast for the said hour no later than three (3) hours prior to the commencement of the
hour for which the forecast is revised;
(ii) Four Hourly Forecast: Not later than eight (8) hours before the start of each four (4)
hour period, a forecast of Net Delivered Energy for such four (4) hour period, provided, the
Seller may revise once, and only once, the forecast for any four (4) hour period no later
than six (6) hours prior to the commencement of the four (4) hour period for which the
forecast is revised;
(iii) Day Ahead Forecast: not later than twelve (12) hours prior to the beginning of each
Day, the Seller shall notify the Purchaser (or revise any such information previously given)
of the estimated net output of the Solar PV Power Plant in MWh which is likely to be
generated for each hour of such Day;
(iv) Month Ahead Forecast: Not later than one (1) Week before the beginning of each
Month, the Seller shall notify the Purchaser (or revise any such information previously
given) of the Month ahead forecast of estimated net output of the Solar PV Power Plant in
MWh which it is likely to generate for each Week of such Month; and
(v) Year Ahead Forecast: not later than thirty (30) Days before the beginning of each
Agreement Year, the Seller shall notify the Purchaser (or revise any such information
previously given) of the year ahead forecast of estimated net output of the Solar PV Power
Plant in MWh which it is likely to generate for each Month of such Agreement Year.
h) The Hourly Forecasts (as may be revised in accordance with Section 12.3-A(a)(i)) shall be
binding on the Seller.
i) The Hourly Forecast Error shall be determined using the following formula:
( Hourly Foreca s t Error h )= ( (( NDE h+ X ) −( Forecast Ener gy h ) )

Contract Capacity ×0.98 ) × 100
where;
Hourly Forecast Errorh = Hourly Forecast Error for the hour “h”
NDEh = Net Delivered Energy for the hour “h”
Forecast Energyh = forecast energy for the hour “h”
X = forecast energy not generated due to Non Project Events
in the hour “h”
j) The Monthly Mean Absolute Error shall be determined using the following formula:
G&D 481
n
∑ ( Hourly Forecast Error h )

1
( Monthly Mean Absolute Error m )=
n
where;
( Ho u rly Forecast Errorh ) = Hourly Forecast Error for the hour “h” during the
relevant Month “m”
n = Number of Hourly Forecast Errorh values during
the relevant month “m”
k) The Annual Mean Absolute Error shall be determined using the following formula:
∑ ( Monthly Mean Absolute Error m )

1
( Annual Mean Absolute Error y )=
n
where;
( Annual Mean Absolute Error y ) = Annual Mean Absolute Error for the
relevant Year “y”
n = Number of Monthly Mean Absolute Errorm values
l) Should the Annual Mean Absolute Error exceed fifteen percent (15%) in the first year or the
second year, and thereafter ten percent (10%) in any year in the Term, the Seller shall give a
rebate (“Forecasting Error Rebate”) to the Purchaser in the Seller’s first invoice delivered to the
Purchaser in the year next after the year for which the Forecasting Error Rebate is calculated,
according to the following table:
Annual Mean Absolute Error Range Forecasting Error Rebate as percentage of

the Energy Payment invoiced by the Seller
15% to 25% Ten percent (10%)
25% to 35% 10%, plus 1% for each 1% variation in
excess of 25% upto 35%
Above 35% Thirty percent (30%)
However, Forecasting Error Rebate has to be capped at some level which would be agreed in the EPA.
12 LIMITATION ON TOTAL GRID CONNECTED SOLAR PV POWER

CAPACITY
d) This addendum allows integration of Solar PV Power Plants to National Grid /DISCO Systems up
to a maximum total power limited to a value that does not deteriorate the overall quality of
power of Grid Systems beyond international IEC Standards.
e) Initially, this upper limit is set to be equal to 5% of the total installed grid-connected installed
G&D 482
f) A modification to above-mentioned allowable limit of total grid-connected Solar PV power
capacity shall be made in Strategic Generation Expansion Plan to be prepared by NTDC. Until
then the limit as defined in Section 13 (ii) shall prevail.
G&D 483
13 APPENDIX-I
2. The Solar PV power plant operator shall make the following signals available at a System Operator
designated communication gateway equipment located at the Solar PV site:
l) Actual sent-out (MW) at the POC
m) Active Power Ramp rate of the entire Solar PV power plant
n) Reactive Power Import/Export (+/-Mvar) at the POC
o) Reactive power range upper and lower limits
p) Power Factor
q) Voltage output
r) Echo MW set point
s) Echo Mvar set point
t) Echo Voltage set point
u) Protection relay operations
v) Alarms, indicators and event updates

2. Solar PV power plant operator shall make available the following signals at System Operator
designated communication gateway equipment located at the Solar PV power plant site:
c) Available MW and forecast MW for the next 24 hours updated hourly on the hour
d) Available range of Mvar capability for the next 24 hours updated hourly on the hour

3. The Solar PV power plant operator shall make the following signals available at a System Operator
designated communication gateway equipment located at the Solar PV power plant site:
d) MW Curtailment facility status indication (ON/OFF) as a double bit point. This is a controllable
e) Curtailment in progress - digital feedback. This single bit point will be set high by the power
f) MW Curtailment set point value (MW- feedback).
request.

c) Frequency Response System mode status indication (ON/OFF) as a double bit point.
d) Voltage control system mode status indication (ON/OFF) as a double bit point
G&D 484
(Revision-0)
for Grid Integration of Battery
Storage Energy Units (BESU)
DNV GL EDIT
G&D 485
Contents
1 General........................................................................................................ 492
2 Definitions................................................................................................... 492
3 Battery Energy System Technology Requirements.......................................... 494
4 Battery Energy UNIT Data Requirements....................................................... 494
5 Black Start and Islanded Operation Requirements.......................................... 495
6 Synchronization / De-Synchronization............................................................ 495
7 Transmission System Frequency ranges:....................................................... 495

7.1 Active Power Management 495
7.2 Storage Capacity control 495
8 Transmission System Voltage requirements................................................... 500

8.2 Transmission System Voltage ranges and Reactive Capability 501
8.3 LVRT/HVRT Requirements 509
9 Power Quality Requirements......................................................................... 513
10 Signaling and Control................................................................................... 513
11 Limitation on Total Grid Connected BESU Capacity......................................... 514
12 Appendix-I................................................................................................... 515
G&D 486
1 GENERAL
(xv) This addendum is applicable only to grid-connected BESU plants with photovoltaic (PV)
technology.
(xvi) This addendum becomes part of the Grid Code with immediate effect.
(xvii) All other clauses of Grid Code, which are not covered by this addendum, if otherwise
applicable as such, shall be applicable to Grid connected BESU Plants.
(xviii) All relevant clauses of Grid Code, which are covered through this addendum, shall be
(xix) Any provisions of this addendum which have not been previously provided in the Grid
Code, shall now form part of the Grid Code, applicable to BESU Plants including already
Grid-connected BESU plants.
(xx) NEPRA may approve any subsequent modification to this addendum proposed by NTDC
through the Grid Code Review Panel (GCRP). However, a Grid-connected BESU Plant may
operate, for its full EPA term, in compliance to the Grid Code prevailing at the time of its
financial closing.
(xxi) Notwithstanding anything contained in this Grid Code Addendum No. 1 (Revision-1) for
BESU Plants, the Regulator may review, amend, modify or change the Addendum from
time to time.
2 DEFINITIONS
2.1. Battery Energy Storage Units (BESU): Grid component with capability of storing
electric energy and able to inject power into or absorb power from the Grid which it is
connected to. A BESU can alternatively behave as a Generating Unit or a Controllable
Load.
2.2 Battery Storage Capacity

The amount of Energy, in MWh, the Battery is able to store.
2.2 Black Start

2.3 Controllable Load

A Load which active power can be controlled in normal operation by sending a signal from the
TSO. The signal shall be in addition to the load control in emergency situation, and may
be used by TSO in normal or emergency prior to the other load shedding actions.



the Seller for the same period.
G&D 487
2.6 Grid Connected Battery Energy Storage Unit
A BESU which can deliver/absorb electrical energy to/from the National Grid System /
DISCO Systems.

fault conditions.



fault conditions.

This is the net energy delivered to the grid at the Point of Common Coupling.

The point of connection for off-take of power from a BESU Plant to the network of
Transmission / Distribution Company. It may also be termed as Point of Connection (POC).
2.14 Purchaser
As defined in Energy Purchase Agreement (EPA).
2.15 Ramp Rate

Upper limit of a generator or a controllable Load in terms of rate of increase/decrease of
real power (MW/min).
2.16 Regulator
NEPRA Act.

2.18 Seller
As defined in Energy Purchase Agreement (EPA).
Government.
G&D 488
2.21 Term
2.23 Battery Storage Controller

Master controller of entire Battery Energy Storage Unit having supervisory control on all
BESUs’ local controllers and also controls all outputs/inputs to/from the Grid at Point of
Common Coupling as shown in Figure-1
Battery
Storage
Controller
Figure 27
3 BATTERY ENERGY SYSTEM TECHNOLOGY REQUIREMENTS

The criteria of Battery Energy System Unit (BESU) selection shall be based on compatibility with the
National Grid System/DISCO Systems, improved operating performance, and optimal efficiency and
accounting for the SPV technology limitations.
4 BATTERY ENERGY UNIT DATA REQUIREMENTS

A grid-connected BESU shall be required to provide "Generator/Load Data" applicable to the type of the
BESU being installed, including the amount of energy the BESU is able to store.
In addition, the BESU shall provide Standard Planning Data as outlined in the Grid Code to the extent
applicable.
5 BLACK START AND ISLANDED OPERATION REQUIREMENTS

A BESU may be asked by the TSO to be designed in order to provide BESUBlack Start and Islanded
Operation for full term of Energy Purchase Agreement.
6 SYNCHRONIZATION / DE-SYNCHRONIZATION
A BESU shall, through appropriate necessary equipment be capable of managing, without feeling jerk(s)
on the National Grid System / DISCO Systems, the following:
G&D 489
(e) Smooth synchronization
(f) Smooth de-Synchronization
7 TRANSMISSION SYSTEM FREQUENCY RANGES:

BESU shall have the capability to:
(i) Operate continuously at normal rated output at Transmission System Frequencies in the range
49.5 Hz to 50.5 Hz;
(j) Remain connected to the Transmission System at Transmission System Frequencies within
(k) Remain connected to the Transmission System at Transmission System Frequencies within
System Frequency
(l) Remain connected to the Transmission System for a Rate of Change of Frequency up to and
cause localised ROCOF values in excess of 1 Hz per second for short periods, and in these cases, the
relates to the capabilities of BESU only, and does not impose the need for Rate of Change of
protection relays.
No additional Generation Unit mode of operation of BESU shall be started while the
Transmission System Frequency is above 50.2 Hz.
7.1 Active Power Management
A BESU Control System shall be installed by the BESU to allow for the of Active Power Control and
Frequency Response from the BESU. The BESU Control System and Frequency Response
System shall provide the functionality as specified in this section7.2.
7.2 Storage Capacity control

BESU has finite capability available for Energy to be delivered to or to be absorbed from the Grid and
dynamically impact on the Power system. To avoid sudden stop of power delivered/absorbed, generating
transients into the grid, BESU shall be capable of controlling the of the rampe rate, from the initial value to
0 according to the suggested Error: Reference source not found.
C B
Pmax tc tb t
[MWexp]
A
Pmax
C B [MWimp]
tc tb t
a) Export Mode of Operation b) Import Mode of Operation
G&D 490
c) discharging Rate and limitation d) Charging Rate and limitation
Figure 28- Charging and Discharging Mode for BESU
In case of discharging to the Grid, it is proposed to maintain a constant rate less equal the maximum BESU
rate until point A, after tc
At this level, i.e. the ramp rate starts linearly decreasing in order to achieve 0 when the BESU minimum
capacity is achieved, i.e. at point B per tb in fig.c
When the BESU is in Charging Mode, fig.b absorbing from the Grid, the ramp rate is kept constant until
point A, per tc
At this level, the ramp rate starts linearly decreasing in order to achieve 0 when the BESU maximum
capacity is achieved, i.e. at point B per tb in fig.d
The Capacity Thresholds indicated in fig.c and d are provided by the TSO.
The BESU control system shall be capable to automatically adjust the ramp rate linear decreasing for any
threshold communicated by the TSO.

The BESU Control System shall be capable of operating each BESU at a reduced level of power
injection if the BESU’s Active Power output has been restricted by the TSO.
In the same way, the BESU Control System shall be capable of operating each BESU at a reduced level
of power absorption if the BESU’s Active Power intput has been restricted by the TSO.
In this Active Power Control Modes, the BESU Control System shall be capable of receiving an on-
line Active Power Control Set-point sent by the TSO and shall commence implementation of the set-
point within 10 seconds of receipt of the signal from the TSO. The rate of change of output to achieve
the Active Power Control Set-point should be the Active Power Control Set-Point Ramp Rate
setting of the BESU Control System, as advised by the TSO, as per xxxxxx. The TSO acknowledges
that if the Active Power output of the BESU is initially less than the Design Minimum Operating
Level PMIN, and if the BESU is expected to increase its Active Power output to achieve the present
operating point, then it may not be able to achieve the specified ramp rate at first, due to Generation
Units going through a start-up sequence. In such a case, BESU in Generation mode shall start up as
quickly as the technology allows, and in any case, not longer than three minutes from the time the
Active Power Control Set-point was

BESU must be capable of;
G&D 491
- Contributing to the control of system frequency by modulation of active power.
- Responding to both high and low frequency conditions from a baseline active power output
anywhere within their operating range, including at zero mw output. Frequency response is
not expected to extend beyond the limits of operating range.
- Accommodating five separate programmable frequency response modes. Each mode shall be
represented by a response curve described in terms of the parameters listed below (see
‘response characteristics and performance’).
The TSO will have the functionality to;
- Toggle between the Frequency Response Modes via SCADA signals

- Turn Frequency Response on and off via a SCADA signal
When Frequency Response is ‘ON’, the BESU shall respond to system frequency in line with the
specified frequency response settings for the active frequency mode. When Frequency Response is
turned ‘OFF’, the Battery ESPS shall not respond to any changes in system frequency.
The selected Frequency Response Mode (and feedback) shall not be affected by the Frequency
Response status (ON / OFF) i.e. the Frequency Response Mode does not change, nor should the
feedback signal go suspect.
The following shall be taken into account for BESU:

(xiv) Grid-connected BESUs shall be exempted from the responsibility of frequency regulation and
control for the “Frequency Sensitive Mode” which is defined by the range between 49.8Hz and
50.2Hz according to OC 4.8.1 (c, ii) of the Grid Code.
(xv) Above 50.2Hz, when frequency enters “Tolerance Frequency Band”, with upper range defined as
50.5Hz according to OC 4.8.1 (c, iii), of the Grid Code, all the Grid-connected BESUthe BESUs
should contribute to a frequency stabilization by reducing active power as described in Figure 3
below:
49.8 Hz 50 Hz 50.2Hz 52.5 Hz

47.5 Hz
Figure 29 - Frequency Control for BESU
Droop control shall be within 2 to 10%, depending on TSO request, with default value of 4%, see Figure-
3.
G&D 492
(xvi) If the Frequency rises above FD=51.5 Hz, then the Frequency Response System shall act to
reduce the Active Power output of the BESUs to its design PMIN. If the Frequency rises above
FE=52.0 Hz, then the Frequency Response System shall act to reduce the Active Power output of
the BESU to zero. Any Generation Unit which has disconnected shall be brought back on load as
fast as technically feasible, provided the Transmission System Frequency has fallen below
FC=50.5 Hz.
(xvii) If the Frequency drops below FB=49.5 Hz, the BESU must be capable to keep the Active Power
(xviii) For steady state frequency regulation, all Gird connected BESU Plants, shall be capable of
managing the following, disconnection/connection operations of the SVPP or any other inverter
(e) Load adjustments in the range of zero to 100% of available power subject to
availability of Load in BESU.
(f) A minimum Ramp Rate of 10% of plant available power per minute subject to
availability of BESU plant power.
100
A
A
the BESU
50
100 B C
ofAvailable
C
0
80
B
% of
Nominal Power
Governor Droop
asasaa%
(default 4%)
Power
60
-50
Output
Power
Active
Please note: D
Power
Please Note:
40
-100 -•Droop
Droop is calculated
control w ith
is calculated
Active
respect
with to Registered
respect Capacity
to Register
BESU Active
Capacity and Real- Time Battery

•The frequency
Status deviation
according to 7.2 is
calculated from nominal
20
BESU
-frequency and not

The frequency the
deviation is
deadband edge
calculated from nominal D
frequency DMOL
0 E
FA FB FC FD
Frequency (Hz)
Figure 30 - BESU frequency control requirements
(xix) Figure 30 shows the Transmission System Frequency and Active Power ranges for F A, FB, FC, FD,
FE, PA, PB, PC, PD and PE.
Table 9- Reference of frequencies
G&D 493
System Frequency Active Power
Registered Capacity ≥ 5 MW
(Hz) Name
FB 49.5-50 PB
FC 50-50.2 PC 15-100
FE 50.5-52.0 PE 0
No. Characteristic Description
1 F System frequency at any given time

Change in active power output, due to change in
2 ΔP
system frequency
Under frequency trigger Frequency at which the unit begins to provide under
3*
frequency (FB) frequency response
Frequency at which the unit would achieve its
4 FA maximum under frequency response setting (FA
Under frequency trajectory setting)
Over frequency trigger frequency Frequency at which the unit begins to provide over
5*
(FC) frequency response
Frequency at which the unit would achieve its
6 FD maximum over frequency response setting (F3 + Over
frequency trajectory setting)
The magnitude of the change in Frequency over which
7* Under frequency trajectory the unit would deliver its Maximum Under frequency
Response Setting (if it was not limited by capacity or
availability)
The magnitude of the change in Frequency over which
8* Over frequency trajectory the unit would deliver its Maximum Over frequency
Response Setting (if it was not limited by capacity or
availability)
Maximum Under frequency Maximum increase in active power which the unit will
9*
Response provide in response to under frequency
Maximum Over frequency Maximum reduction in active power which the unit will
10*
Response provide in response to over frequency
If the Transmission System Frequency rises to a level above ‘D’-, as defined by the Power-Frequency
Response Curve in fig.2bis, the TSO accepts that Generation Units may disconnect. Any Generation
Unit which has disconnected shall be brought back on load as fast as technically feasible (provided the
Transmission System Frequency has fallen below 50.2 Hz). The Frequency Response System shall
continuously monitor the Transmission System Frequency in order to continuously determine the
BESU appropriate Active Power output by taking account of the BESU Available Active Power or
Controlled Active Power. No time delays, such as moving average frequency filters, other than those
necessarily inherent in the design of the Frequency Response System shall be introduced.
Ramp Rates
The BESU Control System shall be capable of controlling the ramp rate of its Active Power output.
There shall be four ramp rate capabilities, designated Resource Following Ramp Rate, Active Power
Control Set-Point Ramp Rate, Frequency Response Ramp Rate and Storage Capacity limit
ramp rate.
The BESU Control System shall operate the ramp rates with the following order of priority (high to low):
Storage Capacity limit ramp rate, Frequency Response Ramp Rate; Active Power Control Set-Point
Ramp Rate; Resource Following Ramp Rate.
G&D 494
shall be the maximum possible ramp rate of the BESU agreed with the TSO and with the characteristics
as set out in 7.2 based on the Storage Capacity limit ramp rate The TSO acknowledges that rapidly
changing resource availability may cause temporary deviations from the ramp rate settings of the BESU.
8 TRANSMISSION SYSTEM VOLTAGE REQUIREMENTS

BESU shall remain continuously connected to the HVAC Transmission System at maximum Available
k. 1100 kV system: 1,045 kV to 11,885 kV

l. 765 kV system: 726 kV to 826 kV
m. 500 kV system: 475 kV to 540 kV
n. 220 kV system: 209 kV to 238 kV

o. 132 kV system: 125 kV to 143 kV
8.2 Transmission System Voltage ranges and Reactive Capability

A BESU must be able to operate in either power factor, reactive power or voltage control as
follows:
(vii) Power Factor:

A BESU Plant shall manage at the Point of interconnection the reactive power control to maintain
the power factor within the range of 0.95 lagging to 0.95 leading, over the full range of plant
operation, as per dispatch instructions and/or voltage adjustments/requirements within the above
range of power factor.
(viii) Reactive Power:

A BESU Plant shall manage at the Point of interconnection the reactive power control within the
setpoints of Qmin and Qmax as Per Unit of full output of Plant as shown in Figure 5. The setpoints
of Qmin and Qmax would be as follows:

G&D 495
Figure 31- Reactive Power Controls
(ix)Voltage Control
A BESU must control voltage at POC along a voltage vs. reactive power characteristic as shown in
Figure 6. The following parameters are set as
conditions.
G&D 496
Figure 32 - Voltage Control
BESU operating in Power Factor control mode, Voltage Control mode or constant Reactive Power
Figure 7 as measured at the Connection Point over the normal and disturbed Transmission System
Voltage ranges specified in xxxxxx;,
additional Reactive Power compensation may be utilised to compensate for the Reactive Power
demand of the connection between the Connection Point and the BESU.
Referring to Figure 7:
 Point A represents the maximum Mvar absorption capability of the Controllable BESU at
100% Registered Capacity in discharging mode and is equivalent to 0.95 power factor
leading, i.e. -0.33*Pn;
 Point B represents the maximum Mvar production capability of the Controllable BESU at
100% Registered Capacity in discharging mode and is equivalent to 0.95 power factor
lagging, 0.33*Pn;
 Point C represents the maximum Mvar absorption capability of the BESU at 100%
Registered Capacity in charging mode and is equivalent to the same Mvar as Point B;
 Point D represents the maximum Mvar production capability of the BESU at 100%
Registered Capacity in charging mode and is equivalent to the same Mvar as Point A;
G&D 497
A B
(0.95;-0.33) (0.95;0.33)
D C
(-0.95;-0.33) (-0.95;0.33)
Figure 33- BESU Capability Curve
For BESU where the Connection Point is remote from the Grid Connected Transformer, any
line, or cable, between the Connection Point and the BESU shall be identified during the TSO’s
The total charging of the BESU Collector Network during low load operation (below 20%) shall be
BESU shall have a continuously-variable and continuously acting Voltage Regulation System with
similar response characteristics to a conventional Automatic Voltage Regulator and shall perform
g) The BESU shall be capable of receiving a Power Factor control (PF) set-point to maintain the Power
Factor set-point at the Connection Point; The BESU shall be capable of controlling the Reactive Power
h) The BESU shall be capable of receiving a Reactive Power control(Q) set-p oint to maintain the
Reactive Power set-point at the Connection Point; The BESU shall be capable of setting the
G&D 498
i) The BESU shall be capable of receiving a Voltage Regulation (kV) Set-point for the Voltage at
the Connection Point. The Voltage Regulation System shall act to regulate the Voltage at this
point by continuous modulation of the BESU’s Reactive Power output, without violating the rapid
Voltage change limits as set out in CC.10.13.1.
The BESU shall be capable of contributing to voltage control at the Connection Point by provision of
covering 0.95 to 1.05 p.u. in steps no greater than 0.01 p.u.. The Reactive Power output shall be zero
Voltage at the Connection Point the BESU shall achieve 90 % of its steady-state Reactive Power
Regulation (kV) Set-Point shall be implemented by the BESU within 20 seconds of receipt of the
appropriate signal from the TSO, within its reactive power capability range as specified in BESU 1.6.3.
shall be smooth in transfer i.e. the BESU shall calculate and implement an appropriate set-point when
BESU 1.6.2.3- The Voltage Regulation System Slope Setting shall be capable of being set to any
change in Voltage at the Connection Point the Controllable BESU shall achieve 90 % of its steady-
G&D 499
G&D 500
501
502
BESU1.6.4 BESU’S Grid Connected Transformer
BESU shall provide on-load tap-changing (OLTC) facilities for all Grid Connected Transformers. All
BESU shall liaise with the TSO on the design specification for the performance of the tap-changing
facility of the Grid Connected Transformer.
(c) BESU1.6.5.2 The BESU’s Grid Connected Transformers may be connected either:in delta on
the lower voltage side and in star (with the star point or neutral brought out) on the HV side; or
8.3 LVRT/HVRT Requirements

(xxi) A BESU Plant must stay connected for transient short duration low voltage dips with slow recovery
i.e. called Low Voltage Ride Through (LVRT), and short duration high voltage swells i.e. called
High Voltage Ride Through (HVRT).
(xxii) A BESU Plant must have the LVRT/HVRT capability as indicated in Figure 8Figure 15. The BESUs
are required to stay connected in the voltage envelope below the HVRT curve and above the LVRT
curve.
Figure 34
(xxiii) LVRT Requirements:

BESU must stay connected for
i) Zero Voltage i.e. Zero Voltage Ride Through (ZVRT) for the initial duration of 150 ms.
j) Recovered/Retained Voltage of 30 % for the next duration of 0.5s
k) Slow voltage recovery up to 0.9 PU in 3 seconds after occurrence of fault.
l) BESU may disconnect if the voltage dips below these limits for longer durations as
(xxiv) HVRT Requirements:

BESU must stay connected for:
g) Voltage swell up to 1.2 PU for the duration of 3 s.
h) Voltage recovers to 1.1 PU in 3 seconds after occurrence of fault
i) BESU may disconnect if the voltage swells higher than this limit or for longer duration as
503
(xxv) Active current support during LVRT/HVRT situations:
In order to actively support voltage during low voltage situations (LVRT-situations), a BESU Plant
must inject additional reactive current into the grid. Likewise, in order to actively reduce the
voltage and help keep the voltage within reasonable limits during high voltage conditions, a BESU
Plant must absorb reactive current
(v.1) During Transmission System Voltage Dips, the BESU shall provide Active Power in proportion
to retained Voltage and provide reactive current to the Transmission System, as set out in Figure
9.
Connection Code (Operational ranges of frequencies) , or for at least 500 ms, whichever is the
sooner.
(v.4)The BESU may use all or any available reactive sources, including installed statcoms or
(xxvi) The BESU shall provide at least 90 % of its maximum Available Active Power or Active Power Set-
point, whichever is lesser, as quickly as the technology allows and in any event within 500 ms of
the Transmission System Voltage recovering to 90% of nominal Voltage, for Fault Disturbances
cleared within 140 ms. For longer duration Fault Disturbances, but less than 300 msec, the BESU
shall provide at least 90% of its maximum Available Active Power or Active Power Set-point,
whichever is lesser, within 1 second of the Transmission System Voltage recovering to 90% of the
nominal Voltage.
(xxvii) During and after faults, priority shall always be given to the Active Power response as defined in
V.3 and V.4. The reactive current response of the BESU shall attempt to control the Voltage back
current response shall be supplied within the rating of the BESU, with a Rise Time no greater than
100ms and a Settling Time no greater than 300ms. For the avoidance of doubt, the BESU may
provide this reactive response directly from individual Generation Units, or other additional
dynamic reactive devices on the site, or a combination of both.
504
Figure 35
According to this diagram, a BESU will inject an additional reactive current (DIq in addition to the pre-fault
reactive current) into the grid if the difference between post-disturbance and pre-disturbance voltage
(DU) goes below -10%.
In the case that DU goes above 10%, a high voltage condition is identified, and a DI will be absorbed in
It is further recommended that DI is defined as being in proportion to DU (the factor of proportionality is

q) It applies to both, symmetrical and asymmetrical

r) Voltage and Current means, deviation of positive sequence voltage and currents post-
s) The support is required at the generator terminals and not at POC because POC is almost
t) The value of is settable, 0<=K<=10 -> reactive current support can be disabled)
u) Dynamic performance requirement for this support is 60ms, well below minimum fault
clearing times
v) The accuracy of reactive current injection within the tolerance band of +/-20% of the
given value
w) The limitation of this current would be absolute current value to rated current
x) The minimum voltage threshold for the applicability of the reactive current support would
required
(xxviii) The BESU Plant shall manage active power restoration, after the voltage recovery, at a
rate of at least 20% of nominal output power per second, subject to availability of
adequate BESU speed at site. However active power recovery must not be faster than a
505
rate of 50% of nominal power per second. The active power has to be ramped up to pre-
fault level (or maximum available power), or at least to 90% of pre-fault level.
(xxix) The BESU Plant must manage reactive power restoration, after voltage recovery, such
that post-fault reactive power must not be below pre-fault reactive power with a minimum
tolerance of 10 % and maximum delay time of 200 ms after fault clearance.
(xxx) The BESU shall be capable of providing its transient reactive response irrespective of the
reactive control mode in which it was operating at the time of the Transmission System
Voltage Dip.
The BESU shall revert to its pre-fault reactive control mode and setpoint within 500ms of
the Transmission System Voltage recovering to its normal operating range as
specified in Connection Code (voltage ranges),.
The Controllable BESU shall revert to its pre-fault reactive control mode and setpoint
within 500ms of the Transmission System Voltage recovering to its normal operating
range as specified in Connection Code (frequency ranges),
the BESU if it is found to cause over-voltages on the Transmission System. In such a case, the TSO will
make a formal request to the BESU. The BESU and the TSO shall agree on the required changes, and the
BESU shall formally confirm that any requested changes have been implemented within xxx days of
BESU connected to the Transmission System shall be capable of staying connected to the
Figure 36 Voltage-against-time profile at the connection point for fault conditions

The
TSO
specifies the pre-fault and post-fault conditions for the fault-ride- through capability on a case-by-case
base, and where requested by the BESU. The specified pre-fault and post-fault conditions for the fault-
ride-through capability will be made publicly available. This includes:
(vii) The calculation of the pre-fault minimum short circuit capacity at the Connection Point
(MVA);
(viii) Pre-fault active and reactive power operating point of the Controllable BESU at the
(ix) Calculation of the post-fault minimum short circuit capacity at the Connection Point
(MVA).
506
9 POWER QUALITY REQUIREMENTS
A BESU shall be compliant with the Contents of the planning code and connection code, in regards the
Notwithstanding Planning and Connection Codes, the BESU shall in particular be compliant with the
followings:
(vii) Power quality parameters, of power output of a BESU Plant shall be governed, for full Term of
Energy Purchase Agreement, by latest relevant IEC Standards (IEC61400-21 amended time to
time) prevailing at the time of Financial Closing.
(viii) Power Quality parameters, for implementation of clause 10(i) shall be observed at the Point of
Interconnection of the grid connected BESU Plant with the National Grid System/DISCO Systems.
(ix) For continuous monitoring of power quality parameters, a BESU Plant shall install and maintain
necessary monitoring equipment, at its site.
10 SIGNALING AND CONTROL
A BESU Plant shall establish bi-directional communication link with NPCC which would be interfaced with
NPCC SCADA system.
In order to allow the System Operator to monitor actual and forecasted power outputs of BESU plants and
for ensuring that active power can be curtailed for congestion management and plants can be tripped in
emergency situations, bi-directional communication links between the NPCC and the plant operator must
be put in place and interfaced with the NPCC SCADA System.
507
11 LIMITATION ON TOTAL GRID CONNECTED BESU CAPACITY
g) This addendum allows integration of BESU Plants to National Grid /DISCO Systems up to a
maximum total power limited to a value that does not deteriorate the overall quality of power of
Grid Systems beyond international IEC Standards.
h) Initially, this upper limit is set to be equal to 5% of the total installed grid-connected installed
i) A modification to above-mentioned allowable limit of total grid-connected BESU capacity shall be
made in Strategic Generation Expansion Plan to be prepared by NTDC. Until then the limit as
defined in Section 13 (ii) shall prevail.
508
12 APPENDIX-I
3. The BESU plant operator shall make the following signals available at a System Operator
designated communication gateway equipment located at the BESU site:
w) Actual sent-out (MW) at the POC
x) Active Power Ramp rate of the entire BESU plant
y) Reactive Power Import/Export (+/-Mvar) at the POC
z) Reactive power range upper and lower limits
aa) Power Factor
bb) Voltage output
cc) Echo MW set point
dd) Echo Mvar set point
ee) Echo Voltage set point
ff) Protection relay operations
gg) Alarms, indicators and event updates

3. BESU plant operator shall make available the following signals at System Operator designated
communication gateway equipment located at the BESU plant site:
e) Available MW and forecast MW for the next 24 hours updated hourly on the hour
f) Available range of Mvar capability for the next 24 hours updated hourly on the hour

5.The BESU plant operator shall make the following signals available at a System Operator
designated communication gateway equipment located at the BESU plant site:
g) MW Curtailment facility status indication (ON/OFF) as a double bit point. This is a controllable
h) Curtailment in progress - digital feedback. This single bit point will be set high by the power
i) MW Curtailment set point value (MW- feedback).
request.

e) Frequency Response System mode status indication (ON/OFF) as a double bit point.
f) Voltage control system mode status indication (ON/OFF) as a double bit point.
509
510

Full Grid Code - NTDC Draft

Uploaded by

Copyright:

Available Formats

Full Grid Code - NTDC Draft

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Full Grid Code - NTDC Draft

Uploaded by

Copyright:

Available Formats

The Pakistan Grid Code

a) To achieve the Performance Standards (Transmission) to be prescribed under the Act;

b) To facilitate the development, operation, and maintenance of an efficient, co-ordinated, safe,

c) To facilitate competition in the provision of electric power; and

This Grid Code includes the following sub-codes:

d. Data Registration Code

f. Protection and Metering Code

g. Scheduling and Dispatch Code

h. Code Glossary & Definitions

Technical Grid Code Transmission Connected Customers

Dist. Code Small Scale Power producers

Figure 2. Stakeholders and the Codes

CM 1 INTRODUCTION & SCOPE.................................................................................. 2

CM 3 THE GRID CODE REVIEW PANEL......................................................................... 3

CM 4 COMMUNICATIONS BETWEEN NTDC AND USERS.............Error! Bookmark not defined.

CM 5 MISCELLANEOUS.......................................................... Error! Bookmark not defined.

CM 6 OWNERSHIP OF FACILITIES, PLANT AND/OR APPARATUS Error! Bookmark not defined.

CM 7 SYSTEM CONTROL........................................................ Error! Bookmark not defined.

CM 8 FORCE MAJEURE.......................................................... Error! Bookmark not defined.

CM 11 INDEMNITY TO THE NTDC............................................. Error! Bookmark not defined.

CM 12 PRESERVATION OF CONTRACTS PRIOR TO ENACTMENT OF NEPRA ACT..........Error!

CM 13 CODE ADMINISTRATION............................................... Error! Bookmark not defined.

CM 14 NON-COMPLIANCE....................................................... Error! Bookmark not defined.

CM 1 INTRODUCTION & SCOPE

b) Generators with capacity greater than 10 MW;

d) Transmission-connected Consumers; and

e) Externally Connected Consumers/Parties, like

1. Special Licensee Transmission Company

5. Independent Power Producers (IPP)

CM 5 THE GRID CODE REVIEW PANEL

CM 5.2 The Panel shall consist of:

(a) a Chairman and up to 3 Members appointed by NTDC;

(b) a person appointed by the Authority;

(c) the following Members;

i. 2 Persons representing Generators/Generator Aggregators with a total

ii. 3 Persons representing Generators/Generator Aggregators with a total

iii. 4 Persons representing Generators/Generators Aggregators with a total

iv. Max 4 Persons representing Demand Side Aggregators wit a total

v. one representative from each Distribution Company Licensed with

vii. a one representative from each Special Purpose Transmission Company

viii. a Person representing Transmission-connected consumers;

ix. a Person representing Small Power Producers (SPP);

x. a Person representing Externally-connected Consumers

xi. one representative from Externally-connected Parties and

xii. one Member from the Industry or an Academic Institution or PEC.

CM 5.3 The panel shall:

(c) publish recommendations as to amendments to the Grid Code that NTDC or

(d) submit all the agreed recommendations to NEPRA for approval;

CM 6 JOINT GRID CODE REVIEW PANEL

CM 7 GRID CODE REVISIONS

CM 8.2.2 Where the non-compliance is:

(a) with reference to Plant and/or Apparatus connected to the Transmission

(a) the version number of the Grid Code;

CM 8.2.7 The SO shall:

CM 8.3 Generating Unit Derogation Procedure

CM 8.3.1 Power to Grant Derogations

CM 8.3.2 General Provisions

CM 8.3.3 Request for a Derogation by a Generator

(a) an identification of the Generator, Generator Aggregator, and a

(b) a description of the Generating Unit(s) for which a derogation is