Draft Distribution Code 2024
Draft Distribution Code 2024
COVER PAGE
1
DISTRIBUTION CODE
Pl
2
DISTRIBUTION CODE
4
DISTRIBUTION CODE
9
DISTRIBUTION CODE
CODE MANAGEMENT
CONTENTS
CM 2 APPLICATION OF CODE CM – 11
CM 3 COMPLIANCE CM – 11
CM 4 UNFORESEEN CIRCUMSTANCES CM – 11
CM 6 COMMUNICATIONS BETWEEN
DISTRIBUTION LICENCEES AND USERS CM – 13
CM 7 MISCELLANEOUS CM – 13
CM 12 MATTERS TO BE AGREED CM – 14
CM 13 INFORMATION DISSEMINATION CM – 14
CM 15 NON-COMPLIANCE CM – 15
CM 16 CODE ADMINISTRATION CM – 15
CM 17 DISTRIBUTION CODE AMENDMENT AND CM – 15
EXEMPTION PROCESS
CM 18 HIERARCHY CM – 17
CM 19 DISPUTES CM – 18
CM 20 LAW REVISIONS CM – 18
CM 21 SEVERABILITY CM – 18
CM 22 RULES OF INTERPRETATION CM – 18
CM 10
DISTRIBUTION CODE
CODE MANAGEMENT
CM 2 APPLICATION OF CODE
The provisions of this Distribution Code shall apply to the DNO and all the
entities using the distribution and/or also transmission network of the DNO
connected either directly or indirectly to the distribution and transmission
network of the DNO.
CM 3 COMPLIANCE
CM 3.1 A User or an entity connected to DNO’s network shall comply with this
Distribution Code unless the Consumer or the entity has been advised
otherwise by the DNO. The requisite level of compliance with the Code shall
be made a part of the contract between a Consumer and the DNO and the
Distribution Service Manual.
CM 3.2 In case a DNO is found to be in breach where a breach of the Code by a DNO
is found to be caused by a User or any entity connected to the DNO’s
distribution system not complying with the Code, the DNO is deemed to have
complied with the Code unless the DNO does not act in accordance with the
provisions of this Code and seeks the User’s compliance.
CM 3.3 The Distribution Code applies to any person or entity who is using, planning to
use or interacting with the Distribution System of the DNO.
CM 4 UNFORESEEN CIRCUMSTANCES
CM 4.1 In case of emergence of unforeseen circumstances, not included in the
Distribution Code, should the circumstances dictate the DNO shall take
prompt unilateral action to remedy the problem.
CM 4.2 If immediate action is not necessary the DNO shall promptly consult all affected
Users in aneffort to reach an agreement to take necessary mitigation actions.
If agreement cannot be reached in the 24 hours, the DNO shall determine the
most appropriate course of action under intimation to Registrar NEPRA. While
arriving at its determination, the DNO shall take into account the views
expressed by the Users and other circumstances peculiar to a particular event.
Each User shall comply with such instructions as issued by the DNO provided
that the instructions do not contravene the technical parameters of a particular
User’s System registered in the Distribution Code. The DNO shall promptly
refer all such unforeseen circumstances and any determination thereof to the
Panel for consideration as per CM 5.4.
CM 11
DISTRIBUTION CODE
CM 5 THE DISTRIBUTION CODE REVIEW PANEL
CM 5.1 All the DNOs shall jointly establish and maintain the Distribution Code
Review Panel within three months of the notification of the code, which shall
be a standing body to undertake the functions detailed in CM 5.4
CM 5.2 The panel shall function in accordance with the DCRP Operating Procedure
(DCRP-OP) duly approved by NEPRA. Subsequent to the establishment of the
panel, it shall formulate its rules and procedures to conduct business and
submit to NEPRA within three months of the establishment of the Panel.
CM 5.3 The Panel shall consist of;
a. one member appointed by each Ex-WAPDA DNO;
b. a person appointed by the Authority;
c. the following;
(i) 1 person representing Embedded Generators.
(ii) 1 person representing Bulk Power Consumers.
(iii) 1 representative from KE.
(iv) 1 member from the Industry or Academic Institution or PEC.
(v) 1 representative from the System Operator (SO).
(vi) 1 representative from NGC
(vii) 1 representative from Metering Service Providers (MSP).
(viii) 1 representative of Suppliers.
(ix) 1 Representative from the Market Operator (MO).
The chairpersonship of the DCRP shall rotate every Three (3) years
between DNOs.
The chairperson shall be from EX-WAPDA DNO’s or KE.
The decisions of the DCRP, after approval by the Authority, shall
become binding on the DNO and all Distribution Code Users.
Representation within each category shall be based on rotation and
mutual agreement as detailed in the DCRP-OP.
CM 12
DISTRIBUTION CODE
g. consider what changes are necessary to the Distribution Code arising
out of any unforeseen circumstances as referred by the DNO under CM
CM 7 MISCELLANEOUS
CM 7.1 Data and Notices
CM 7.1.1 References in the Distribution 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 7.1.2 Where applicable all data items shall refer to nominal Voltage and Frequency.
CM 13
DISTRIBUTION CODE
Illustration: - Relationship Diagram of Power System at the beginning shows
the functional inter-relationships between Grid Code and Distribution Code and
interfaces with the Network Users.
CM 12 MATTERS TO BE AGREED
Unresolved matters between Distribution Companies and Users are referred
to the Distribution Code Review Panel (DCRP) for resolution. The DCRP will
need to refer to the Authority any matters requiring interpretation of the
Distribution Code provisions.
CM 13 INFORMATION DISSEMINATION
The DNO shall establish, operate, and maintain web site providing necessary
information about the transmission and distribution system status, distribution
use of system pricing, congestion, operating procedures, technical bulletins,
technical committee meetings, and other relevant information and data.
CM 14
DISTRIBUTION CODE
CM 15 NON-COMPLIANCE
Any Act of non-compliance of any of the provision of this Distribution Code by
any of the User or entity shall be subject to penalties as per NATIONAL
ELECTRIC POWER REGULATORY AUTHORITY (FINE) REGULATIONS,
2021.
CM 16 CODE ADMINISTRATION
Distribution Companies shall be responsible for the enforcement and
administration of the distribution code. Details of the administration are given
in DCRP-OP.
The Chairperson’s DNO shall act as host and its MIRAD (Market
Implementation & Regulatory Affairs Department) shall serve as the DCRP
secretariat.
CM 15
DISTRIBUTION CODE
CM 17.5.2 The Amendment request shall be admitted once all the required information
has been submitted. The SO may request additional information or
clarifications to add to the Amendment request.
CM 17.5.3 A DCRP meeting shall be called within a period not more than two (2) weeks
after admission of the request for Amendment.
CM 17.5.4 The DCRP shall review the request for Amendment and based on the review
and discussions in meetings, submit to the Authority its recommendations
within one (1) month of its admission for its approval.
CM 17.5.5 The Authority shall consider the Amendment in light of the recommendations
of DCRP, and may require additional information from the DCRP or carry out
public or stakeholders’ consultations to arrive at an informed decision.
CM 17.5.6 The Authority may return the request to the DCRP with comments and
instructions to address in the Amendment. The DCRP shall review and re-
submit the Amendment after addressing the comments and instructions by the
Authority within fifteen (15) days of receipt of such instructions.
CM 17.5.7 After the Authority approves an Amendment, it shall be the responsibility of the
DCRP to inform all Users and DNOs about the same.
CM 17.5.8 If the Authority considers that an Amendment in the Distribution Code is
required to be made, the Authority may direct the DCRP to make such
Amendment within thirty (30) days and submit the draft Distribution Code with
relevant Amendments for the approval of the Authority. Provided that a
meeting of the DCRP may be convened to consider and submit
recommendations on the Amendment to the Authority, in support or otherwise,
for consideration. Provided further that if the DCRP does not comply with the
directions of the Authority within the specified period without providing just
cause, the Distribution Code shall be deemed to have been amended.
CM 17.6 Distribution Code Exemption
CM 17.6.1 A User or DNO can seek Exemption from complying with one or more
provisions of the Distribution Code for Plant, Apparatus, Systems or
Equipment which existed prior to the approval of this Distribution Code, and
which may be considered on the following grounds:
a) to provide for existing Plant and/or Apparatus that has not been designed
in accordance with the provisions of this Distribution Code;
b) to facilitate a smooth transition into this Distribution Code from the existing
Plant, Apparatus, Systems or Equipment;
c) to ease one or more temporary constraints that prevent compliance and
necessitate exemption; and/or
d) to deal with any variation from this Distribution Code in the Legacy
Contracts.
CM 17.6.2 A User or DNO seeking Exemption from one or more provisions of the
Distribution Code shall make a written request to the DCRP and shall be
required to justify the request in terms of both the specific circumstances and
the expected duration. As a minimum, the application request must include the
following information:
CM 16
DISTRIBUTION CODE
a) detail of the applicant;
b) relevant provisions of the Distribution Code and the required performance;
c) a description of the relevant Plant and/or Apparatus and/or equipment and
the nature and extent of non-compliance (where applicable);
d) a description of the proposal for restoring compliance (where applicable)
including details of actions to mitigate risks and restore compliance
including timelines;
e) a description of the reasonable alternative actions that have been
considered; and
f) a statement of the expected duration of the non-compliance.
CM 17.6.3 On receipt of a request for Exemption with all the information required, the
DCRP shall promptly consider such request (by seeking independent third-
party expert advice/opinion on the request, if necessary) and submit its
recommendations to the Authority within one (1) month of the admission of the
application for a final decision.
CM 17.6.4 The Authority shall consider the request in light of the recommendations of the
DCRP and shall decide on the request as appropriate. In deciding on the
request, the Authority may require additional information, and/or invite the
applicant or members of the DCRP to seek clarification on the request, and/or
publish on its website for comments by other potentially affected Users and
DNOs.
CM17.6.5 The Authority determination shall be public and uploaded to the NEPRA
website. It shall be considered as the final decision for the DCRP to
communicate to the applicant and/or for taking further action, as may be
appropriate.
CM 17.6.6 If an Exemption is granted, then the relevant User or DNO shall not be obliged
to comply with the applicable provisions of the Distribution Code (to the extent
and for the period of the Exemption) and shall comply with any alternative
provision as set forth in the Exemption.
CM17.6.7 An Exemption from the Distribution Code shall have an expiry date in order to
review its continued needs and monitor performance towards compliance.
CM 17.6.8 An Exemption granted to a User or DNO shall be transferable for the approved
period/term. However, in the event of transfer of ownership of Plant and
Apparatus of the User or DNO, the transferee shall need to seek a concurrence
of the Exemption from the Authority.
CM 17.6.9 Where a material change in circumstances has occurred, a review of any
existing Exemption, and any Exemption under consideration, may be initiated
by the Authority or the DCRP or at the request of User or DNO.
CM 18 HIERARCHY
Where there is the potential for conflict between the various codes and
contracts governing the power system, the following hierarchy, in descending
order, shall be used to decide the correct approach:
a) NEPRA Act;
CM 17
DISTRIBUTION CODE
b) NEPRA Performance Standards (Transmission);
c) NEPRA Performance Standards (Distribution);
d) The Grid Code;
e) The Distribution Code;
f) Connection Agreement (stand-alone or as part of other agreements); and
g) Any other contract or agreement between/among the parties.
CM 19 DISPUTES
CM 19.1 When there is a dispute between a DNO and any User (existing or
prospective), both parties will endeavour to resolve it amicably through
negotiations. In case, they are unable to do that within one (01) month, they
will be entitled to raise the dispute before the DCRP for settlement. The DCRP
will examine the case and try to work out a solution within one (01) month. If
either of the parties to the dispute is still not satisfied with the DCRP's
suggested solution, it will have the right to raise the dispute to NEPRA whose
decision on the issue will be final and binding to both the parties.
CM 19.2 Given the D-Code on the Consumer side only applies to Consumers with 1MW
or more, likewise this disputes section does not apply to Consumers below
1MW.
CM 20 LAW REVISIONS
All laws, regulations, standards, procedures, documents referred to in the
Distribution Code will include their latest revision, which are made to them from
time to time.
CM 21 SEVERABILITY
In the event that any provision of this Code is declared invalid by a competent
court, such provision shall be ineffective to the extent declared invalid without
affecting the validity of the rest of the Code which shall remain binding on the
Parties hereto.
CM 22 RULES OF INTERPRETATION
In this Code:
1) the headings, diagrams and table of contents are for convenience only
and shall be ignored in construing this Agreement;
2) except where the context determines otherwise, the singular includes the
plural and vice versa and the masculine gender includes the feminine;
3) references to Clauses, recitals and Schedules are, unless otherwise
specified, references to Clauses of, and Schedules and recitals to this
Code;
4) reference to any publication, statute, rule, code, regulation, instrument,
or standard means the same as amended, supplemented, or re-enacted
CM 18
DISTRIBUTION CODE
from time to time;
5) reference to any agreement means the same as amended,
supplemented, or replaced from time to time;
6) unless otherwise provided herein, whenever a consent or approval is
required by one party from the other party, such consent or approval shall
be in writing and shall not be unreasonably withheld, conditioned, or
delayed;
7) the words “include,” “including,” and “in particular” are used by way of
illustration only, and shall not be construed as, nor shall they have the
effect of, limiting the generality of the preceding words;
8) references to a User or DNO are references to a User or DNO of this
Code, including that User’s assigns or transferees permitted in
accordance with the terms of this Code and its successors in title;
9) the Schedules (and if any schedules or tables thereto) to this Code form
part of this Code, and capitalised terms and abbreviations used in the
Schedules (and if any schedules or tables thereto) which are not defined
therein shall have the meanings given to them in the definition annex of
this Code and in the event of any conflict between the main body of this
Code and a Schedule, the main body of this Code shall prevail over the
provisions of the Schedule;
10) if a period of time is specified as from a given day, or from the day of an
act or event, it shall be calculated exclusive of that day;
11) reference to any notice or notification means a notice or notification made
in writing or as otherwise expressly provided in this Code;
12) a reference to “day” means a calendar day; And
13) where transmission is used in this document it may refer to transmission
assets owned by the DNO where it acts as a TNO whereby the detailed
management of the assets comes under the Grid Code.
End of CM
CM 19
DISTRIBUTION CODE
DISTRIBUTION OPERATING CODE
DISTRIBUTION OPERATING CODE NO. 1
LOAD FORECASTS
CONTENTS
DOC-1 20
DISTRIBUTION CODE
DOC 1.3.4.2 On the basis of information provided by the Consumers as outlined in DOC
1.1.2 and DOC 1.3.4.1 above the DNO shall work out its load forecast for the
next schedule day.
DOC 1.3.5 Post Control Phase
DOC 1.3.5.1 The following data shall be supplied to the DNO by 0200 hours each day:
Details of hourly Active Power and Reactive Power output sent out to the
DNO’s System by Embedded Generator not subject to central Scheduling and
Dispatch during the previous day on a half hourly basis.
DOC-1 23
DISTRIBUTION CODE
DISTRIBUTION OPERATING CODE NO. 2
OPERATIONAL PLANNING
CONTENTS
DOC-2 24
DISTRIBUTION CODE
OPERATIONAL PLANNING
DOC-2 25
DISTRIBUTION CODE
DOC 2.3 TIMESCALES AND DATA
DOC 2.3.1 Detailed implementation of data gathering, and timescales shall be agreed
locally between the DNO and each of the Users. Due recognition shall begiven
by the DNO to voltage levels, capacities, and load levels of facilities when
assessing information requirements.
DOC 2.3.2 All information shall be provided on a weekly basis, where week 1 commences
in the first week of January as published from time to time.
DOC 2.3.3 The rolling timescales involved in DOC2 are illustrated in Figure 1 on page 20
are as follows:
a. Operational Planning Phase
i. Medium Term – covers the next calendar year and the year that
follows it
ii. Short Term – covers the current calendar year down to 8
weeks ahead
b. Programming Phase
i. Covers 24 hours to 8 weeks ahead inclusive
c. Control Phase
i. covers 0 to 24 hours ahead
DOC 2.3.4 In DOC2 Year 0 means the current calendar year at any time, Year 1 means
the next calendar year, year 2 means the calendar year after year 1 etc.
DOC 2.4 OPERATIONAL PLANNING PHASE
DOC 2.4.1 Medium Term Programme (Current Year 1-2 ahead Appendix 2)
DOC 2.4.1.1 Users and Embedded Generators (not subject to Central Despatch) shall
provide the DNO with information in accordance with DOC 2 Appendix 1.
DOC 2.4.2 Short Term Programme (Current Year down to 8 weeks ahead DOC2
Appendix 2).
DOC 2.4.2.1 The previous Medium-Term Programme shall be updated to form the basis of
the Short-Term Programme. The DNO shall continually review this programme
as necessary and periodically discuss it with the relevant parties as
appropriate.
DOC 2.4.2.2 It shall take account of such review and discussions and any additional
outages, and the following further details of each outage proposed shall be
notified at this stage by the appropriate party.
a. return to service timing of circuits (if different from the programme);
b. specific facilities to be worked upon; and
c. any other information that may be reasonably specified by the DNO
from time to time.
DOC 2.4.2.3 At any time and from time to time during the current Calendar year up to the
Programming Phase (8 weeks ahead), all the relevant Users specified in DOC
2.1.6 may notify reasonable changes and additions to the outages previously
notified during the Medium-Term planning process. The DNO shall consider
whether the changes shall adversely affect system security, stability,reliability
and quality or other parties connected to the DNO’s network and shall discuss
with the party in question. Where the change is so discussed the DNO shall
DOC-2 26
DISTRIBUTION CODE
inform the other affected Users.
DOC-2 27
DISTRIBUTION CODE
OPERATIONAL
E
n
d
of
D
O (RE
C TIM
2
DATA INPUT TIMING
Figure 1
DOC-2 28
DISTRIBUTION CODE
SYSTEM RESTORATION
CONTENTS
DOC-3 29
DISTRIBUTION CODE
DOC 3.1.2 The objectives of DOC3 are to lay down the requirements, actions, and
procedures with a view to assist System Operator in the restart of the Total
System or tooperate the Total System under abnormal situations which require
co- ordination between all Users of the DNO with a common approach to give
uniformity of priorities. It also specifies requirements to be met during force
majeure conditions.
DOC 3.1.3 The DNOs shall identify and list-out the black start facilities and inform System
Operator any changes to this information.
DOC 3.1.4 DOC3 will apply to;
a. All DNOs.
b. All Generators including Embedded Generators.
c. Bulk Power Consumers.
d. Consumers having a connected load of more than 1MW.
e. Externally connected Consumers.
DOC-3 30
DISTRIBUTION CODE
DOC-3 31
DISTRIBUTION CODE
DISTRIBUTION OPERATING CODE NO. 4
OPERATIONAL LIAISON
CONTENTS
DOC-4 32
DISTRIBUTION CODE
d. Voltage control;
34
DISTRIBUTION CODE
caused by an incident or scheduled or planned action affecting (but not on) its
System the notification to the DNO shall contain the information which theUser
has been given by the person connected to its System in relation to that incident
or scheduled or planned action (which the User must require, contractually or
otherwise the person connected to its System to give it) and the DNO may
pass on the information contained in the notification.
DOC 4.2.3.4 A notification by the DNO of an operation under DOC4 which has been caused
by an Operation or an Event on the NGC Transmission System or a connected
TNO system, may describe the Operation on the DNO’s System and shall
contain the information which the DNO has been given in relation to the
Operationor an Event on the NGC Transmission System or a connected TNO
system by System Operator. The notification (other than in relation to the
information which the DNO is merely passingon from System Operator) shall
be of sufficient detail to enable the recipient of the notification to consider and
assess the implications and consequences arising from the Operation on the
DNO’s System and shall include the name of the individual reporting the
Operation on behalf of the DNO. The recipient may ask questions to clarify the
notification.
DOC 4.2.3.5 A User may pass on the information contained in a notification to it from the
DNO to a Generator with a Generating Unit connected to the System or to
another DNO connected to its System if it is required (by a contract pursuant
to which that Generating Unit or that DNO is connected to the System) to do
so in connection with the equivalent of an Operation on its System (if the
Operation on the DNO’s Systemcaused it).
DOC 4.2.3.6 Other than as provided in DOC4.2.3.5, a User may not pass on any
information contained in a notification to it from the DNO or in a notification to
another User from the Licensee to any other person connected to its System.
Each User shall procure that any other Users receiving information, which was
contained in the notification to a User from the Licensee, which is not bound
by the Distribution Code, does not pass any information on other than as
provided above.
DOC 4.2.4 Timing
DOC 4.2.4.1 A notification under DOC 4.2.2 shall be given as far in advance as possible
and in any event shall be given in sufficient time as shall reasonably allow the
recipient to consider and assess then implications and risks arising.
DOC 4.2.5 Requirement to Notify Events
DOC 4.2.5.1 In the case of an Event on the System of a User connected to the DNO’s
System, which has or has had an Operational Effect on the DNO’s System or
on the NGC Transmission System a connected TNO system, the Usershall
notify the DNO in accordance with this DOC4.
DOC 4.2.5.2 In the case of an Event on the DNO’s System or on receipt of notification of an
Event on the NGC Transmission System or a connected TNO system, which
shall have or may, in the opinion of the DNO, have an Operational Effect on
the System of a User connected to the DNO’s System, the DNO shall notify
the User in accordance with this DOC4.
DOC 4.2.5.3 An Event may be caused by (or exacerbated by) another Event or by an
Operation on NGC system, another DNO or User System and in that situation
the information to be notified is different from that where the Event arose
independently of any other Event or Operation.
35
DISTRIBUTION CODE
DOC 4.2.5.4 Whilst in no way limiting the general requirement to notify the following are
examples of situations where notification shall be required if they have an
Operational Effect:
a. the actuation of any alarm or indication of any abnormal operating
condition;
b. adverse weather conditions being experienced;
c. breakdown of, or faults on, or temporary changes in the capabilities of,
facilities including Protection; and
d. increased risk of inadvertent Protection operation.
DOC 4.2.6 Form
DOC 4.2.6.1 A notification under DOC 4.2.5 of an Event which has arisen independently of
any other Event or of an Operation, shall describe the Event (although it need
not to state the cause of the Event) and subject to that it shall be of sufficient
detail to enable the recipient of the notification to consider and assess the
implications and risks arising. The recipient may ask questions to clarify the
notification.
DOC 4.2.6.2 A notification by the DNO of an Event which has been caused by (or
exacerbated by) another Event (the “first Event”) or by an Operation on a
User’s System shall describe the Event and shall contain the information which
the DNO has been given in relation to the first Event or that operation by the
User. The notification (other than in relation to the information which the DNO
is merely passing on from a User) shall be of sufficient detail to enable the
recipient of the notification reasonably to consider and assess the implications
and risks arising from the Event on the DNO’s System and shall include the
name of the individual reporting the Event on behalf of the DNO. The recipient
may ask questions to clarify the notification.
DOC 4.2.6.3 Where a User is reporting an Event or an Operation which itself has been
caused by (or exacerbated by) an incident or scheduled or planned action
affecting (but not on) its System the notification to the DNO shall contain the
information which the User has been given by the person connected to its
System in relation to that incident or scheduled or planned action (which the
User must require the person connected to its System to give it) and the DNO
may pass on the information contained in the notification.
DOC 4.2.6.4 A notification by the DNO of an Event under DOC 4.2.5.2 which has been
caused by (or exacerbated by) an Event or an Operation on the NGC
Transmission System or a connected TNO system,, shall describe the Event
on the DNO’s System and shall contain the information which the DNO has
been given in relation to the Operation on the NGC Transmission System or a
connected TNO system,. The notification (other than in relation to the
information which the DNO is merely passing on from NGC) shall be of
sufficient detail to enable the recipient of the notification reasonably to consider
and assess the implicationsand risks from the Event on the DNO’s System and
shall include the name of the individual reporting the Event on behalf of the
DNO. The recipient may ask questions to clarify the notification.
DOC 4.2.6.5 A User may pass on the information contained in a notification to it from the
DNO to a Generator with a Generating Unit connected to its System or to
another DNO connected to its System if it is required (by a contract pursuant
to which that Generating Unit or DNO is connected to its System) to do so in
connection with an Event on its System (if the Event on the DNO’s System
36
DISTRIBUTION CODE
caused or exacerbated it).
DOC 4.2.6.6 Other than as provided in DOC 4.2.6.5, a User may not pass on any
information contained in a notification to it from the DNO (and a User receiving
information which was contained in a notification to another User from the DNO
may not pass on such information) to any person connected to its System, but
may only say that there has been an incident onthe Total System and (if known
and if power supplies have been affected) an estimated time of return to
service. Each User should ensure that any other User receiving information,
which was, contained in a notification to such Userfrom the DNO, which is not
bound by the Distribution Code, does not passany information on other than as
provided above.
DOC 4.2.6.7 Except in an emergency situation the notification shall be dictated to the
recipient who shall record it and on completion shall repeat the notification in
full to the sender and check that it has been accurately recorded
DOC 4.2.6.8 Where an Event has been reported to the DNO by a Generator
under DOC 4.2.5 relating to a Generating Unit and in order for the Generator
to assess the implication of the Event on its System more accurately, it may
ask the DNO for details of the Fault Levels on infeeds from the Distribution
System to that Generating Unit at the time of the Event, and the DNO shall, as
soon as reasonably practicable, give the Generator the information provided
that the DNO has that information.
DOC 4.2.7 Timing
DOC 4.2.7.1 A notification under DOC 4.2.5 shall be given as soon as possible after the
occurrence of the Event, or time that the Event is known of or anticipated by
the giver of the notification under DOC4
DOC 4.2.8 System Control of the System Operator
DOC 4.2.8.1 Where a part of a DNO’s System is, by agreement, under the System Control
of the System Operator then the requirements and provisions of OC6 of the
Grid Code shall apply to that situation as if the DNO’s system is a part of NGC
System.
DOC 4.2.9 System Control of the DNO
DOC 4.2.9.1 Where a part of a System of a User is, by agreement, under the System Control
of the DNO then the requirements and provisions of this DOC4 shall apply to
that situation as if the User’s System is a part of the DNO’s System.
DOC 4.2.10 Significant Incidents
DOC 4.2.10.1 Where an Event on the DNO’s System or the Dedicated System of a User has
had or may have had a significant effect on the System of any of the others,
the Event shall be reported in writing to the owner of the System affected in
accordance with the provisions of DOC5. Such an Event shall be termed a
“Significant Incident”.
DOC 4.2.10.2 Where a DNO notifies a User of an Event under DOC4, which the User
considers has had or may have a significant effect on that User’s dedicated
System, that User shall require a DNO to report that Event in writing and shall
notify the DNO accordingly. Such an Event shall also be termed a “Significant
Incident”.
DOC 4.2.10.3 Without limiting the general descriptions set out in DOC 4.2.10.1 or
DOC4.2.10.2 a Significant Incident shall include Events which result in, or may
result in, the following:
37
DISTRIBUTION CODE
a. operation of facilities controlled either manually or automatically;
b. voltage outside the limits, prescribed in Performance Standards
(Distribution);
c. System frequency outside the limits, provided in the grid code;
d. System Stability failure (transient and voltage both);
e. Likelihood of system collapse or shut down;
f. Thermal overloading of the facilities; and
g. Tripping of large amounts of load or generation.
38
DISTRIBUTION CODE
CONTENTS
DOC-5 39
DISTRIBUTION CODE
DOC-5 41
DISTRIBUTION CODE
CONNECTION POINT
CONTENTS
DOC-6 42
DISTRIBUTION CODE
DOC 6.2.2.3 Where relevant, copies of the Safety Management System (safety
DOC-6 43
DISTRIBUTION CODE
code) and related documentation shall be exchanged between the DNO
and Users for each Operational Boundary at the time of their connection
with the DNO’s Distribution System.
DOC 6.2.3 Authorised Personnel
DOC 6.2.3.1 Safety Management System must include the provision for written
Authorisation of personnel concerned with the control, operation, work
or testing of Plant and Apparatus forming part of, or connected to, the
DNO’s System.
DOC 6.2.3.2 Each individual Authorisation shall indicate the class of operation
and/or work permitted and the section of the System to which the
Authorisation applies.
DOC-6 44
DISTRIBUTION CODE
DOC 6.4.2.2 All documentation relevant to the Operation of the Distribution System,
and safety precautions taken for work or tests, shall be held by the DNO
and the appropriate User for a period of not less than one year.
DOC 6.4.3 System Diagrams
DOC 6.4.3.1 Diagrams illustrating sufficient information for control personnel to
carry out their duties shall be exchanged by the DNO and the appropriate
User.
DOC 6.4.4 Communications
DOC 6.4.4.1 Where the DNO reasonably specifies the need, suitable communication
systems and protocols shall be established between the DNO and other
Users to ensure the control function is carried out in a safe and secure
manner.
DOC 6.4.4.2 Where the DNO reasonably decides a backup or alternative routing of
communication is necessary to provide for the safe and secure
Operation of the DNO’s System the means shall be agreed with the
appropriate Users.
DOC 6.4.4.3 Schedules of telephone numbers / call signs shall be exchanged by
the DNO and appropriate User to enable control activities to be efficiently
co-ordinated.
DOC 6.4.4.4 The DNO and appropriate Users shall establish 24-hour availability of
personnel with suitable Authorisation where the joint operational
requirements demand it.
DOC-6 45
DISTRIBUTION CODE
PLANT IDENTIFICATION
CONTENTS
DOC-7 46
DISTRIBUTION CODE
DOC-7 47
DISTRIBUTION CODE
DOC-7 48
DISTRIBUTION CODE
SYSTEM TESTS
CONTENTS
DOC-8 49
DISTRIBUTION CODE
DOC 8.2.2.1 When the DNO or a User intends to undertake a System Test which shall have
or may have an effect on the System of others normally twelve months’ notice,
or as otherwise agreed by the DNO, of the proposed System Test shall be
given by the person proposing the System Test (the ‘Test Proposer’) to the
DNO and to those Users who may be affected by such a System Test.
DOC 8.2.2.2 The proposal shall be in writing and shall contain details of the nature and
purpose of the proposed System Test and shall indicate the extent and
situation of the facilities involved.
DOC 8.2.2.3 If the information set out in the proposal notice is considered insufficient by the
recipient, they shall contact the party proposing the test with a written request
for further information which shall be supplied as soon as reasonably
DOC-8 50
DISTRIBUTION CODE
practicable. The DNO shall not be required to do anything under DOC 8 until
it satisfied with the details supplied in the proposal or pursuant to a request for
further information.
DOC 8.2.2.4 If the DNO wishes to undertake a System Test the DNO shall be deemed to
have received a proposal of that System Test.
DOC 8.2.3 Preliminary Notice and Establishment of Test Panel
DOC 8.2.3.1 The DNO shall carryout the overall co-ordination of the System Test, using the
information supplied to it under DOC 8 and shall identify in its reasonable
estimation, which Users other than the party proposing the test, may be
affected by the proposed System Test.
DOC 8.2.3.2 A Test Co-ordinator, who shall be a suitably qualified person, shall be
appointed by the DNO with the agreement of the Users which the DNO has
identified may be affected and shall act as Chairman of the TestPanel referred
to in DOC 8.2.4 (the Test Panel).
DOC 8.2.3.3 All Users identified under DOC 8.2.3.1 shall be given in writing, by the Test Co-
ordinator, a preliminary notice of the proposed System Test. The preliminary
notice shall contain:
a. The Test Co-ordinator’s name and nominating company.
b. The details of the nature and purpose of the proposed System Test,
the extent and situation of Plant or Apparatus involved, and the Users
identified by the DNO under DOC 8.2.3.1.
c. An invitation to each User to nominate within one month a suitably
qualified representative, or representatives where appropriate, to be a
member of the Test Panel for the proposed System Test.
DOC 8.2.3.4 The preliminary notice shall be sent within one month of the receipt of the
proposal notice or the receipt of any further information requested under
DOC 8.2.2.3.
DOC 8.2.3.5 As soon as possible after the expiry of that one-month period all relevant Users
and the Test Proposer shall be notified by the Test Co-ordinator of the
composition of the Test Panel.
DOC 8.2.3.6 Where the test has impacts on total system then:
a. SO shall be a member of that test panel; and
b. Grid Code OC 10. OPERATIONAL TESTING requirements shall be
taken into account.
DOC 8.2.4 Test Panel
DOC 8.2.4.1 A meeting of the Test Panel shall take place as soon as possible after the
relevant Users and the Test Proposer have been notified of the composition of
the Test Panel, and in any event within one month of the appointment of the
Test Panel.
DOC 8.2.4.2 The Test Panel shall consider:
a. the details of the nature and purpose of the proposed System Test and
other matters set out in the proposal notice (together with any further
information requested under DOC 8.2.2);
b. the economic, operational and risk implications of the proposed System
Test;
DOC-8 51
DISTRIBUTION CODE
c. the possibility of combining the proposed System Test with any other
tests and with Plant and / or Apparatus outages which arise pursuant
to the operational planning requirements of the DNO, the System
Operator and Users; and
d. implications of the proposed System Test on the Scheduling and
Despatch of Generating Plant, insofar as it is able to do so.
DOC 8.2.4.3 Users identified under DOC 8.2.3.1 and the DNO (whether or not they are
represented on the Test Panel) shall be obliged to supply that Test Panel upon
written request with such details as the Test Panel reasonably requires in order
to consider the proposed System Test.
DOC 8.2.4.4 The Test Panel shall be convened by the Test Co-ordinator as often as he
deems necessary to conduct its business.
DOC 8.2.5 Proposal Report
DOC 8.2.5.1 Within two months of the first meeting the Test Panel shall submit a report,
which in this DOC 8 shall be called a proposal report, which shall contain;
a. proposals for carrying out the System Test (including the manner in
which the System Test is to be monitored);
b. an allocation of costs (including un-anticipated costs) between the
affected parties, (the general principle being that the Test Proposer
shall bear the costs); and
c. such other matters as the Test Panel consider appropriate.
The proposal report may include requirements for indemnities to be given in
respect of claims and losses arising from the System Test. All System Test
procedures must comply with all applicable legislation.
DOC 8.2.5.2 If the Test Panel is unable to agree unanimously on any decision in preparing
its proposal report, the disputed matter regarding System Testing and
inspection shall be referred to the Distribution Code Review Panel for
resolution.
DOC 8.2.5.3 The proposal report shall be submitted to all those who received a preliminary
notice under DOC 8.2.2.
DOC 8.2.5.4 Within fourteen days of receipt of the proposal report, each recipient shall
respond to the Test Co-ordinator with its approval of the proposal report or its
reason for non-approval.
DOC 8.2.5.5 In the event of non-approval by one or more recipients, the Test Panel shall as
soon as practicable meet in order to determine whether the proposed System
Test can be modified to meet the objection or objections.
DOC 8.2.5.6 If the proposed System Test cannot be so modified, the matter be referred to
the Distribution Code Review Panel for resolution.
DOC 8.2.5.7 If the proposed System Test can be so modified, the Test Panel shall as soon
as practicable, and in any event within one month of meeting to discuss the
responses to the proposal report, submit a revised proposal report and the
provisions of DOC 8.2.5.3 and DOC 8.2.5.4 shall apply to that submission.
DOC 8.2.5.8 In the event of non-approval of the revised proposal report by one or more
recipients, the disputed matter shall be referred to the Distribution Code
Review Panel for resolution.
DOC 8.2.6 Final Test Programme
DOC-8 52
DISTRIBUTION CODE
DOC 8.2.6.1 If the proposal report (or, as the case may be, the revised proposal report) is
approved by all recipients, the proposed System Test can proceed and at least
one month prior to the date of the proposed System Test, the Test Panelshall
submit to the DNO and all recipients of the proposal notice a programme which
in this DOC 8 shall be called a final test programme stating the switching
sequence and proposed timings, a list of those staff involved in the carrying
out of the System Test (including those responsible for the site safety) and
such other matters as the Test Panel deem appropriate.
DOC 8.2.6.2 The final test programme shall bind all recipients to act in accordance with the
provisions contained within the programme in relation to the proposed System
Test.
DOC 8.2.6.3 Any problems with the proposed System Test which arise or are anticipated
after the issue of the final test programme and prior to the day of the proposed
System Test must be notified to the Test Co-ordinator as soon as possible in
writing. If the Test Co-ordinator decides that these anticipated problems merit
an amendment to or postponement of the System Test, he shall notify any
party involved in the proposed System Test accordingly.
DOC 8.2.6.4 If on the day of the proposed System Test operating conditions on the System
are such that any party involved in the proposed System Test wishes to delay
or cancel the start or continuance of the System Test, they shall immediately
inform the Test Co-ordinator of this decision and the reason for it. The Test Co-
ordinator shall then postpone or cancel, as the case may be, the System Test
and shall, if possible, agree with all parties involved in the proposed System
Test another suitable time and date or if he cannot reach such agreement, shall
reconvene the Test Panel as soon as practicable which shall endeavour to
arrange another suitable time and date and the relevant provisions of this DOC
8 shall apply.
DOC 8.2.7 Final Report
DOC 8.2.7.1 At the conclusion of the System Test, the Test Proposer shall be responsible
for preparing a written report (the ‘final report’) of the System Test for
submission to other members of the Test Panel.
DOC 8.2.7.2 The final report shall include a description of the facilities, tested and of the
System Test carried out, together with the results, conclusions, and
recommendations.
DOC 8.2.7.3 The final report shall not be distributed to any party which is not represented
on the Test Panel unless the Test Panel, having considered the confidentiality
issues, shall have unanimously approved such distribution.
DOC 8.2.7.4 When the final report has been submitted under DOC 8.2.7 the Test Panel
shall be dissolved.
DOC-8 53
DISTRIBUTION CODE
DISTRIBUTION OPERATING CODE NO. 9
CONTENTS
DOC-9 54
DISTRIBUTION CODE
DOC-9 55
DISTRIBUTION CODE
DOC-9 56
DISTRIBUTION CODE
DISTRIBUTION OPERATING CODE NO. 1 0
CONTENTS
DOC 10.5 PCC, SUPPLIERS AND THE COMPETATIVE MARKET DOC 10-59
DOC-10 57
DISTRIBUTION CODE
DOC-10 58
DISTRIBUTION CODE
DOC 10.5.1 The PCC shall have staff responsible for day-to-day interaction with Electric
Power Suppliers.
DOC 10.5.2 The PCC shall have staff responsible for day-to-day interaction with Bulk
Power Consumers.
DOC 10.5.4 The PCC shall apply Load Management (Demand Side Management) and
Load Shedding in a technically, socially and commercially appropriate manner
DOC 10.6.1 Under SPR 6.2 each DNO is required to install metering on each 11kV feeder,
under SPR 6.3 the DNO is required to integrate its IT infrastructure
DOC 10.6.2 It is imperative that the PCC stores all this data in a manner that:
a. Can be efficiently analysed.
b. Can be shared with the SO as is relevant.
c. Is available to NEPRA for their regulatory processes.
d. Can be shared with other stakeholders where relevant for planning
purposes.
DOC-10 59
DISTRIBUTION CODE
CONTENTS
DPC 60
DISTRIBUTION CODE
DPC 1 INTRODUCTION
DPC 1.1 The Distribution Planning Code (DPC) contains distribution system planning
and specifies criteria and principles to be followed by the DNO in the planning
and development of its Distribution System. DPC also applies to Users of the
DNO’s System in the planning and development of their Systems in so far as
they affect the DNO’s System.
DPC 1.2 The User’s requirements may necessitate the reinforcement of or the
extension to the DNO Distribution System and in some cases may require the
DNO to seek reinforcement of or extension to the relevant NGC/ DNO interface
and capacity, such work being identified by the DNO or NGC as appropriate
shall be a part of the discussions with the User concerning the User’s
requirements. Such requirements, if not already covered in the Connection
Agreement may require modification of the agreement.
DPC 2 SCOPE
DPC 2.1 The Distribution Planning Code (‘DPC’) applies to the following:
a. All Generators and DNOs or any other entity who is using or planning
to use the Distribution System of the DNO;
b. NGC; and
c. The System Operator
DPC 2.2 This sub-code outlines the following:
a. General principles, aims and objectives of Distribution Planning.
b. Recommended planning criteria voltages, power factor, equipment
loading criteria, Fault Level, and security standards.
c. Load planning.
d. Power System Losses.
e. Loss Reduction.
f. Load Management.
DPC 61
DISTRIBUTION CODE
DPC 63
DISTRIBUTION CODE
factor as follows;
Load Factor = kWh in period
Peak kW load x hours in period
Load can be used to calculate kW load for substation or a particular feeder and
with a given power factor can calculate the kVA load of the respective sub-
station or feeder.
DPC 65
DISTRIBUTION CODE
DPC 66
DISTRIBUTION CODE
DPC 68
DISTRIBUTION CODE
DISTRIBUTION DESIGN CODE
CONTENT
DDC 69
DISTRIBUTION CODE
DDC 1 INTRODUCTION
The DNO must develop, operate, and maintain an efficient, secure, and
coordinated system of electricity supply that is both economical and safe.
DDC sets out principles and standards to be applied in the design process of
the DNO’s System and any User connections to the Distribution System of the
DNO.
Nothing contained in DDC is intended to inhibit design innovation. DDC is,
therefore, cognizant of the performance requirements of the DNO’s System to
be operated and managed in an efficient, secure, safe, and economical
manner as per the provisions of the Performance Standards (Distribution)-
Rules.
DDC described Design Criteria, frequency and voltage parameters, design
principles of equipment, cables and lines and other electrical facilities in terms
of their loading thresholds. Loading thresholds for design purpose shall be
considered as 100% of rated capacity only, i.e. overload capability shall be
conserved for operational use.
DDC 71
DISTRIBUTION CODE
specified operating voltage range and at the design short-circuit rating
of the DNO’s System to which it is connected having due regard to fault
carrying capabilities and making and breaking duties of the circuit
breakers. In appropriate circumstances, details of the System to which
connection is to be made shall be provided by the DNO to the
prospective User.
d. The standards, publications and specifications referred to in
paragraphs (a) to (c) above are such standards, publications, and
specifications current at the time that the facility was manufactured
(and not commissioned) in the case of facility on the Total System or
awaiting use or re-use. If any such facility is subsequently moved to a
new location or used in a different way, or for a different purpose, or is
otherwise modified then such standards, publications and
specifications current at the time that the facility was manufactured
(and not commissioned) shall apply provided that in applying such
standards, publications and specifications the facility is reasonably fit
for its intended purpose and use having due regard to the obligations
of the DNO under their respective licenses and the User under the
Distribution Service Manual.
DDC 4 EARTHING
A DNO must ensure that the neutrals and body of the power transformer at a
grid station shall be connected to earth mesh provided in the yard of the grid
stations through independent leads. The neutral wire should additionally be
connected to earth rod and mesh through a separate lead. All other
installations in the yard be connected to earth mesh. The earth resistance shall
be up to or less than 2Ω for Grid Station equipment.
The earthing of a distribution transformer, the neutral and body of the
transformer shall be connected to ground rods as per IEC and PSI Standards
Design Specifications.
Earthing of Consumer Service and its meter shall be as per design standards
adopted by the DNOs; and consistent with IEC, and IEEE Standards.
The earth resistance of the distribution transformers and HT/LT
structures/poles shall not be more than 2.5 and 5Ω respectively.
The DNO shall perform verification of its electrical system’s earthing at a
frequency defined by NEPRA’s Power Safety Code.
End of DDC
DDC 72
DISTRIBUTION CODE
CONNECTION CODE
CONTENTS
CC 1 INTRODUCTION CC-74
CC 2 SCOPE CC-74
CC 4 PRINCIPALS CC-75
CC 73
DISTRIBUTION CODE
CONNECTION CODE
CC 1 INTRODUCTION
This section deals with the connection principles, requirements, guidelines,
and procedures for the entities other than NGC seeking either new connection
with DNO's network or modifying existing connection.
In this sub-code of the Distribution Code, the network connection requirements
have been outlined which specify both the minimum technical/functional,
design and operating criteria that must be complied with by any User
connected to or seeking connection with the DNO's network.It also prescribes
the application procedures to be adopted by the prospective Users, and the
obligation that needs to be fulfilled by the DNO related to providing connection
and operating its system after the connection has been provided. Furthermore,
it specifies the information requirements on the part ofprospective and existing
Users of the DNO's system. The procedures contained in this chapter are
applicable to the following.
a. Embedded Generators
b. Other Distribution Companies
c. Externally Connected Consumers
d. Externally Connected Parties
e. BPCs.
CC 2 SCOPE
This chapter deals with connection to the DNO’s network at Distribution
Voltages in respect of the entities listed in CC1. The time limits related to
provide new connection to Applicants provided in this sub-code shall not be
inconsistent with the time limits as provided in NEPRA Performance Standards
(Distribution)-Rules clause 4(c). These time limits have also been detailed in
the Distribution Service Manual approved by NEPRA.
CC 74
DISTRIBUTION CODE
CC 4 PRINCIPLES
The conditionalities and the procedures covered under this Connection Code
are based on, among others, the following principles, and assumptions:
a. All Users shall have an opportunity to form a connection to the network;
and have access to the services provided by the DNO.
b. To provide a uniform treatment in identifying terms and conditions for
each applicant.
c. The treatment will significantly depend on whether the applicant is
passive, i.e. no generation, or active, with generation either standard or
SWE. Significantly more information will be required from active
applicants.
d. Where a User later wishes to add generation to their internal network
this will be considered to be a modification of a connection and a new
connection application will be required.
CC 5 OWNERSHIP BOUNDARIES
CC 5.1 The point or points at which supply is given or taken between the DNO’s
System and Users shall be agreed upon between the DNO and the User as
required. For supplies at Low Voltage (LV) the general rule is that the point of
supply will be at the Users terminals of the DNO’s owned metering equipment
but not inconsistent with Distribution Service Manual and Consumer Eligibility
Criteria. For High Voltage (HV) supplies, including connections between
Distribution DNOs and Users, and where necessarybusbar connected supplies
at Low Voltage, the points of supply shall be subject to specific agreement
between the parties in each case.
CC 5.2 The respective ownership of Plant and Apparatus shall be recorded in a
Connection Agreement between the DNO and the User as required. In the
absence of a separate agreement between the parties to the contrary,
construction, commissioning, control, operation, and maintenance
responsibilities shall follow ownership.
CC 5.3 For supplies at High Voltage, the DNO shall with the User’s agreement
prepare a responsibility schedule and, an Operation Diagram determined by
the DNO during the application process for connection showing the agreed
Ownership Boundary. Copies of these documents shall be retained bythe DNO
and User. Changes in the boundary arrangements proposed by either party
must be agreed in advance and shall be re-coded on the DNO Operation
Diagram.
CC 5.4 Bifurcation of Network between Distribution Companies and Azad Jammu and
Kashmir (AJK) Network
AJK Electricity Department is taking power from PESCO, IESCO and GEPCO
at 11kV voltage. The Network Bifurcation Point shall be the jumpers of 11kV
Power cable connected to the panel.
CC 5.5 Nomenclature
The DNO shall supply the User and the User shall supply the DNO details of
the numbering and nomenclature of Apparatus at or near the Ownership
Boundary.
CC 75
DISTRIBUTION CODE
CC 6 ESTABLISHING OR MODIFYING CONNECTION
CC 6.1 Process and Procedures
The entities listed in CC 1 seeking a new connection or modification of an
existing connection shall adopt the following process and the procedures.
The DNO shall follow the connection process detailed in Error! Reference s
ource not found. attached at the end of this sub-code, whereas BPCs, and
Special Purpose Transmission Licensee (SPTL), Housing Colonies, Defence
Establishment, and Embedded Generators shall submit their applications to
the respective DNO . The DNO shall evaluate their application for providing
the connection and shall forward to the System Operator (wherever applicable)
what DNO considers to be necessary.
CC 6.2 Intention Application
The entity wishing to modify its existing connection or connect to the network
of the DNO at Distribution Voltages for the first time shall prepare an intention
proposal. The proposal must indicate:
a. The type of facilities he intends to establish (distribution and/or
transmission system).
b. Size of the facility and range including load factor.
c. Proposed Connection Point.
d. Tentative Schedule for connection.
e. Protection and metering requirements.
f. Voltage level at which the connection is required/modified.
g. Maximum and minimum active and reactive power requirements.
CC 77
DISTRIBUTION CODE
a. Technical Feasibility Report.
b. Detailed Design of the facility the applicant intends to install.
c. A final committed Implementation Schedule showing proposed
milestone dates for construction and commissioning of the applicant’s
connection facilities.
d. Details of the Protection arrangements and settings keeping in view the
protection schemes adopted by the Grid Code and concerned DNO.
e. Copies of all Safety Rules and Local Safety Instructions applicable at
Applicant’s Sites.
f. Proposed usage of the facilities.
DNO shall carryout preliminary evaluation of the application and if the
application meets requirements of this Code and the technical criteria for
connection/ modification, it shall send its concurrence to the Applicant to allow
connection with its network. Where the DNO believes it necessary the System
Operator shall be consulted and shall evaluate the application with reference
to the Grid Code and its obligations as System Operator.
If the Applicant wants to have connection at multiple connection points of the
network of DNO, then he shall include all the connection points in the same
application, however, the term and conditions for each connection point may
vary in accordance with the conditions prevailing at each connection point
The DNO shall evaluate the application and its contents within 30 (thirty) days
and invite the applicant to have negotiations for Connection Agreement.
CC 6.5 Connection Agreements
If the Applicant wishes to accept the Offer to Connect, the Connection
Applicant must:
a. Agree and apply for licence from NEPRA to operate as an Embedded
Generator, or a Special Purpose Transmission Licensee.
b. Agree to be bound by relevant provisions of the Grid Code (if applicable)
and Distribution Code.
c. Must follow all relevant rules and regulations already issued or to be
issued in future by the DNO, GoP, NEPRA, or the relevant Authorities
including Safety Code of the concerned DNO.
d. The detailed environmental framework is not being provided in the Grid
Code and Distribution Code; however, the applicant must agree to abide
by all such requirements, which are set out by the environmental
agencies or NEPRA Licences, Rules, and Regulations.
e. Enter into a Connection Agreement with each relevant distribution DNO
and, in doing so, must use its reasonable endeavours tonegotiate in
good faith with all parties with which the Applicant must enter into such
a Connection Agreement.
The DNO must, within 10 business days of receipt of communication regarding
Connection Agreement shall convey its comments on the metering, and
protection arrangements.
If the DNO believes the connection may cause deteriorated quality and
reliability of supply at the connection points of other Users caused by the
Applicant’s connection to the network and subsequent operation, the
application will be rejected, and the applicant will need to revise and reapply.
CC 78
DISTRIBUTION CODE
In the event of disagreement between the parties, Review Panel shall be the
arbitrator whereas the final decision shall be made by NEPRA only, if
requested by the Review Panel.
CC 6.6 The design of connection between DNO’s distribution system and Users
shall be in accordance with the principles set out in the Grid Code, Distribution
Code, Performance Standards(Distribution), Consumer Eligibility Criteria and
Distribution Service Manual, as applicable.
CC 79
DISTRIBUTION CODE
Before entering into the Connection Agreement, it shall be necessary for the
DNO to be reasonably satisfied that the User's system and
installation/equipment at the boundary with the DNO’s distribution systemor
network shall comply with all appropriate requirements of the Distribution
Code/Grid Code and applicable design specifications of the DNO.
CC 80
DISTRIBUTION CODE
CC 6.8 Communication
Where for operational reasons, DNO determines that a means of routine and
emergency operation, communication between the DNO and the User is
required, then the same shall be provided and maintained by the DNO.
CC 6.9 Supervisory Control and Data Acquisition (SCADA) System
DNO shall have a communication system and supervisory control and data
acquisition (SCADA) system to monitor and control its network including
generators connected to its network. At the generating station, a RTU shall be
provided for monitoring and control of each generating unit. In addition, RTU
provided by the Generator shall have facility of dispatching and loading the
generating unit by the DNO from DNO’s Power Control Centre.
CC 6.9.1 The SCADA System will be used by the DNO for real time monitoring and
control of the Distribution Network during normal, contingency, emergency,
extreme emergency and restorative conditions.
CC 6.9.2 All Users shall install remote telemetry equipment and associated auxiliary
components, at their respective facilities for exchanging real time data and
control signals with the DNO’s SCADA System through standard IEC
protocols. The cost of integration of Users telemetry equipment (Remote
Telemetry Units RTUs, SAS/PCS/DCS Gateways etc.) with the DNO’s SCADA
System, both at Main and Backup Control Centers, will be borne by the relevant
Users.
CC 6.9.3 Remote telemetry equipment, which may include RTU, PCS/DCS/SAS
Gateways, IEDs or any other such equipment/Facility (to be installed with prior
approval of the DNO), shall be capable of exchanging real time data and
control signals with the DNO’s SCADA System through standard IEC data
communication protocols.
CC 6.9.4 The remote telemetry equipment of Users shall be compatible with the DNO
SCADA master station protocol requirements and must provide redundant and
standard IEC interfaces for data connectivity with PCC. It shall also be capable
of time stamping of signals and events on minimum resolution of 1 millisecond
or finer resolution as specified by the DNO.
CC 6.9.5 All Users shall maintain the remote telemetry, networking and communication
equipment at their respective sites and shall be responsible to expand and
upgrade the equipment as and when required by the DNO. All such equipment
shall have at least 50% spare capacity for future expansion. The cost of such
expansion and upgradation of User’s remote telemetry system along with its
auxiliary components and its integration with DNO SCADA System will be
borne by the relevant Users.
CC 6.9.6 SCADA Signals Interface Cabinets/Cubicles (SIC) shall be installed in the
User’s Control Centre/Control Facility, for the transmission of signals and
indications to and from the DNO. The provision and maintenance of the wiring
and signalling from the User’s Plant and equipment to the interface cabinets
shall be the responsibility of the User.
CC 6.9.7 In case of Generators, signals and indications must be provided to the DNO
on individual Generating Unit basis.
CC 6.9.8 In cases where the Users are equipped with or intending to develop their own
SCADA System or any other telemetry system such as Automatic Meter
Reading (AMR), Smart/Secured Metering System (SMS), Web portals based
telemetry, Awareness System, etc., covering all or part of its Distribution
System or Plant/equipment and the DNO considers necessary to exchange the
information collected into such system, data communication/exchange through
CC 81
DISTRIBUTION CODE
standard IEC protocols between the DNO’s and User’s SCADA or other such
system, as the case may be, shall be established.
CC 6.9.9 If any change occurs in the User’s Plant and equipment, User shall be
responsible to incorporate all such changes in the remote telemetry equipment.
CC 6.9.10 The DNO shall have the capability to deactivate and reactivate the scanning of
a given RTU, as well as the capability of monitoring the availability of all RTUs
from the PCC.
CC 6.9.11 In the absence of any such remote telemetry system or during development
phase of such remote telemetry facilities, Users shall provide the real time
data/information related to its plant and equipment to DNO through interim
alternate arrangements with prior approval of DNO.
CC 82
DISTRIBUTION CODE
facility from the DNO’s network or subject to the procedure set out in the
Connection Agreement.
However, it shall be ensured that disconnection and reconnection procedures
are made an integral part of the Connection Agreement.
Before taking decision for disconnection of the equipment or the facility, it must
be ensured that by such disconnection there is no impact on the quality or
reliability of supply to other Users. If an impact is found, it shall be handled as
per the provision of the contract between DNO and the User to resolve the
issue.
Prior to disconnection, the DNO must inform the System Operator about the
disconnection proposal and its expected impact on the network.
The voluntary disconnection and subsequent re-connection shall be subject to
fulfilment of all the requirements placed under the provision of Distribution
Licence, NEPRA Act and Rules, and Distribution Service Manual.
CC 7.2.2 Involuntary Disconnection
The DNO may disconnect equipment or the facility of User or entity if:
a. The User is not operating its facility in accordance with the Connection
Agreement or the provisions of Grid/Distribution Codes, in accordance
with the law of the land, or the Distribution Service Manual giving
advance notice depending upon the situation.
b. In case of operational emergencies due to which electrical system of
the DNO is incapable of providing the required services.
c. In the event of emergencies, the User’s facility must be disconnected in
an orderly manner or as indicated in the Connection Agreement, so that
the security of the system, as per Grid Code, is not affected.
d. A defaulted User must not bring proceedings against the DNO to seek
to recover any amount for any loss or damage incurred due to the
disconnection.
CC 7.2.3 Reconnection of the Equipment or the Facility
The DNO, following an outage or emergency, must reconnect the User’s
Facility after confirming that:
a. The User has rectified all such circumstances, which were the cause of
disconnection.
b. The DNO must charge a reasonable cost as indicated in theConnection
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 the emergency have been
eliminated, and the network has returned to steady state operating
conditions.
CC 7.3 General Connection Requirements on Generators
CC 7.3.1 Connection Related Obligations of Generators
Generators proposing to connect to the DNO’s system shall submit a detailed
design report that covers, as a minimum, the following subjects:
a. Suitability requirements
CC 83
DISTRIBUTION CODE
b. Adequate Fault Levels at the Site
c. Maintenance outage co-ordination
d. Stability requirements.
e. Insulation level requirements (switching insulation levels and high
voltage protection)
f. Lightning protection for average isokeraunic levels for the site.
g. Efficient and simple operational co-ordination procedures
h. Plant Dispatch obligations
i. Isolation Equipment
j. Grounding method (Solid, through NGR or isolated).
CC 7.3.2 Generating Plant Performance Requirements
For Embedded Generators, the electrical parameters shall be specified by the
DNO at the time of Offer for Connection. A Generating Unit must be capable
of supplying its Registered Capacity within the System frequency range of 49
to 51Hz as per the Grid Code. The output power should not be affected by
voltage changes within the permitted operating range as provided in this Code,
Grid Code or Transmission Performance Standards. The Generating Unit shall
comply with the voltage and frequency requirements as set by the DNO in the
Connection Agreement not inconsistent with the Codes and Performance
Standards at all times.
CC 7.3.3 Co-ordination with Existing Protection
It shall be necessary for the Protection associated with Embedded Generating
Plant to co-ordinate with the Protection associated with the DNO’s systemas
follows:
a. For Generating Unit directly connected to the DNO’s system, the
Generating Unit must meet the target clearance times for fault current
interchange with the DNO’s system in order to reduce to a minimum the
impact on the DNO’s system due to faults on circuits owned by
Generators. The DNO shall ensure that the DNO Protection settings
meet its own target clearance times. Protection systems of both parties
must be well-coordinated and periodically tested for their functioning as
expected.
The target clearance times are measured from fault current inception to
arc extinction of the circuit breaker and shall be specified by the DNO
to the requirements of the connecting network of the DNO’s system.
b. The settings of any Protection controlling a Circuit Breaker or the
operating values of any automatic switching device at any point of
connection with the DNO’s system shall be agreed upon between the
DNO and the Generator in writing during the initial connection
consultation process.
The Protection settings or operating values shall not be changed without
the express agreement of the DNO and/or the System Operator, if
applicable.
c. It shall be necessary for the Generating Plant Protection to co-ordinate
with any auto-reclose policy specified by the DNO.
d. Any Generating Unit connected to the DNO’s system shall be required
to withstand, without tripping, the Negative Phase Sequence loading
incurred during the clearance of a close-up phase-to-phase fault by
System Back-up Protection which shall be within the Generating Unit
short-term rating in the DNO’s system. The DNO shall advise the
CC 84
DISTRIBUTION CODE
Generator of the expected Negative Phase Sequence loadings during
the Connection Agreement process.
CC 7.3.4 Islanding
It is conceivable that a part of the DNO’s system, to which Embedded
Generators are connected can, during emergency conditions, become
detached from the rest of the distribution and transmission System. It shall be
necessary for the DNO to decide, dependent on local network conditions, if it is
desirable for the Embedded Generators to continue to generate onto the
islanded DNO’s system.
If no facilities exist for the subsequent resynchronization with the rest of the
DNO’s system, then the Embedded Generator shall under DNO’s instruction,
ensure that the Generating Unit is disconnected for resynchronization.
Under emergency conditions there is an expectation that some generation
shall continue to operate outside the frequency limits specified in the Grid
Code. However, for Embedded Generators connected to the DNO’s system it
is likely that this could mean connection within an automatic low frequency load
disconnection zone. Consequently, Embedded Generators should ensure that
all Protection on Generating Unit should have settings to co-ordinate with those
on the automatic low frequency load disconnection equipment, which shall be
detailed by the DNO.
An active Externally Connected Consumer or an Externally Connected Party
must take particular care when there is the possibility of islanding. It is expected
that the DNO will agree and put in place a specific procedure to cover this
eventuality.
CC 7.3.5 Generating Unit Commissioning Tests
Where a Generator requires connection to the DNO’s system in advance of the
commissioning date, for the purposes of testing, the Generator must comply
with the requirements of the Connection Agreement. The Generator shall
provide the DNO with a commissioning programme, approved by theDNO if
reasonable in the circumstances, to allow commissioning tests to be co-
ordinated.
Under certain circumstances either more or less detailed information than that
specified above might need to be provided and shall be made available by the
Generator at the request of the DNO.
CC 7.3.6 Any relevant information regarding technical design and operational criteria as
mentioned in CC 5.4 of the Grid Code may also be supplied along with the
following information.
a. Earthing requirements/negative sequence current injection
b. AGC (frequency and speed governing characteristics)
c. Emergency generator disconnection conditionalities.
d. Power quality requirements
i. Harmonics
ii. Resonance
iii. Voltage flicker / dips
e. Voltage unbalance
f. Adequate and accurate metering equipment.
CC 85
DISTRIBUTION CODE
CC 7.3.7 Preferred Connection Arrangement
Two schemes have been shown in the annex at the end of the C-Code for
interconnection of generators. The existing generators are using these
schemes; however, the new generators may design new configurations, which
shall be acceptable by DNO after evaluation of the prevailing system
conditions.
CC 7.4 Connection Requirements on Alternating Current (AC) Generators
CC 7.4.1 Frequency and Voltage Control
Each Generator’s generating unit must be capable of contributing to frequency
and voltage control of the NGC’s Transmission System or a connected TNO
system, by continuous modulation of Active Power and Reactive Power
output. Therefore, to achieve this requirement it shall require that: (a) Each
Generating Unit must be fitted with a fast acting, proportional speed governor,
and a unit load controller or equivalent control device to provide frequency
regulation under normal operating conditions; and (b) The generating unit must
ensure that a continuously acting automatic excitation control system is
provided to manage constant terminal voltage control of the Generating Unit
without instability over the entire operating range of the Generating Unit. The
requirements for excitation control facilities shall be included in the Connection
Agreement.
Reactive Power Supply and Voltage Regulation
The Generators shall maintain a network voltage or reactive power output as
required by the System Operator within the reactive capability of the
Generators by use of an Automatic Voltage Regulator (AVR).
CC 86
DISTRIBUTION CODE
Frequency Requirement
It shall be necessary for each Embedded Generator to notify the DNO if its
Generating Unit has a restart capability without support from an external power
supply. Or otherwise, the generator will provide the Black start facility if
CC 87
DISTRIBUTION CODE
required/identified by SO under GC.
CC 7.4.5 Data Requirements
The Applicant shall provide the following data with the Intention Application.
The Applicant shall also provide a Single Line Diagram of the proposed facility
which must indicate all the current carrying parts/equipment connectedat all the
voltage levels of the proposed substation.
a. Names of the substation and its operating voltage
b. Connection of the Operators Network and Generators
c. Metering arrangement
d. Protection arrangement
e. Make of the equipment
f. If double busbar is being operated by splitting, it shall be indicated
accordingly
g. Any other useful information not listed above.
Equipment Data
Circuit Parameters:
a. Rated voltage (kV)
b. Operating voltage (kV)
c. Positive phase sequence reactance
d. Positive phase sequence resistance
e. Positive phase sequence susceptance
f. Zero phase sequence reactance (both self and mutual)
g. Zero phase sequence resistance (both self and mutual)
h. Zero phase sequence susceptance (both self and mutual)
Transformers
a. Rated MVA
b. Voltage Ratio
c. Winding arrangement
d. Positive sequence reactance
e. Max, min, and nominal tap positions
f. Positive sequence resistance
g. (max, min, and nominal tap)
h. Zero sequence reactance
i. Tap changer range
j. Tap change step size
k. Tap changer type: on load or off circuit
l. Earthing method: Direct, resistance or reactance
m. Impedance (if not directly earthed)
n. Phase connection.
Switchgear
b. Switchgear. For all circuit breakers: Rated voltage (kV)
c. Operating voltage (kV)
i. Rated 3-phase rms short-circuit breaking current, (kA)
ii. Rated 1-phase rms short-circuit breaking current, (kA)
iii. Rated 3-phase peak short-circuit making current, (kA)
iv. Rated 1-phase peak short-circuit making current, (kA)
v. Rated rms continuous current (A)DC time constant applied at
testing of asymmetrical breaking abilities (secs.)
Generating Unit Data
CC 88
DISTRIBUTION CODE
a. Rated terminal volts (kV)
b. Rated MVA
c. Rated MW
d. Dependable Capacity MW
e. Minimum Generation MW
f. Short circuit ratio
g. Direct axis synchronous reactance
h. Direct axis transient reactance
i. Direct axis sub-transient reactance
j. Direct axis short-circuit transient time constant.
k. Direct axis short-circuit sub-transient time constant.
l. Quadrature axis synchronous reactance.
m. Quadrature axis sub-transient reactance.
n. Quadrature axis short-circuit sub-transient time constant.
o. Stator time constant.
p. Stator leakage reactance.
q. Armature winding direct-current resistance.
r. Maximum Emergency Capability.
s. Installed Capacity.
t. Maximum action and reaction power output.
u. Type of generating plant (synchronous, asynchronous etc).
v. Type of prime movers
w. Operating regime of generator in continuous intermittent, peak lopping.
x. Fault Level contribution.
y. Method of voltage control.
z. Zero sequence
aa. Negative sequence
bb. Automatic voltage regulation.
cc. Speed governor and prime mover data.
dd. Capacity and stand by requirements.
ee. Auxiliary load of individual unit and powerhouse.
Interface Arrangements
a. The means of synchronization between the DNO and the User;
b. Details of arrangements for connecting with earth that part of the
Generator’s System directly connected to the DNO’s System;
c. The means of connection and disconnection which are to be employed;
and
d. Precautions to be taken to ensure the continuation of safe conditions
should any earthed neutral point of the Generator’s System operated at
HV become disconnected from earth.
More or less detailed information than that contained above might need to be
provided, subject to the type and size of generation or the point at which
connection is to be made to the DNO’s System. This information shall need to
be provided by the Generator at the reasonable request of the DNO.
CC 7.5 Connection Requirements on SWE Generators
CC 7.5.1 Information Provision
SWE Embedded Generators should provide the appropriate signals (as
agreed by the DNO’s Control Centre) from the following list:
a. Wind speed (m/s) (for SWE Embedded Generators comprised of wind turbines)
CC 89
DISTRIBUTION CODE
b. Wind direction (degrees (0 = North)) (for SWE Embedded Generators comprised of wind
turbines)
c. Solar irradiance (W/m2) (for SWE Embedded Generators comprised of PV modules)
d. Percent of Plant in operation (%) (for all SWE Embedded Generators)
e. Available power estimation (MW) (for all SWE Embedded Generators)
Short circuit contribution shall be provided for the SWE Embedded Generator
with all DC Embedded Generating Units in service.
CC 7.5.2 SWE Embedded Generator performance requirements during normal Voltage operating range
a. SWE Embedded Generators must remain connected for Voltage changes at the
Connection Point in the normal operating range.
b. The Active Power output under steady state conditions of any SWE Embedded
Generator should not be affected by Voltage changes in the normal Voltage operating
range.
CC 7.5.3 SWE Embedded Generator performance requirements during Voltage disturbances
a. SWE Embedded Generators shall be designed to withstand Voltage drops and peaks, as
illustrated in Figure 1.
b. Vmin and Vmax in Figure 1 correspond to the appropriate ranges, based on the
Connection Point rated Voltage.
c. The SWE Embedded Generator shall be able to withstand Voltage drops to zero,
measured at the Connection Point, for a minimum period of 0.15 seconds without
disconnecting, as shown in Figure 1.
d. The SWE Embedded Generator shall be able to withstand Voltage peaks with a
maximum Voltage of up to 120% of the nominal Voltage, measured at the Connection
Point, for a minimum period of 2 seconds without disconnecting, as shown in Figure 1.
e. Figure 1 shall apply to all types of faults (symmetrical and asymmetrical) and the bold
line shall represent the minimum Voltage of all the phases.
CC 90
DISTRIBUTION CODE
Figure 1: Voltage Fault Ride Through requirement for SWE Embedded Generators
(This figure and those following in this section are standard internationally acceptable requirements that all
major manufacturers comply with and are direct copies from the Grid Code.)
f. If the Voltage (V) reverts to the normal operating range during a fault sequence,
subsequent Voltage drops shall be regarded as a new fault condition. If several
successive fault sequences occur and the Voltage remains outside of the normal Voltage
operating range, the successive series of faults shall be considered to be one continuing
fault condition. In addition, desynchronisation of the Power Station from the Distribution
Network will be permitted if the operating point falls below the LVRT line to the
‘desynchronisation permitted’ area or above the HVRT line to the ‘desynchronisation
permitted’ area, as illustrated in Figure 1.
CC 91
DISTRIBUTION CODE
ΔV (per unit)
0.2
Vmax
0
Vmin
0.5
-1.0 -0.8 -0.6 -0.4 -0.2 0 0.2 0.4 0.6 0.8 1.0
Figure 2: Requirements for Reactive Power support, IQ, during Voltage drops or peaks at the DC
Embedded Generating Unit terminals
CC 7.5.4 Voltage support during grid faults (see Figure 2).
Note that due to the timescales involved, this requirement is applied at the DC
Embedded Generating Unit level. Therefore, this Subsection shall also apply
at the terminals of any additional dynamic Reactive Power Equipment which
may form part of the SWE Embedded Generator.
a. The DC Embedded Generating Unit shall have the capability of delivering an additional
reactive current in proportion to the Voltage change ∆V at its terminals, as illustrated in
Figure 2.
b. Vmin and Vmax in Figure 2 correspond to the appropriate ranges, based on the
Connection Point rated Voltage but applied to the DC Embedded Generating Unit
terminal Voltage.
c. The factor of proportionality between additional reactive current and Voltage deviation is
named K (∆IQ=K*∆V). The factor K must be settable in the range of 0<K<4.
d. The default setting for the K factor shall be 2 as shown in Figure 2.
CC 92
DISTRIBUTION CODE
e. The additional reactive current ∆IQ according to Figure 2 shall be injected in addition to
the pre-fault reactive current.
f. The Voltage deviation ∆V is defined as being the difference between the pre-fault
Voltage and the Voltage during the fault.
g. Both pre-fault current and pre-fault Voltage are defined by the 1-minute average of the
positive sequence component of the fundamental frequency value of current and
Voltage, respectively.
h. The post-fault Voltage on which basis the Voltage deviation ∆V is calculated is the
positive sequence component of the Voltage at the DC Embedded Generating Unit
terminals.
i. The additional reactive current shall be injected as a positive sequence component.
j. 60ms after fault inception, the additional current shall remain within a tolerance band of
±20% around the value according to Figure 2.
k. The absolute value of the current in each phase that is injected into the grid can be
limited to the rated current of the DC Embedded Generating Unit.
l. The reactive current requirement applies to retained Voltages (during the fault) greater
than 10%. Below 10% the current of the DC Embedded Generating Unit can be set to
zero.
m. As long as the DC Embedded Generating Unit operates below Vmin, reactive current
will have priority over active current, and active current should therefore be reduced if
required to meet the characteristic shown in Figure 2.
n. Upon the termination of a LVRT event, when Voltage is back into the normal operating
range, each DC Embedded Generating Unit shall restore Active Power to it at least 90%
of its pre-fault value within 1s.
o. During Voltage recovery, a DC Embedded Generating Unit must not absorb more
Reactive Power than prior to the fault (reference for pre-fault Reactive Power: 1-minute
average).
CC 7.5.5 Minimum requirements for Reactive Power capability for SWE Embedded Generators
a. A SWE Embedded Generator must have the capability of varying Reactive Power at the
Connection Point within the reactive capability limits defined by Figure 3 when the
Connection Point Voltage is at 1 per unit.
b. These Reactive Power limits will be reduced pro rata to the amount of Plant in service.
c. The SWE Embedded Generator shall be designed in such a way that the operating point
can lie anywhere within its maximum and minimum capability according to Figure 3.
d. The Reactive Power capability defined in Figure 3 is modified depending on the Voltage
at the Connection Point as per Figure 4. This requirement applies once automatic Tap
Changer(s) of the grid transformer(s) and / or any switched shunts in the SWE
Embedded Generator have operated. In the period(s) that the Automatic Tap Changer is
not functional the SWE Embedded Generator is required to reduce Active Power export
from the SWE Embedded Generator so that Reactive Power capability can be provided.
e. For Active Power levels below 5% of rated MW output (point C in Figure 3), there is no
Reactive Power capability requirement. In this range, it is required that the SWE
Embedded Generator operates within the tolerance range specified by point A and point
B in Figure 3. Point A is equivalent (in MVAr) to –5% of Rated Output and point B is
equivalent (in MVAr) to 5% of Rated Output. Note that if the SWE Embedded Generator
can provide full or partial Reactive Power Control capability down to zero Active Power
CC 93
DISTRIBUTION CODE
then it may do so without limitation provided that this capability allows operation at zero
MVAr exchange (unity power factor).
P / Pmax
1,0
PF=0,95 PF=0,975 PF=1 PF=0,975 PF=0,95
0,8
0,6
+
Inductive Capacitive
Q-import Q-export
0,4
0,2
C
0,0 A B
Figure 3: Reactive Power requirements at 1 per unit Voltage at the Connection Point for SWE Embedded
Generators
CC 94
DISTRIBUTION CODE
V
Vmax
Vn
Vmin
Figure 4: Variation of Reactive Power requirement for different Voltages at the Connection Point for SWE
Embedded Generators
CC 7.5.6 Reactive Power Control and Voltage Control Requirements for SWE Embedded Generators
a. The SWE Embedded Generator shall be equipped with Reactive Power Control
functions capable of controlling the Reactive Power supplied by the SWE Embedded
Generator at the Connection Point as well as a Voltage Control function capable of
contributing to Voltage support at the Connection Point via orders using set-points and
gradients.
b. The Reactive Power and Voltage Control functions are mutually exclusive, which means
that only one of the following three functions can be activated at a time:
i. Voltage Control
ii. Power Factor Control
iii. Reactive Power (Q) Control, including Q(P) Control
c. The control function and applied parameter settings for Reactive Power and Voltage
Control functions shall be determined by the DNO’s Control Centre and implemented by
the SWE Embedded Generator. The agreed control functions and initial parameters shall
be documented in the Connection Agreement.
d. Reactive Power (Q) Control, including Q(P) Control:
i. Q control is a control function controlling the Reactive Power supply and
absorption at the Connection Point, either independently of the Active Power and
the Voltage or in function of Active Power (Q(P) Control). This control function is
CC 95
DISTRIBUTION CODE
illustrated in Figure 5 as a vertical, red line (independent of Active Power) or as
the green line (in function of Active Power). The indicated Q(P) characteristic is
just an example. It is up to the DNO’s Control Centre to define the actual settings
of the Q(P) characteristic; however, it will always start with unity power factor (0
MVAr) at low power output.
ii. The SWE Embedded Generator shall be able to receive a Q setpoint with a
discrimination of at least 1kVAr.
iii. If the operating point of the SWE Embedded Generator deviates from the
characteristic in Figure 5 the automatic control system should act to restore the
operating point onto the characteristic within the following timescales:
1. Response from inverter-based Plant should commence within 0.5 seconds
2. All transformer and shunt tapping (where applicable) should be completed, and
the operating point should be settled onto the characteristic within 2 minutes.
Figure 5: Reactive Power Control functions for the SWE Embedded Generator
e. Power Factor Control:
i. Power Factor Control is a control function controlling the Reactive Power to
maintain a constant power factor at the Connection Point as shown by the blue
line in Figure 5.
ii. If the operating point of the SWE Embedded Generator deviates from the
characteristic in Figure 5 the automatic control system should act to restore the
operating point onto the characteristic within the following timescales:
1. Response from inverter-based Plant should commence within 1 second
2. All transformer and shunt tapping (where applicable) should be completed, and
CC 96
DISTRIBUTION CODE
the operating point should be settled onto the characteristic within 2 minutes.
f. Voltage Droop Control:
i. Voltage Droop Control is a control function which helps to control the Voltage at
the Connection Point based on a target and slope (droop) approach.
ii. The individual SWE Embedded Generator shall be able to perform the control
within its dynamic range and Voltage limit with the droop configured as shown in
Figure 6. In this context, droop is percentage change in Voltage from the Voltage
setpoint which will cause a change in Reactive Power exchange from zero to
Qmax or zero to Qmin as appropriate.
iii. If the operating point of the SWE Embedded Generator deviates from the
characteristic in Figure 6 the automatic control system should act to restore the
operating point onto the characteristic within the following timescales:
1. Response from inverter-based Plant should commence within 1 second
2. All transformer and shunt tapping (where applicable) should be completed, and
the operating point should be settled onto the characteristic within 2 minutes.
g. When the Voltage Control has reached the SWE Embedded Generator’s dynamic design
limits, the control function shall maintain this position (maximum or minimum reactive
current) and await possible overall control from the tap changer or other Voltage Control
functions.
CC 97
DISTRIBUTION CODE
a. All SWE Embedded Generators should be capable of setting an Active Power
curtailment setpoint given in MW to limit Active Power following receipt of an instruction
from the DNO’s Control Centre.
b. Following an instruction to set an Active Power curtailment setpoint the SWE Embedded
Generator should begin to respond to the new setpoint within 2 minutes.
c. The SWE Embedded Generator should ramp to the new Active Power curtailment
setpoint at the ramp rate agreed with the DNO’s Control Centre.
d. Any Active Power curtailment setpoint shall apply until such times as the DNO’s Control
Centre releases the Active Power curtailment setpoint. For the avoidance of doubt,
should the Active Power of the SWE Embedded Generator decrease below the Active
Power curtailment set point, the Active Power curtailment setpoint will still apply as a
maximum limit until released by the DNO’s Control Centre.
CC 7.5 8 High Frequency Active Power reduction requirement for SWE Embedded Generators
a. During excessive high frequency operating conditions, SWE Embedded Generators shall
be able to provide the mandatory Active Power reduction requirement in accordance with
Figure 7 in order to assist with stabilisation of the frequency.
b. When the frequency on the System exceeds 50.5 Hz, the SWE Embedded Generator
shall reduce the Active Power as a function of the change in frequency as illustrated in
Figure 7.
c. If the frequency reaches 51.75 Hz the SWE Embedded Generator output should reduce
to zero.
d. The required reduction in Active Power output should commence within 2 seconds of the
frequency exceeding 50.5 Hz and be continuously and linearly proportional, as far as is
practicable to the characteristic in Figure 7.
100
80
60
40
20
0
48.5 49 49.5 50 50.5 51 51.5 52 52.5
System frequency [Hz)
51.75 Hz
Regarding inspection and testing of equipment and the facilities of the Users,
the following procedures are to be followed:
CC 99
DISTRIBUTION CODE
requirements set out for the connection by the DNO as per this sub-code
or Connection Agreement.
e. Must provide generation availability forecast information including the
amounts of output, partial shutdowns, any de-ratings, and outages (MW
& MVAR both), to the relevant DNO.
f. The Generators must provide their development programs to the
relevant DNO so that the transmission or distribution facilities can be
upgraded in a timely manner, if required for, evacuation of power from
the Generator’s facilities.
g. Permit and participate in inspection and testing of facilities and
equipment prior to commissioning.
h. Must participate in frequency and voltage control, stability requirements
and short circuit requirements as specified in the Grid Code or
Distribution Code.
i. Even if contractually permitted to self-dispatch the Generator must obey
all instructions from the System Operator, given through the Power
Control Centre of the DNO, in emergency circumstances.
j. Must maintain requisite functional protection facilities accurate metering
facilities, testing, inspection, and repairs at all times.
CC 100
DISTRIBUTION CODE
CONNECTION PROCEDURE
for new connection or amendment
of existing connection
CC 101
DISTRIBUTION CODE
DISCO APPLICANT
Prepare Intention
Application
Submit Intention
Application along with
Provisional Review
applicable documents
Estimate
Internal
Approvals
Negotiation Negotiation
Connection Connection
Agreement Agreement
Make a
Connection
CC 102
DISTRIBUTION CODE
Scheme 1
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
DNO's
Substation
Generator Substation
CC 103
DISTRIBUTION CODE
SYSTEM CONSTRUCTION CODE
CONTENT
SC 104
DISTRIBUTION CODE
SC 2 CONSTRUCTION GUIDELINES
Following instructions are provided on construction practices as guidelines to
form contents and level of details required for the operating / construction
manual to be prepared by the DNO's
SC 105
DISTRIBUTION CODE
SC 2.1 Overhead Distribution Lines
The overhead distribution lines shall be designed in accordance with
applicable international standards, e.g. IEC.
SC 2.2 Wiring on Consumer’s Premises
The service Wires to Consumers shall be installed in accordance with relevant
Construction Standards for 230V/400V supply and in accordance with the
Distribution Service Manual.
SC 2.3 Underground Installations
Direct buried cable or conduit or other raceways installed shall meet the
minimum depth or height or clearances requirements of international
standards e.g. NESC. All underground installations shall be grounded in
accordance with the DNOs approved standards based on relevant
international standards like IEC60364, BS7671, and NESC. Underground
cable installed within a building like for example a consumer substation shall
be routed through proper raceway/trench.
SC 2.3.1 Protection from Damage
All underground cables should be laid down in proper trenches up to required
length or direct buried with standard depth and as per DNOs approved
standard procedure based on relevant international standards like IEC 60364,
BS 7671 etc.
SC 2.3.2 Backfill
Backfill containing large rock, paving materials, cinders, large or sharply
angular substance, or corrosive material shall not be placed in an excavation
where materials may damage cables or other substructures or prevent
adequate compaction of fill or contribute to corrosion of such structures. When
necessary to prevent physical damage to the cables, structures, protection
should be provided in the form of appropriate means.
SC 2.3.3 Sealing of Entry Points
All the entry points of cables to a building or substation shall be properly sealed
to avoid ingress of water or rodent entry.
SC 3 CONSTRUCTIONAL IMPROVEMENTS
The system can be improved by providing the following construction criteria
by the DNO.
SC 3.1 Foundation of the Poles/Structure
Foundations shall be designed considering the nature of soil/salinity in the
area. Concrete foundations of sulphate resistive cement shall be provided
wherever necessary and required.
SC 3.2 Insulators
In areas where air borne dust/salts are deposited on insulators during fog and
forms contamination double disc insulators sh all b e use d in the
construction design in such areas.
SC 3.3 Line Connectors
Line connectors must be installed properly so as not to result in loose joints or
cause flashovers, broken conductors, and severe line losses. The DNO must
use parallel grove type connectors (PG) and follow installation instructions to
SC 106
DISTRIBUTION CODE
assure proper installation. The instructions shall indicate wire brushing of the
conductors, adding an oxide compound to conductor surface, and proper
tightening of the bolts.
Use of compression type connectors shall be promoted. Hand Compression
Tools shall be used to affix these connectors.
Insulation Piercing Connectors (IPCs) for covered conductor and LT ABC shall
be used.
SC 3.4 Transformer Connections
a. DNO shall develop construction standards that provide for the best
connections to primary and secondary conductors.
b. The DNO shall incorporate the following in its construction design
standards:
i. Use of Wasp conductor/copper conductor Jumpers for
transformers up to capacity of 100 kVA.
ii. Use of double WASP Conductor jumpers for 200 kVA
Transformer.
iii. Use of P.G. connectors for joining the jumpers to line.
iv. Use of special compression lugs/Thimbles to join the jumpers
to transformer bushings.
v. Lead sizes shall be standardized by DISCO as per transformer
rating.
vi. Thumb clamp shall be used at transformer bushing for
connection of leads with bushing instead of directly connecting
lugs with bushing.
The DNO shall specify that distribution transformers are provided with lugs on
transformers bushings.
Transformer shall be protected at its LT and HT side using overcurrent
protection devices. Additional protections like pressure relief device may be
added in specification of DNO.
SC 3.5 Proper Construction Techniques
Construction of Distribution network shall be conducted using proper
construction techniques. Use of sag/span chart, tension meter, stay wire 45
deg angle, crimping machine, torque wrench and trolley for ABC pulling and
electrical grease application are some of quality methods for construction.;
Techniques includ.
The use of shovel for structure pit digging and auger for PCC poles.
The use of Rollers on every pole for Stringing of Conductors.
The use of Sag Charts and Tension Meters for proper sags.
Stay wire shall be affixed to the pole at a 45-degree angle to provide the
maximum strength to the pole or at appropriate angle depending upon the site
location, and condition.
SC 3.6 Affixing of Hardware
The pole framing to install Hardware, Cross arms, Insulators shall be affixed
to the pole while it is still lying on ground and then erect it, so that labour time
can be saved.
Pole shall be erected 1st adopting all the safety measures and subsequently
SC 107
DISTRIBUTION CODE
hardware installation may be carried out.
The DNO Engineer shall prepare a site plan, stating the requirement of
shutdowns, transport, Tools and Plant, work force and the material needed
for the job and shall arrange them before starting work atsite.
End of SC
SC 108
DISTRIBUTION CODE
CONTENTS
SPR 109
DISTRIBUTION CODE
SYSTEM PERFORMANCE, RELIABILITY AND
CONSUMER SERVICE REQUIREMENTS
SPR 110
DISTRIBUTION CODE
b. One transformer towards the end of the feeder
The load on each phase shall be kept equal to the maximum possible extent.
• Voltage Imbalance
o Unbalance caused by individual loads should be kept within
a reasonable range.
• Voltage Fluctuation
o A 3% general limit on the allowable magnitude of voltage
changes, regardless of shape.
• Harmonics
o IEEE 519 shall be used as the applicable standard.
Improvement to voltage conditions can be achieved by but not limited to the
following action: -
a. Providing proper earthing of the transformer. Proper earth connection
may result in proper voltage at Consumer premises.
b. The load on the LT feeders must be kept balanced as far as possible -
unbalanced loads cause heavy voltage drops in the overloaded phases.
The unbalanced load on the Low Voltage side of the Distribution
transformers shall not exceed 10% of the peak load.
c. Adjusting/shifting Consumers on adjacent transformers to reduce the
length of LT radial line from the transformer as for as possible.
d. To bring in circuit all fixed disconnected 11kV capacitors installed on
the feeders.
e. By bifurcating the existing 11kV feeders.
f. By augmenting the existing 11kV conductor.
g. By providing 11kV voltage regulators on the feeders.
SPR 111
DISTRIBUTION CODE
SPR 112
DISTRIBUTION CODE
The Disco shall set timelines for all User outage planning request submission
and consequent PCC approval, so as to allow the PCC to fulfil its outage
submission duties to the SO.
From time to time, but not less than once every three years, the System
Operator shall schedule a test of the system restoration plan and DNO shall
co-operate and participate in the exercise.
In the event of breakdown within its own System, the DNO shall
restore/maintain supply by taking appropriate pre-specified measures within a
pre-specified time.
End of SPR
SPR 113
DISTRIBUTION CODE
METERING A N D D A T A C O L L E C T I O N
CONTENT
MDC-115
MDC 1 INTRODUCTION
MDC 114
DISTRIBUTION CODE
MDC 1 INTRODUCTION
This sub-code defines conditions/obligations and operational responsibilities
for efficient commercial metering and data collection at the points of
connection between DNO’s network and User’s system (including generators).
MDC 2 PURPOSE
This section specifies the minimum technical, design, operational and
performance criteria for revenue metering, for the purpose of electricity sales
and flow, which must be complied with by all the DNOs, and Users connected
to or seeking connection with the network of the DNO.
For the purpose of settlement the electric energy (active and reactive) supplied
and delivered at each defined connection point (Common Delivery Point) must
be measured and recorded through metering equipment of the required
specifications as described in this sub-code, Distribution Service Manual or
Grid Code, which shall be installed, operated, and maintained according to this
code.
MDC 115
DISTRIBUTION CODE
• The meter installation must be set up to allow remote access by
standard protocols.
• Data collection will be by secure means.
MDC 116
DISTRIBUTION CODE
requirements of the MCC and/or any other applicable regulation.
c. Time synchronization of meters
d. Meter display parameters
e. Sign conventions
MDC 6.4. Data Communications
MDC 6.4.1 Meters shall be equipped with standard communications ports/modules for
local and remote downloading of Load Profile and other Metering Data.
MDC 6.4.2 Both the Primary and Back-up Energy meters shall be integrated in the AMI
System of MSP. The relevant User shall be provided with read-only indirect
access of Metering Data for its Primary and Back-up Meters.
MDC 6.4.3 The communication protocol for transmitting Metering Data shall be in
accordance with IEC 61107, IEC 62056 (DLMS/COSEM/UDIL specifications),
or IEC 61850.
MDC 6.4.4 Provided energy meter shall be capable of integration with the MDM Server of
MSP. All the necessary communication modules required for this integration
shall be provided by User.
MDC 6.4.5 Remote communication option shall be provided by means of suitable
communication medium as deemed appropriate by MSP while adhering to
security guidelines as set out in MC 4.6.
MDC 6.5. Metering Data Storage
MDC 6.5.1 MSP shall maintain record of Metering Data in MDM server for three (3) years.
Metering Data shall be maintained with a back-up arrangement.
MDC 6.5.2 The stored Metering Data values shall be in kilowatt (kW) and kilowatt-hour
(kWh) for power and energy respectively.
MDC 6.5.3 In the event of a power supply failure, the meters shall protect all data stored
up to the time of the failure and maintain the time accuracy. To cater for
continuous supply failures, the clock, calendar and all data shall be retained in
meters for a period of at least twenty-four (24) months without an external
supply connected.
MDC 6.5.4 Uninterrupted auxiliary supply should be provided to meters and
communication devices for metering and continuous transmission of data.
MDC 6.5.5 A “read” action shall not delete or alter any stored Metering Data in the meter
and MDM.
MDC 6.6 Meter Time Synchronization
MDC 6.6.1 Time of Metering System shall be kept synchronized as per Pakistan Standard
Time (PST).
MDC 6.6.2 Time synchronization of meters shall be performed as per MSP operating
procedures and consequently, appropriate measures shall be taken to ensure
the accuracy of the time-stamped Metering Data.
MDC 6.7 Sharing of Metering Data
MDC 6.7.1 The MSP shall share relevant Metering Data with the following:
a. The MO for performing billing and settlement activities;
b. The SO, required for operational monitoring;
MDC 117
DISTRIBUTION CODE
c. The involved User, to fulfil their own obligations.
MDC 6.7.2 MSP shall keep the Metering Data confidential to avoid unauthorized access
by any entity.
MDC 6.8 Metering Data Validation, Estimation, and Editing (VEE)
The Metering Data – that will be transferred to the MO – shall be complete,
correct and its type, format and Frequency shall be in accordance with the
Market Commercial Code. For such purpose, the MSP shall follow the
provisions of the Market Commercial Code and its associated CCOPs.
MDC 6.9 Technical Disputes in Metering Data
MDC 6.9.1 MSP shall resolve errors/omissions in Metering Data (as a result of metering
system error or malfunction), if any, in collaboration with the relevant Users
and the adjusted/corrected Metering Data shall be reported to the MO and the
relevant Users.
MDC 6.9.2 In case MSP and the relevant Users do not reach an agreement, the Dispute
Resolution Procedure provided in the Market Commercial Code shall be
followed.
MDC 118
DISTRIBUTION CODE
MC 7.1.7 In case of tampering with Metering System, MSP shall perform audit/enquiry
of User’s Metering System to ascertain if the tampering is deliberate or
inadvertent and the duration of such tampering. If the tampering of Metering
System is proven to be deliberate, a complaint will be lodged by MSP with the
Authority and the appropriate law enforcement agency for investigation and/or
punitive actions as per law of the country, if any.
If the MSP detects any anomaly, including maintenance defects, inappropriate
equipment, or evidence of tampering, thereof, it shall prepare a Metering
Incident Report, informing this situation to the Market Operator as per the
provisions of the Market Commercial Code.
MDC 8 APPLICATION
Metering shall provide accurate measurement of electrical quantitiesdelivered
to or received from the electric transmission, transmission, and distribution
network. Metering devices including all instrument transformers shall be
revenue class with facilities for measuring, active and reactive energies, peak
load, 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 DNO computer centre and MSP (if applicable).
Metering facility shall be provided at the connection points between Users
and DNO to record energy (kWh) delivered or consumed for the purpose of
billing, engineering studies and planning. Metering shall provide
measurements of energy delivered at the point of connections between the
Generators and other Users. Metering data shall be made available to each
User.
The DNO or MSP shall make all meter data available to the User.
MDC 119
DISTRIBUTION CODE
MDC 10 STANDARDS
All metering devices and instrument transformers for metering shall comply
with the latest applicable international and local standards. Accuracy (energy
and demand). Reference “applicable IEC specifications” (Class 0.5, 1 and 2
Alternating Current watt-hour meters) No. I85 (Current transformers), No. 186
(Voltage Transformers), “applicable IEC specifications” (Measuring Relays
and Protection Equipment).
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 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 carriersignalling.
• IEC 62056-41 Electricity metering – Data exchange for meter reading,
tariff, and load control – Part 41: Data exchange using
wide area networks: Public Switched
Telephone Network with
LINK+ protocol.
• IEC 62056-51 Electricity metering – Data exchange for meter reading,
tariff, and load control – Part 51: Application layer
protocol.
• IEC 60186 Voltage transformers
• IEC 62052-11 Electricity metering equipment - General requirements, tests
and test conditions - Part 11: Metering equipment
• IEC 62053-21 Electricity metering equipment - Particular requirements - Part 21:
Static meters for AC active energy (classes 0,5, 1 and 2
• IEC 62053-22 Electricity metering equipment - Particular requirements - Part 22:
Static meters for AC active energy (classes 0,1S, 0,2S and 0,5S)
• The meter shall have the capability of recording active and reactive
energy and maximum demand for the entire billing period. The meter
billing period shall be programmable and can be programmed to
automatically store the accumulated value and reset the counter for the
next billing period.
MDC 120
DISTRIBUTION CODE
• Multiplier corresponding to the combination of CT and PT ratios shall be
programmable in the meter. Accuracy class of CT and PT shall be in
accordance with applicable DNOs technical specifications.
a) Installation
Installation of revenue meter and ancillary equipment at the substation
for the point of connection shall be the Generator and other Users’
responsibility. The Generators and other User connecting to the DNO's
network shall submit to the DNO for approval theengineering design
for revenue metering, proposed location of metering equipment and
ancillaries complete with wiring and installation drawings and bill of
materials. The proposed metering location shall be adjacent to any
telemetering, communication, and datalogging equipment.
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. 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.
b) Access
Each User shall grant the DNO and the MSP 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 of obligation under
this Code.
The right of access provided for under this code includes the right to
bring on to such User property such vehicles, plant machinery and
maintenance or other materials as shall be necessary for the purpose
of performance of obligation under this Code.
Each User shall procure 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.
c) Telemetering (Data Collection System)
Facilities are to be provided by the User for remote transmission of
metering information to the DNO to be recorded in the metering
MDC 121
DISTRIBUTION CODE
database. Transmission of telemetered data information must be
secure and reliable and not prone to tempering. All metered quantities
including times and date of acquisition must be telemetered. Quantities
that are to be metered shall include:
• Apparent energy
• Real energy
• Energy (kWh or MWh) delivered to load
• Energy (kWh or MWh) received from supply
• Reactive energy (kVArh or MVArh)
• Peak load MW or kW
• Peak MVAr or kVAr load
• Power Factor.
MDC 122
DISTRIBUTION CODE
PROTECTION REQUIREMENTS
CONTENT
PR 1 PROTECTION SYSTEM PRACTICES AND
SYSTEM CO-ORDINATION PR-124
PR 123
DISTRIBUTION CODE
PROTECTION REQUIREMENTS
The protection relays shall be in accordance with the IEC Standard No. 255,
and IEC 60255 (Protective Relays)
PR 5 SUBSTATION PROTECTION
The time setting for clearing a fault by any relay operating a breaker should
be provided by the DNO and coordinated with NGC or connected TNO.
Connections between the DNO and the transmission network of NGC or a
connected TNO system, and other Users (Distribution Companies, BPC,
TNOs, generators (Embedded and Consumer’s-owned) substations must
meet the minimum requirements delineated below:
a. For faults on the User’s substation equipment directly connected to
the network of the DNO and for faults on the network of the DNO
directly connected to the User’s substation equipment, fault clearance
period from fault inception to circuit breaker arc extinction duly co-
ordinated with the NGC or connected TNO shall be set out in the
Transmission Service or Connection Agreement duly coordinated with
the System Operator.
b. All fault clearing times shall be specified by the DNO and approved by
NGC or connected TNO except for the transmission connection point
where NGC or connected TNO is required to specify.
c. In the event the primary or main protection system fails to meet the
fault clearance times listed above, a backup or secondary protection
system shall be provided. Back-up protection shall be coordinated
with the primary protection so as to provide discrimination.
d. Circuit breakers provided at the point of connection between the
User's substation and the transmission network shall be provided with
breaker failure protection. In the event the breaker fails to operate, the
breaker failure protection will initiate tripping of all the electrically
adjacent circuit breakers within the time limit approved by the System
Operator.
Additional protection may be required by NGC or connected TNO as per the
provisions of the Grid Code.
End of PR
PR 127
DISTRIBUTION CODE
SYSTEM MAINTENANCE AND TESTING
CONTENT
SMT 128
DISTRIBUTION CODE
The training shall incorporate but not limited to the following procedures and
techniques.
SMT 129
DISTRIBUTION CODE
a. Lines
• Distribution Transformers
• Oil Dielectric Testing
• Insulation Testing
• These should be done at least every five years.
SMT 130
DISTRIBUTION CODE
e. Safety
Awareness and implementation of safety code management.
SMT 132
DISTRIBUTION CODE
SAFETY REQUIREMENTS
CONTENTS
SR 1 INTRODUCTION SR-134
SR 2 OBJECTIVES SR-134
SR 3 SCOPE SR-134
SR 5 PROCEDURES SR-135
SR 133
DISTRIBUTION CODE
SAFETY REQUIREMENTS
SR 1 INTRODUCTION
The DNO shall abide by the Safety Requirements of NEPRA HSE Code for
Licensees, 2021”. (Currently Draft 2nd Edition published). This code presents
safety instructions for the electrical works concerningconstruction, installation,
operation and maintenance of electric supply lines and grid station facilities.
The DNO shall also abide by the Safety requirements as per NEPRA
Regulation of Generation, Transmission and Distribution of Electric Power Act
(XL of 1997), and safety standards established in the Distribution Service
Manual, Consumer Eligibility Criteria andDistribution Performance Standards
Rules.
SR 2 OBJECTIVES
To lay down the safety management criteria to be applied to ensure safety of
persons working on the Distribution System and at or across operational and
Ownership Boundaries, general public and animals.
SR 3 SCOPE
Each DNO shall develop its Safety Manual in accordance with the requirements
of the NEPRA HSE Code for Licensees, 2021”. (Currently Draft 2nd Edition
published).
Similar Criteria and Standards of Safety Management Systems shall be
provided by other Users of the Distribution System and approved by the DNO
when carrying out work or tests at the operational interface with the DNO. If
these are not provided the DNO standards shall apply.
b. A DNO shall ensure that its distribution facilities do not cause any leakage of
Electrical Current or Step Potential beyond a level that can cause harm to
human life, as laid down in the relevant IEEE/IEC Standards; prevent
accessibility of live conductors or equipment; and prevent development of a
situation due to breakdown of equipment which results in voltage or leakage
current that can cause harm to human life, property and general public
including without limitation, employees and property of the DNO.
c. A DNO shall implement suitable, necessary, and appropriate rules, regulations
and working practices, as outlined in its Distribution Code or applicable
documents, to ensure the safety of its staff and members of the public. This
shall also include suitable training for familiarity and understanding of the rules,
regulations, practices, and training to use any special equipment that may be
required for such purposes including without limitation basic first aid training.
The Safety Management criteria that apply to the DNO and the followingUsers
of the Distribution System:
SR 134
DISTRIBUTION CODE
a. Embedded Generators.
b. Bulk Power Consumers
c. Other DNOs
d. SHYDO
e. Any other party reasonably specified by the DNO including Users
connected at Distribution Voltages for appropriate sections when
necessary.
f. Agents of the DNO or Users working on the Distribution System or at or
across operational boundaries.
SR 5 PROCEDURES
The Safety Manual will present the principles, guidelines, and procedures
(Safety Management System) for ensuring safety of all relevant personnel of
the DNO and Users for work on their respective Systems or Plant or Apparatus
connected to them.
There shall be joint agreement by the DNO and Users on which Safety
Management System is to be used for sites or locations where an Operational
Boundary exists and proper documentation of the safety precautions to be
taken shall be maintained.
There shall be written authorization of personnel who do the work of control,
operation, work or testing of Plant or Apparatus forming part of or connected to
the Distribution System of the DNO.
There shall be joint agreement between the DNO and Users which specifies
responsibility for system or control equipment which shall ensure that only one
party is responsible for any item of plant or apparatus at any one time.
The DNO and each User shall at all times have nominated a person or persons
responsible for the co-ordination of safety on the respective systems.
The DNO and each User shall maintain a suitable system of documentation
which records all relevant operational events that have taken place on the
Distribution System or other System connected to it and the co- ordination of
relevant safety precautions for work.
System diagrams which show sufficient information for control personnel to
carry out their duties shall be exchanged between the DNO and User as
required.
SR 135
DISTRIBUTION CODE
person at any one time.
d. Adequate means of isolation shall be provided at the interface to allow
work to be carried out safely at either side of the interface.
e. Where necessary to prevent danger adequate facilities for earthing shall
be provided at either side of the interface to allow work to be carried out
safely at the interface or at either side of the interface.
f. Adequate working space, adequate means of access where necessary,
adequate lighting shall be provided at all electrical equipment on or near
which work is being done in circumstances, which may cause danger.
g. All electrical equipment shall be suitably identified and tagged where
necessary to prevent danger.
h. Electrical installations and equipment shall comply with the relevant
requirements as set down in the Power Safety Code.
i. safety protocols to be followed while working at height.
j. Communication plan to be established to avoid incorrect / inadequate
information and to communicate right and clear information to right
people at right time to control and monitor operational and HSE critical
activities.
k. Risk assessment of each activity to be conducted to reduce risk to as
low as reasonably practicable.
l. Personal protective equipment (PPE) shall be provided in accordance
to Hazard/Risk category to provide protection.
m. Permit to work system to be adopted while carrying out maintenance
activities.
n. Minimum safety requirement for scaffolds to be followed.
o. Entry of unauthorized visitor and vehicle to the restricted/operational
area to be controlled.
SR 136
DISTRIBUTION CODE
Consumers’ premises unless it is positively known ‘that such action
does not conflict with the Consumers’ rules, wishes and safety.
f. Walks, aisles, stairways, fire escapes and all other passageways shall
be kept clear of all obstructions.
g. Any floor or wall opening shall be guarded with standard railings and toe
boards. Other means of temporary protection may be used only with an
observer present.
h. Tools and plant shall not be placed where they may cause tripping or
stumbling hazards, or where they may fall and strike anyone below.
i. Adequate measures shall be taken as per hierarchy of controls to
overcome slipping hazards,which may exist.
j. Nails in boards, such as those removed from scaffolds, forms and
packing boxes shall be removed. The boards shall be carefully stacked
or stored.
k. Nails that have been driven into barrels or tins to secure the head shall
be removed when the head is removed.
l. Work areas and vehicles shall be neat and orderly at all times.
m. Separate dust bins shall be provided and used for broken glass,
insulators, sheet metal scraps, used pressurized containers and other
waste material for segregation of waste at source end.
n. HSE signs to be pasted at work areas & prominent locations as an
administrative control to give awareness to staff & public regarding
specific hazards.
o. Hierarchy of controls to be adopted to reduce risk at an ALARP level.
SR 137
DISTRIBUTION CODE
PUBLIC LIGHTING
CONTENT
PL 138
DISTRIBUTION CODE
PUBLIC LIGHTING
PL 1.1 The DNO shall provide distribution facilities for public lighting within its
distribution territory. Maintenance/operation and replacement of lamps/fixtures
shall be carried out by the DNO at mutually agreed terms and conditions with
the relevant local body desirous of establishing a public lighting system.
PL 1.2 Construction of the public lighting in the territory of the DNO shall also be
governed under a mutual agreement between the DNO and the relevant local
body. Civic agencies to ensure intimation to DNO for such development in
due time.
End of PL
PL 139
DISTRIBUTION CODE
EMERGENCY PLANS AND LOAD SHEDDING
CONTENTS
EPL 140
DISTRIBUTION CODE
General Comments
It is important to lay down the principles and priorities of load shedding and
detailed procedures as to how the load shedding shall be carried by the DNO
under the instructions of the System Operator. This section needs to be
consistent with Performance Standards (Distribution), Grid Code, and
TransmissionPerformance Standards.
The Network Load Management actions should treat all Consumers equally
independent of who supplies them. Where Commercial Load Management is
in place it should always be preferred, noting that large Consumers are more
likely to be interested in delivering this service and would often have an
independent supplier.
EPL 141
DISTRIBUTION CODE
shed the load in the following order:
End of EPL
EPL 142
DISTRIBUTION CODE
PROVISION OF INFORMATION
CONTENTS
PI 1 REQUIREMENTS PI-144
PI 4 CONFIDENTIALITY PI-144
Pi 5 NEW MARKET - CTBCM PI-144
PI 143
DISTRIBUTION CODE
PROVISION OF INFORMATION
PI 1 PROVISION OF INFORMATION
The DNO shall fulfil requirements related to but not limited to the
following:
a. DNO’s obligation to provide information on quality and tests made
or and when required by Consumer.
b. DNO’s obligation in providing technical information
PI 2 DNO'S OBLIGATIONS
DNO shall provide all necessary information to NEPRA as required under
current regulations and legislation.
PI 2.1 As a requirement of Distribution Licensing Rules - 1999 and the
distribution licence developed under such rules a DNO must provide a
summary of the DNO's and Consumers' rights and obligations in the form
of Distribution Service Manual and make such available to each of its
Consumer:
a. at the time the Consumer is connected;
b. on request; at least once every two years.
PI 2.2 When requested by a Consumer, the DNO must:
a. provide information on the reliability or quality of supply provided to
that Consumer as per the requirements of Performance Standards
(Distribution); and
b. provide a copy of the NEPRA Performance Standards (Distribution)
to the Consumer.
PI 4 CONFIDENTIALITY
A DNO must use all reasonable endeavours to keep confidential any
confidential information which comes into the possession or control of the
DNO or of which the DNO become aware of.
PI 5 NEW MARKET - CTBCM
The provision of information to the New Market should cover at least:
1) Registration of each CDP with a Supplier.
2) Hence registration of the CDP meter(s) with that Supplier.
3) Commercial metered energy data from CDPs.
PI 144
DISTRIBUTION CODE
4) Commercial metered energy data from generators connected
directly to its network.
5) Capacity contribution of each generator connected directly to its
network.
6) Distribution loss factor for each BPC CDP and generator CDP.
End of PI
PI 145
DISTRIBUTION CODE
DISTRIBUTION DATA REGISTRATION CODE
CONTENTS
DDRC 146
DISTRIBUTION CODE
b. NGC
c. Embedded Generators
d. SHYDO
e. BPCs
f. SPPs
g. AJK
DDRC 149
DISTRIBUTION CODE
CONTENTS
DOC 1 Appendix 1
LOAD FORECASTS – OPERATIONAL PLANNING PHASE
(8 weeks to 1 year ahead inclusive) S&A-145
DOC 1 Appendix 2
LOAD FORECASTS – PROGRAMMING PHASE
(24 hours to 8 weeks ahead inclusive) S&A-146
DOC 1 Appendix 3
LOAD FORECASTS – CONTROL PHASE
(0 to 24 hours ahead) S&A-147
DOC 2 Appendix 1
OUTAGE PLANNING
OPERATIONAL PLANNING PHASE
MEDIUM TERM PROGRAMME S&A-148
DOC 2 Appendix 2
OUTAGE PLANNING
OPERATIONAL PLANNING PHASE
SHORT TERM PROGRAMME S&A-149
DOC-5 Appendix-I
Matters, if Applicable to the Significant Incident,
to be included in a Written Report Given in
Accordance with DOC 5.2.2 S&A-150
DPC Appendix-I
SHUNT CAPACITOR INSTALLATION
(Useful Formula) S&A-151
DDC Appendix-I
KVA-KM LOADING
(Sample Calculations) S&A-152
PR Appendix-I
Publications found with ICS code. S&A-153
S&A 150
DISTRIBUTION CODE
S&A 151
DISTRIBUTION CODE
DOC-1
APPENDIX-1
S&A 152
DISTRIBUTION CODE
DOC-1
APPENDIX-2
The following information shall be provided to the DNO in the time scales
specified in DOC1:
(b) All the Bulk Power Consumers and other distribution companies
connected to the DNO's system shall intimate to the DNO the
specific date and time where the aggregate change in their load
due to their operation is expected to be more than 1 MW.
S&A 153
DISTRIBUTION CODE
DOC-1
APPENDIX-3
(a) Intimation by all the Bulk Power Consumer to the DNO the detail of
changes in the load if such changes are more than 1 MW.
S&A 154
DISTRIBUTION CODE
DOC-2
APPENDIX-1
155
OUTAGE PLANNING
S&A 155
DISTRIBUTION CODE
DOC-2
APPENDIX-2
OUTAGE PLANNING
S&A 156
DISTRIBUTION CODE
DOC-5
APPENDIX-I
Applicable to DNO:
(a) duration of incident and corrective actions taken;
(b) estimated date and time of return to normal service.
S&A 157
DISTRIBUTION CODE
DPC
APPENDIX-I
1. CAPACITOR REQUIRED
Where,
Where,
S&A 158
DISTRIBUTION CODE
DDC
APPENDIX-1
KVA-KM LOADING
(Sample Calculations)
1. CONDUCTOR DATA
* Appropriate values may be taken for any other temperature and equivalent spacing.
2. ASSUMPTIONS
3. REGULATION
Where
416.2 x (0.5449x0.8+0.421x0.60
x 100 = 4.44%
Percent Regulation =
For 1% Voltage Regulation the KVA-KM loading for the selected conductor size at
0.8 PF will be 1912 KVA-KM. For any other Power Factor, voltage, and conductor
temperature the Voltage Regulation may be calculated by substituting appropriate
values of current, Resistance Cos and Sine in the formula.
S&A 159
DISTRIBUTION CODE
PR
APPENDIX-I
Publications found with ICS code:
29.060.01 Electrical wires and cables in general
S&A 160
DISTRIBUTION CODE
S&A 161
DISTRIBUTION CODE
S&A 162
DISTRIBUTION CODE
S&A 163
DISTRIBUTION CODE
S&A 164
DISTRIBUTION CODE
S&A 165
DISTRIBUTION CODE
S&A 166
DISTRIBUTION CODE
S&A 167
DISTRIBUTION CODE
S&A 168
DISTRIBUTION CODE
S&A 169
DISTRIBUTION CODE
S&A 170
DISTRIBUTION CODE
S&A 171
DISTRIBUTION CODE
Insulators for overhead lines with a nominal voltage above 1000 V - Ceramic or glass
insulator units for a.c. systems - Characteristics of insulator units of the cap and pin type
S&A 172
DISTRIBUTION CODE
S&A 173
DISTRIBUTION CODE
S&A 174
DISTRIBUTION CODE
Distribution automation using distribution line carrier systems - Part 3: Mains signalling
requirements - Section 21: MV phase-to-phase isolated capacitive coupling device
S&A 175
DISTRIBUTION CODE
S&A 176
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 1
(k) Auxiliary Demand (MW) of the Power Station and each Unit
S&A 177
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 2
• Present capability in MW which a DNO can meet from other source of supply in caseof
an unplanned and planned outages.
S&A 178
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 3
LOAD CHARACTERISTICS
• Maximum and minimum demand and active and reactive power requirements.
• Details of load causing short term and long-term fluctuations on the DNO’s system.
S&A 179
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 4
(e) Hourly Active and Reactive power usage at the specific time of
DNO's Annual Peak and the System Operator's Annual Peak
and minimum system load at each transmission connection
point.
S&A 180
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 5
The following information shall be provided to the DNO in the time scales
specified in DOC1:
(e) Notification to the DNO by all its Bulk Power Consumers and
other Distribution Companies connected to the DNO system for
the specific time intervals where the aggregated change in the
load due to their operations is expected to be greater than 1MW.
S&A 181
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 6
(0 to 24 hours ahead)
S&A 182
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 7
OUTAGE PLANNING
S&A 183
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 8
184
OUTAGE PLANNING
S&A 184
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 9
185
GENERATING UNIT'S OUTAGES
Comprising information required by the DNO for outages on each generating unit
effecting the DNO's system operation and demand.
S&A 185
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 10
1860
Comprising information required by DNO for outages on the User’s system plants
and apparatus effecting the DNO’s System.
S&A 186
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 11
DOC 5 Appendix 1
S&A 188
DISTRIBUTION CODE
DDRC
SCHEDULE NO. 12
The DNO shall supply its Annual Performance Data as supplied to NEPRA under
Performance Standards (Distribution).
S&A 188
DISTRIBUTION CODE
The Terms Not included here have been Defined in Various Applicable Documents of
NEPRA and Grid Code.
1000 Watts = 1 kW
1000 kW = 1 MW
1000 MW = 1 GW
1000 GW = 1 TW
S&A 188
DISTRIBUTION CODE
society or association.
12. Commercial The commercial code prepared and maintained by the market
Code operator pursuant to sections 23A and 23B of the Act and
approved by the Authority, from time to time.
13. Commercial Where a Supplier may offer discounts to Consumers who agree
Load to be shed under specific, Supplier determined conditions.
Management
15. Common Points at the boundary between commercial entities where there
Delivery Points is Commercial Metering.
(CDP)
16. Connection An Agreement between a User and DNO setting out the terms
Agreement and conditions relating to a Connection to the Distribution
System.
18. Consumer with A Consumer with one or more generating units connected to the
Own Generation Consumer’s system, providing all or part of the Consumer’s
electricity requirements, and which may use the DNO’s
Distribution System for the transport of any surplus
of electricity being exported.
19. Consumption Is the use of electrical energy by a DNO or Bulk Power
Consumer, in a period of time previously established.
20. Continuity of Means providing electrical power services in an uninterrupted
Supply manner.
21. Control The process of managing the System Operator Transmission
System or a Distribution System or a User System in “real time”
by means of instructions issued verbally using the control
telephony or by means of SCADA systems. Control includes
monitoring as well as operating the networks.
S&A 188
DISTRIBUTION CODE
26. DCRP Operating The operating procedure under the D-Code by which the DCRP
Procedure or operates, covering its constitution, duties, operations, and
DCRP-OP timescales.
27. Discrimination The minimum time by which events must be separated such
that the sequence of their occurrence is determined correctly.
28. Distribution Code The distribution code prepared by the DNOs and approved by
the Authority.
29. Distribution “Financial Year” means a consecutive period of twelve calendar
Licensee Financial months commencing on the 1st day of July of any year and
Year ending on the 30th day of June of the following year.
30. Distribution An entity, which owns, operates, and maintains Distribution
Network Operator Facilities.
(DNO)
31. Distribution Service the manual of instructions developed by a DNO and approved by
Manual the Authority detailing instructions and guidance to the persons
connected or to be connected to the distribution system of the
licensee as more fully described in regulation 8 of the NEPRA
distribution licensing regulations.
32. Distribution Use of the charges made or levied or to be made or levied by a DNO for
System Charges the use of its distribution system for the purposes of the
(DUOS) distribution services but shall not include connection charges.
33. Distribution Voltages below 66kV.
Voltage(s)
34. Efficiency The ratio of active output power to active input power,
expressed per unit or as a percentage.
35. Embedded Having a direct electrical connection to a Distribution System.
36. Embedded Generating Units within a Power Station which are directly
Generator connected to a Distribution System and have no direct
Connection to the Transmission System. For the avoidance of
doubt this shall include Captive Generators.
37. Emergenc An instruction issued by the System Operator in emergency
y circumstances to its Users.
Instruction
s
38. Emergency Operating condition outside of the Normal Operation.
Operation
S&A 188
DISTRIBUTION CODE
39. Entity Entity means a Person involved in either the generation,
transmission, distribution, acquiring, purchasing,
supplying/delivery or consuming electrical power and energy.
40. Equipment Means Plant and/or Apparatus
S&A 188
DISTRIBUTION CODE
56. Metering Service An entity enrolled with the MO (currently NTDC).to:
Provider (MSP) a) to collect all metering information required by the Commercial
Code and its operational procedures, for the Market Operator to
perform the settlement functions;
b) to assess the completeness and consistency of the metering
information; and
c) to transfer the metering information to the Market Operator
through electronic means, at such intervals as specified in the
relevant operational procedures.
57. Negative Phase A term used within the theory of symmetrical components,
Sequence which is a method of analysing an AC multiphase System.
58. Network Load Load Management which is done on an equitable basis for the
Management purposes of stabilising the system, be it shortage of generation
or transmission outages.
59. New Market or The electric power market established in accordance with the
CTBCM high-level and detailed designs approved by the Authority vide
its determinations dated 5th day of December 2019 and 12th
day of November 2020 as may be amended by the Authority
from time to time.
60. Nominal Voltage A suitable approximate value of voltage used to designate or
identify a system.
61. Normal Operating The number of Alternating Current cycles per second, expressed
Frequency in Hertz at which the System normally operates, i.e. 50 Hertz.
62. Operational Effect Any effect on the operation of the relevant other System which
causes the Systems of the DNO, NGC or otherUsers, as the case
may be, to operate (or be at a materially increased risk of
operating) differently from the way in which they would or may
have operated in the absence of such effect.
63. Operational The equipment boundary one DNO or User and another where
Boundary control of the equipment changes. If not explicitly defined it is the
Ownership Boundary.
64. Output Usable or That portion of Registered Capacity, which is not unavailable
(OU) due to a Planned Outage or breakdown.
65. Overloading The condition under which part of the System is subject to a
Load in excess of the normal design rating of that part of the
System and not due directly to System fault current.
66. Ownership The boundary between the equipment owned by one
Boundary DNO or User and the Equipment owned by another.
S&A 188
DISTRIBUTION CODE
82. System Stability The state of the System whereby predicted changes in load and
generation can be accommodated without any detrimental effect
on the System.
83. System Tests Those tests which involve simulating conditions or the controlled
application of irregular, unusual or extreme conditions on the
Total System or any part of it, but not including routine testing,
commissioning or re-commissioning tests.
S&A 188
DISTRIBUTION CODE
84. Telemetering A process in which measurements are made at some remote
location and the results are transmitted by
telecommunication. The transmission of the values of
measured variables using telecommunication
techniques.
85. Total System The NGC Transmission Systems, other TNO systems, and the
Distribution Systems of all the DNOs in Pakistan.
86. User: The term used in various sections of the Distribution Code to refer
to the person who is directly or indirectly connected with or using
the Distribution system of the DNO to whom this code is
applicable and includes other DNO and generator as identified
in relevant sections of this code.
AMENDMENT HISTORY
Amendment History
Version Date Change Reason
1 2005 Original Required under the Act
2 2022 Significant revision The CTBCM
S&A 188