1

Grid Code

Electricity Power System

Sumatra 2007

Electricity for Better Life

 2

PT PLN (PERSERO)

DECISION of BOARD OF DIRECTORS OF PT PLN (PERSERO)

NUMBER 367. K/DIR/2007

ON

GRID CODE OF SUMATERA ELECTRICITY POWER SYSTEM

BOARD OF DIRECTORS OF PT PLN (PERSERO)

Considering: a. that Electricity power supply system of

Sumatra has been expanded and supported by

some operators of Electricity Power Supply

Business, so that it is needed Electricity

power Grid Code to create a reliable an

integrated Electricity power transmission

system;

b. that there is no provisions on Electricity

Power System Grid Code of Sumatra issued

by the Government cq. The Ministry of

Energy and Mineral Resource as the

Regulator Body in the field of Electricity

power.

c. that pursuant to the consideration as

referred to letter a and b above, it is

required to stipulate Decision of the

Board of Directors of PT PLN (Persero) on

Electricity Power System Grid Code of

 3

Sumatra

In view of 1. Law of The Republic of Indonesia Number 15

Year 1985 on Electricity power

2. Law of The Republic of Indonesia Number 19

Year 2003 on State Owned Enterprise

3. Government Regulation of The Republic of

Indonesia Number 10 Year 1989 on Supply

and Exploitation of Electricity Power as

have been amended based on Government

Regulation of The Republic of Indonesia

Number 3 Year 2005 and Government

Regulation of The Republic of Indonesia

Number 26 Year 2006;

4. Government Regulation of The Republic of

Indonesia Number 23 Year 1994 on Transfer

of Public Company Form (Perum) of State

Electricity To Become Limited Liability

Company (Persero).

5. Government Regulation of The Republic of

Indonesia Number 45 Year 2005 on

Establishment, Management, Control and

Liquidation of State Owned Enterprise

6. Articles of Association of PT PLN

(Persero)
 4

7. Decree of the Minister of State Owned

Enterprise Number KEP-180/M-MBU/2003 on

Cessation and Appointment of the Members

of Board Of Directors of the Limited

Liability Company (Persero) PT Perusahaan

Listrik Negara

8. Decision of Board Of Directors of PT PLN

(Persero) Number 001.K/030/DIR/1994 on

Application of Regulation Referring to the

Transfer of Legal Form of the Company

9. Decision of Board Of Directors of PT PLN

(Persero) Number 337.K/DIR/2007 on

Organization and Working Administration of

PT PLN (Persero)

HAS DECIDED

To stipulate: DECISION of BOARD OF DIRECTORS of PT PLN

(PERSERO) ON ELECTRICITY POWER SYSTEM GRID CODE

OF SUMATERA

Article 1

Electricity Power System Grid Code of Sumatra are as

contained in the Attachment representing an

inseparable part of this Decision of Board of

Directors

Article 2
 5

Electricity Power System Grid Code of Sumatra as

referred to Article 1 must be adhered by all

Business Units of PT PLN (Persero) executing the

development of Power Generation, Transmission and

Distribution and shall become a guidance for

business perpetrator of Electricity Power Supply

Business and Electricity power consumer connected to

Sumatra Electricity Power System Grid

Article 3

Electricity Power System Grid Code of Sumatera may

be revised in accordance with needs or after the

issuance of Regulation of the Minister of Energy and

Mineral Resource on Electricity Power System Grid

Code of Sumatra

Article 4

(1) All installations of Electricity power

connected to Sumatra Electricity Power System

Grid before stipulating this Decision of the

Board of Directors, within period of 3 (three)

years, installation operator is obliged to

conduct adjustment to Sumatra Electricity Power

System Grid.

(2) In the case of installation operator consider

that adjustment of installation as referred to

paragraph (1) cannot be conducted because of

 6

technical reason or other reason, then within

period of 2 (two) years, the installation

operator is obliged to report it to the

Committee for Grid Code Management.

This Decision shall come into force commenced as

from the stipulation date

Stipulated in: Jakarta

On 28 December 2007

PRESIDENT DIRECTOR

Signed and stamped

EDDIE WIDIONO S
 7

Addresses of

DIRECTOR OF TRANSMISSION AND DISTRIBUTION

Praise our thanks to the God Allah SWT, who has given the

power to us, so that Electricity Power System Grid Code of

Sumatra could be finished. This Grid Code is representing a

set of regulations, conditions, and standard aimed to

guarantee safety, security, reliability, quality and

efficiency of System operation in following the improvement of

Electricity Power requirements.

Publishing this Electricity Power System Grid Code of Sumatra

will become guidance for all Electricity consumers in

executing design plan, development, operation plan and system

operation, measurement and transaction settlement, and data

requirement in the Electricity Power System of Sumatra.

In line with the growth of Electricity power usage in the

Sumatra System that has been high, where it is needed addition

on generating and channeling installation, then closed

coordination among Grid users will determine fluency of

development process until the operation of such facility.

Coordination may be executed well if there are the same

guidance, namely Electricity Power System Grid Code of Sumatra

In order to make all Grid users understand on the provisions

in this Grid Code, then socialization concerning the contents

of Grid Code is very vital for all Grid users of Generating,

Transmission and Distribution installation, besides IPP and

 8

High Voltage Consumers.

Expectation in order to reach reliability and quality of

Electricity power system is highly depended on the compliance

of Grid users in executing the provisions of Grid Code,

including to conduct upgrading this Code in accordance with

the growth of system and technological progress of Electricity

power.

In this opportunity, I would like to many thanks to the Team

arranging this Electricity Power System Grid Code of Sumatra

led by Deputy Director of Transmission Guidance who have

worked hard to complete this Grid Code. Hopefully Allah SWT

give HIS reward and benediction to all Team members.

Finally, I hope that existence of this Grid Code may give

benefit for better operation of Electricity power system in

the future.

Director of Transmission and Distribution

Dr. HERMAN DARNEL IBRAHIM

 9

INTRODUCTION

Electricity Power System Grid Code of Sumatra shall represent

an inseparable part of the Decision of Board of Directors

Number 367.K/DIR/2007 dated 28 December 2007 on Electricity

Power System Grid Code of Sumatra.

This Grid Code is a set of regulations, conditions and

standards to guarantee security, reliability and operation as

well as development of efficient system in fulfilling the

increase of electricity power needs.

Electricity Power System Grid Code of Sumatra is arranged

based on conditions of structure of Electricity Power System

of Sumatra for this time, to be applied for all stakeholder at

Sumatra System, namely PT PLN (Persero) Penyaluran dan Pusat

Pengatur Beban Sumatera (P3B Sumatra)as the operator of

transmission Grid and at once as the system operation, PT PLN

(Persero) Pembangkitan Sumatera Bagian Utara, PT PLN (Persero)

Pembangkitan Sumatera Bagian Selatan, PT PLN (Persero) Proyek

Induk Pembangkit dan Jaringan, Private Power Generating

Companies (IPP), PT PLN (Persero) Regional se Sumatra and the

large scale consumer in which their installation directly

connected to the transmission Grid

All business perpetrators at Sumatra System are obliged to

meet all provisions in this Grid Code as basis for operation

of Electricity power supply installation to be possessed. In

addition, the provisions in this Grid Code will give

 10

clarification concerning obligations of each business

perpetrator at Sumatra System

Grid Code of this Sumatra System is dynamic documents so that

it should always be updated by the Committee of Grid Code

Management (Grid Code Management Committee) along with the

development of system condition and business structure and the

change of electricity system complexity.

 11

Grid Management Code - GMC

GMC 1.0 Unpredictable Condition

GMC 2.0 Management Committee

GMC 3.0 Dispute settlement

GMC 4.0 Change of code

GMC 5.0 Enforcement

GMC 6.0 Reporting

GMC 7.0 General Interpretation of Grid Code

 12

Grid Management Code - GMC

This Grid Management Code is to explain general

procedures concerning the change/revise of Grid

Code, dispute settlement, and periodical re-

assessment of operation and transmission grid

management. Application of the Procedures will push

for creating Grid security and reliability, motivate

economic and operation efficiency, and facilitate

Grid investment and development

Grid Code Management Committee (GCMC), hereinafter

referred to as Management Committee is a committee

formed to run the procedures outlined in this Grid

Management Code.

GMC 1.0 Unpredictable Condition

GMC 1.1 In the event of a condition that has not been

included into the provisions Grid Code, PT PLN

(Persero) Penyaluran dan Pusat Pengatur Beban

Sumatera (P3B Sumatra) hereinafter abbreviated by

“P3B Sumatra” has to immediately conduct consultancy

with all related Grid Users to reach into agreement

correctly. If it is not reached an agreement within

period that is available, then P3B Sumatra has to

immediately take decision by considering Grid User

views subject to the effect. In this case, each Grid

User has to fulfill all instructions issued by P3B

 13

Sumatra as far as the instructions are consistent

with the technical characteristic of Grid User

facility equipments listed in accordance with the

Grid Code. P3B Sumatra has to immediately submit all

unpredictable condition together with the decision

taken by P3B Sumatra to the Management Committee to

be reviewed.

GMC 2.0 Management Committee

GMC 2.1 Management Committee of Grid Code or referred to as

Management Committee is established to carry out the

tasks expressed at GMC 2.2

GMC 2.2 Management Committee shall undertake:

a. to review Grid Code and its implementation,

according to the requirements

b. to review all proposals submitted by Grid User

or the interested parties for amendment of Grid

Code

c. to publish each recommendation for amendment of

Grid Code in which by Management Committee is

assumed necessary or intended, together with

the reasons for recommendation

d. to publish interpretation and guidance for Grid

Code together with its implementation if it is

needed by Grid User or the interested parties;

 14

and

e. to arrange recommendation for change of Grid

Code covering unpredictable condition, such as

mentioned at GMC 1.0.

GMC 2.3 Delegation In Management Committee

GMC 2.31 Management Committee consists of PT PLN (Persero)-

Head Office, P3B Sumatra, PT PLN (Persero)

Pembangkitan Sumatera Bagian Utara hereinafter

abbreviated by KITSU, PT PLN (Persero) Pembangkitan

Sumatera Bagian Selatan (hereinafter abbreviated by

KITSBS), PT PLN (Persero) Regional Sumatra. At the

early steps, the Chief of Management Committee is

General Manager of P3B Sumatra or those appointed to

represent him, personnel in odd number as follows:

a. A Chief from P3B Sumatra;

b. Members

i. two members representing PT PLN (Persero)

- Head Office;

ii. two members representing P3B Sumatra;

iii. one member representing KITSU;

iv. one member representing KITSBS

v. one member representing each PT PLN

(Persero) Regional Sumatra; and,

 15

vi. one member representing each PT PLN

(Persero) Proyek Induk Pembangkitan dan

Jaringan di Sumatra

For further phases, Management Committee Chief shall

be selected among the Management Committee members

in the Committee Meeting. Establishment of

Management Committee shall be specified by President

Director of PT PLN (Persero).

GMC 2.3.2 Appointment of each Management Committee Member

shall be conducted by each party with the

notification officially to the Management Committee.

If it is assumed necessary, the party to be

represented may propose member replacement in the

Management Committee with the clarification on the

reason of such replacement.

GMC 2.3.3 Service period of Management Committee Chief shall

be for 2 (two) years and eligible for the next

service period. Position of Management Committee

Chairmanship shall automatically be terminated if

the pertinent concerned is permanently prevented or

does not longer work for the company/institution to

be represented and immediately selected its

substitute. While the service period of Management

Committee Member shall automatically end if there is

official letter from the institution/company

 16

concerning withdrawal of the pertinent person from

the Management Committee membership or the person

concerned is permanently prevented or does not

longer work for the company to be represented and

immediately selected its substitute.

GMC 2.4 Management Committee has to make, publish, and

always fulfill all regulations and procedures.

Management Committee has to conduct meeting at least

once in a year to review the Grid operation. Other

meeting is scheduled according to the requirement to

handle any problems and issues submitted to the

Management Committee. Management Committee should

establish Sub-Committee of Planning and Sub-

Committee of Operation. If it is required,

Management Committee may form other Sub-Committees.

GMC 2.5 Sub-Committee of Planning is obliged to review

annual plan of Grid development in order to assure

adequate provisions for reliability and efficiency

of operation for the next time. In addition, Sub-

Committee of Planning is also obliged to review and

recommend follow-up of the project proposal of Grid

development.

GMC 2.6 Sub-Committee of Operation is obliged to review

annual report of Grid operation planning and to

recommend the changes of operating procedure for

 17

reliability and economics of Grid operation. This

Sub-Committee has to conduct meeting quarterly to

evaluate realization of previous quarter operation

GMC 2.7 Operating Expenses of Management Committee

Management Committee has to submit proposal of

operational expenses budget for the next year to P3B

Sumatra on each September. P3B Sumatra has to

provide operation fund of Management Committee

amounting to the agreed budget

GMC 3.0 Dispute settlement

Interpretation and management of Grid Code may

possible cause dispute from time to time. Process of

dispute settlement of Grid Code outlined in this

clause shall be effective for P3B Sumatra and all

Grid Users, but not intended for dispute settlement

arranged separately in the Settlement Code.

GMC 3.1 Process of Dispute Settlement of The First Phase

Process of Dispute Settlement of first phase Grid

Code cover the following matters:

a. if a dispute arising among the parties and

cannot be settled informally, then one of the

parties may submit the dispute in writing to

the other party.

b. the disputed parties must meet to discuss and

 18

endeavor its settlement; if it is settled, then

its resolution shall be documented and its note

is passed to the parties.

c. if the dispute can not be settled, then it is

formed a committee consisting from delegation

of the parties to discuss and strive a

settlement; if it is settled, then its

resolution shall be documented and its note is

passed to the parties; and

d. if the dispute can not be settled by the

committee as meant at letter (c), then on the

request of one or both parties, the dispute

shall be continued to the Management Committee

for settlement; pursuant to its option,

Management Committee may continue it to a Panel

of Grid Code Dispute Settlement.

GMC 3.2 Panel of Grid Code Dispute Settlement

In the case of specific dispute, Management

Committee has to appoint Panel of Dispute settlement

comprising of 3 (three) or 5 (five) personnel having

technical capability and knowledge to discuss

subject matters disputed by the parties.

The panel has to conduct formal meetings to hear and

get statement (testimony) of each party. Position of

the parties and Panel decision must be documented,

 19

submitted to both parties, and kept as Management

Committee note. Panel Decision is binding and final.

GMC 3.3 Expense of Dispute settlement.

If a dispute is continued from the settlement

process of the first phase, then all expenses of the

settlement process will be divided based on one of

as follows:

a. if the dispute can be settled, parts of the

settlement /resolution must include allocation

of settlement process expenses; and

b. if GMC 3.2 dispute process could not be settled

(for example: the dispute is discontinued/

canceled), then both parties shall be charged

equally the expense of settlement process of

the dispute.

GMC 4.0 Change of code

If P3B Sumatra, Grid User, or PT PLN (Persero) -

Head Office believe that it is needed a change in

the Grid Code, then they must submit proposal of the

change together with arguments and supporting data

to the Management Committee.

In case of Management Committee agree on the

proposal of Grid code change, then Management

Committee shall propose to the President Director of

 20

PT PLN (Persero) to get stipulation.

In case of Management Committee refuse the proposal

of Grid code change, then the decision of rejection

has to be completed with the written reasons to the

proposing party

GMC 5.0 Enforcement

If Management Committee conclude that Grid User has

impinged or in the process of collision to the

provisions of Grid Code, then Management Committee

may submit enforcement process, with the process

steps as follows:

a. written notice is sent to the impinging party

with the clarification specifically for its

collision, and correction action needed;

b. party doing collision has to give written

answer within period of 30 (thirty) days, for

its reaction toward collision accusation, and

information on whether or not the party will

obey the instruction of Management Committee.

c. if Management Committee may agree to the

reasons given by the trespasser, such matter

has to be expressed in written to the

trespasser that problems have been settled; and

d. if Management Committee disagree with the

 21

reason given by the trespasser, then Management

Committee has to document the accusation to the

trespasser, and recommend to President Director

of PT PLN (Persero) to be given sanction.

GMC 6.0 Reporting

GMC 6.1 Annual Report

Management Committee has to publish annual summary

from the Report of Grid Operation of the previous

year, at the latest at the end of March.

GMC 6.2 Reporting Important Occurrence

Within period of one month after an important

occurrence such as big trouble in the System,

Management Committee should have already received

report of its occurrence. The report shall cover the

causes of trouble/occurrence, total and period of

trouble/occurrence, recommendation (if any) for the

change of operating procedures, training or

provisions of Grid Code. In the case of Grid User is

proven to conduct breach upon the provisions of Grid

Code, sanction may be recommended as a part of

trouble/occurrence report.

GMC 6.3 Special Reports

Special Reports must be prepared in accordance with

the Management Committee option, such as on the

 22

request of the government or on the request of one

or more Grid User

GMC 7.0 General Interpretation of Grid Code

GMC 7.1 Table contents, Introduction and Each Title are not

interpreted as parts of Grid Code

GMC 7.2 Grid Code is published and applied in Indonesian

language

GMC 7.3 All operational communications between P3B Sumatra

and PLN Generating/Generating Company or other Grid

User must use Indonesian language except on the

written approval of P3B Sumatra.

GMC 7.4 P3B Sumatra is as

a. Grid operator and owner; and

b. Coordinator in all Grid operation including

Dispatch.

Such matters may be revised, along with the growth

of organization chart in the course of restructuring

Electricity power sector

GMC 7.5 The Word of “in written" in this Grid Code contain

definition by typewriter, printer, lithography,

facsimile, and other reproducing procedures of words

which are read clearly and permanent, and the way

agreed by P3B Sumatra with the delivery through

computer to computer link (LAN/e-mail)

 23

GMC 7.6 If in the Definition and Terminology (Glossary),

there are clarification concerning an expression or

word (term), meanwhile in the Grid Code there is

more specific definition, then definition existing

in the Grid Code shall be assumed more precise than

the clarification in the glossary.

GMC 7.7 If there are reference to an item with the data as

expressed by full number, smaller fraction than 0.5

shall rounded downwards, whereas the same fraction

or larger than 0.5 shall be rounded up.

GMC 7.8 All references of time are the Time of Western

Indonesian Standard Time (WIB), and expressed in

notation of 24 Hours, 2 digit for “hour" (00 till

23) and 2 digits for minutes (00 till 59) with the

expression of “hour”

GMC 7.9 All ‘unit’, ‘symbol’, and its multiplication shall

follow the international convention.

 24

Connection Code - CC

CC 1.0 Objectives

CC 2.0 Characteristics of Grid Performance

CC 3.0 Conditions For Grid User Equipments

CC 4.0 Connection Procedures

CC 5.0 Characteristics of Registered Operation

CC 6.0 Data of Facility Planning and Operation

CC 7.0 Nomenclature and Identify of Equipments

CC A1 Appendix 1: Conditions and Standardization of

Equipments at Connection point

CC A2 Appendix 2: Measurement, Telemetry, and Control at

Connection point

CC A3 Appendix 3: Equipment Numbering and Code

Identification
 25

Connection Code – CC

This Connection Code expresses technical and

operational minimum conditions for each Grid User,

both which have and will be connected into

transmission Grid, and the technical and operational

minimum conditions which must be fulfilled by P3B

Sumatra at Connection points with Grid users

CC 1.0 Objectives

Objectives of this Connection Code is to ensure

that:

a. Technical and operational conditions which must

be fulfilled by Grid User in order to make

connection with transmission Grid shall be

expressed clearly, and

b. Grid User is connected to transmission Grid

only if the technical and operational

conditions expressed in the Connection Code

have been fulfilled.

CC 1.1 This Connection Code shall be applied for P3B

Sumatra and all Grid Users, among other:

a. Generating Company directly connected to the

Grid

b. Distribution Units at Connection points with

the Grid
 26

c. Big Consumer directly connected to Grid; and

d. Agent/Company who work for the above mentioned

Grid users, such as Contractor of Maintenance

and Development and others.

CC 2.0 Characteristics of Grid Performance

CC 2.1 P3B Sumatra and all Grid Users must endeavored as

maximum as possible in order to meet each Connection

point, the following working performance may be

fulfilled.

a. nominal frequency 50 Hz, is endeavored not to

be lower then 49.5 Hz or higher than 50.5 Hz,

and during emergency period (emergency) and

trouble, System frequency is permitted to

descend till 47.5 Hz or increase up to 51.5 Hz

before generating unit is permitted to quit

from the operation

b. System voltage had to be defended in the

following limitation:

Nominal voltage Normal Condition

275kV + 10%,-10%

150kV + 10%,-10%

66kV + 10%,-10%

20kV + 10%,-10%
 27

c. Total maximum harmonic distortion in each

Connection point in a normal operation

condition and at out planed and non planned

condition must fulfill as follows:

Nominal Voltage Total Distortion

275 kV 3%

150kV 3%

66kV 3%

20kV 3%

d. Maximum negative sequence component and phase

voltage in the Grid may not exceed 1% at normal

operation condition and planned out and not

more than 2% during momentary impulse voltage

occurrence (infrequently short duration peaks),

and

e. voltage fluctuation at one particular

connection point with fluctuation load should

not exceed the limitation:

(i) 2% of the voltage level for all changes of

steps, which may recur. Each big excursion

voltage occurrence outside of the change

of step may be allowable till 3% as long

as do not generate risk to the

transmission grid, or Grid User

 28

installation. Voltage Blink till 5% at the

time of operating Electricity motor which

are rarely happened is tolerable.

(ii) sort term flicker 1.0 units and long term

0.8 unit measured by flicker meter in

accordance with the specification of IEC-

868

f. power factor (Cos p) in the connection point

between Grid User installation with minimum

Grid amounting to 0.85 lagging

g. both parties is obliged to install power

quality meter which may monitor continually and

recorded in the form of softcopy.

CC 2.2 Characteristic of Grid Performance expressed at CC -

2.1 might be possibly not fulfilled at a hard

trouble condition at the System, such as breaking

System, exit of big component from the System and/or

voltage collapse. P3B Sumatra and all Grid Users are

obliged to coordinate in order to guarantee

achievement of performance characteristic of Grid

transmission at item CC 2.1, except at very critical

condition.

CC 3.0 Conditions For Grid User Equipments

CC. 3.1 General Conditions for all Grid Users:

 29

a. All equipments must be designed and attached

based on good specification and operated and

looked after based on a good practices in the

electricity industry (good utility practices),

and must be able to operate at the condition as

defined by CC 2.1

b. As addition to the conditions of CC 3.1. a, all

Grid User equipments must fulfill the standards

or conditions as expressed in Appendix 1 of

this Connection Code; and

c. Grid User has to pay for all link installation

facility expenses to Grid, Load Regulator

Center and/or Load Regulator Load Regulator

Unit/Sub Unit must own full operational control

for all facilities connected to high voltage

grid without reference to the ownership of it.

If then in the future a facility give advantage

to the new comer as Grid User, then P3B Sumatra

will arrange the new Grid User participate to

compensation the investment value of old Grid

Users on proportional basis.

CC 3.2 Generating Unit Conditions

This Part arrange technical criterion and design,

and conditions of performance for generating unit

directly connected to transmission Grid, with the

 30

exception for units assumed very small. For the sake

of Grid Code and Connection Code, classification of

generating unit is defined as follows:

Big : larger or the same with 100 MW;

Medium : from 30 MW up to less than 100 MW;

Small : less than 30 MW

CC 3.2:1 Each Big Generating Unit has to be provided with:

a. governor of quick reaction having an influence

to the frequency primary regulator of System

among 48.5 Hz till 51.0 Hz. Generator has to

able to accept signal of Automatic Generation

Control (AGC) from the dispatch of Load

Regulator Center/Load Regulator Unit to enable

arrangement of secondary system frequency

b. automatic voltage regulator of quick reaction

for voltage regulation of terminal generator in

the spanning generating unit operation without

resulting instability; and

c. power system stabilizer

CC 32.2 Each Medium Generating Unit must be provided with

a. governor of quick reaction having an influence

to the frequency primary regulator of System

among 48.5 Hz till 51.0 Hz. Generator has to

able to accept signal of Automatic Generation

 31

Control (AGC) from the dispatch of Load

Regulator Center/Load Regulator Unit to enable

arrangement of secondary system frequency

b. automatic voltage regulator of quick reaction

for voltage regulation of terminal generator in

the spanning generating unit operation without

resulting instability;

CC 3.2.3 Each Small Generating Unit must be provided with

a. Governor having an influence to the frequency

primary regulator of System among 48.5 Hz till

51.0 Hz; and

b. automatic voltage regulator of quick reaction

for voltage regulation of terminal generator in

the spanning generating unit operation without

resulting instability;

CC 3.2.4 Each Generating Unit must be able to operate

according to capability to be declared

a. at frequency in the spanning of 48.0 Hz till

51.0 Hz; and

b. at each power factor among 0.85 lagging and

0.90 leading.

exemption of this conditions is induction generating

unit of small capacities or agreed by Load Regulator

 32

Center or Load Regulator Unit/ Load Regulator Sub

Unit.

CC 3.2.5 Each Generating Unit must remain connected to Grid

at spanning frequency of 47,5 Hz till 52,0 Hz.

Separating Generating Unit from Grid in spanning.

This frequency is enabled if it is representing part

of Grid security as a whole arranged by Load

Regulator Center or Load Regulator Load Regulator

Unit/Sub Unit.

CC 3.3 Conditions of Communication Equipments of Grid User

Each Grid User must provide Communication Equipments

connected to communication facility Load Regulator

Center or Load Regulator Unit/Load Regulator Sub

Unit:

Voice - Operational:

Special Communications Circuit and

Redundancy for big Generating connected to

275 kV and Central Power Station 275 kV;

and, Telecommunication network of PT PLN

(Persero) for medium and small Generating

connected to 150 kV and 66 kV and Central

Power Station of 150kV and 66 kV

- Administrative:

Telecommunication network of PT PLN

 33

(Persero) or special circuit of general

telecommunications for all Grid Users.

Data - Circuit of special communications for

SCADA

- Circuit of special communications for

Protection Net

- Telecommunication network of PT PLN

(Persero) or special circuit of general

telecommunications for facsimile; and

- Telecommunication network of PT PLN

(Persero) or special Grid for computer

network.

CC 3.3.1 To guarantee availability of monitoring and adequate

transmission Grid arrangement, telecommunications

facility among Grid User and Load Regulator Center

or Load Regulator Unit/Load Regulator Sub Unit have

been arranged in accordance with the following

conditions or other communications facility agreed

by Load Regulator Center or Load Regulator Unit/Load

Regulator Sub Unit

CC 3.3.2 Grid User must install, look after and operate two

voice communications channel independently, in the

Control Room of Grid User in order to communicate

with Load Regulator Center and/or Load Regulator

 34

Unit/Load Regulator Sub Unit. Terminology of

‘independent’ means that if one channel is annoyed,

one another channel may still be used. The

Communication channels must be integrated adequately

with the telecommunication facility which have been

existed. Voice channel must be used for

communications among operator of Load Regulator

Center/Load Regulator Unit/Load Regulator Sub Unit

with operator of Grid Users, and only used for the

purpose of operational only. Telecommunication

facility has to be completed by main power supply

and adequate reserves.

CC 3.3.3 Grid User must install and look after computer

series separately and facsimile which are compatible

with the equipments of Load Regulator Center and/or

Load Regulator Unit/Load Regulator Sub Unit.

CC 3.3.4 Grid User must install, maintain and operate data

channel of SCADA at connection point providing

indication, measurement, telemetry and remote

control, such as expressed at Appendix 2 of this

Connection Code to Load Regulator Center and/or Load

Regulator Unit/Load Regulator Sub Unit.

CC 3.3.5 Grid User must install, maintain and operate data

channel of Grid protection at Connection point,

providing indicating remote protection, measurement,

 35

telemetry and remote control, as stated at Appendix

2 of this Connection Code to Load Regulator Center

and/or Load Regulator Unit/Load Regulator Sub Unit

CC 4.0 Connection Procedures

CC 4.1 Submitting Data and Information

Application is submitted at least 30 (thirty)

workdays before the execution date of granting

voltage (energize) of Connection point, provided

that Grid User have fulfilled the conditions for

facility and related connection points.

a. According to the conditions in Scheduling and

Dispatch Code (SDC), and have submitted data

and information needed in accordance with the

Data Requirements Code – (DRC) with sufficient

time for its technical evaluation

b. fulfilling conditions of Operating Code (OC)

c. submitting written request to P3B Sumatra/Load

Regulator Unit for the purpose of energizing

Connection point, including information on the

intention of the quickest time for energizing

d. submitting to P3B Sumatra/Load Regulator Unit

on information needed to prepare sequence of

field work:

i. list of Grid User Equipments (such as

 36

transformer, tap changer, reactive

arrangement and supply, protection

equipments and others) influencing Grid;

and,

ii. list of personnel of Grid Users to be

responsible to give and take data or

information needed according to the

Operation Code and Planning Code and

Operational execution concerning the name,

position, responsibilities at connection

point or location of its office

e. to submit to P3B Sumatera Load Regulator Unit

written confirmation that all equipments at

connection point have fulfilled the conditions

of Grid Code, and Connection Code, except for

something that guaranteed by P3B Sumatra

CC 4.2 Before connection point is given voltage, Grid User

must prove to P3B Sumatra/Load Regulator Unit that

Grid User have fulfilled all conditions from the

Institute in charge that is the inspection,

construction certificate, voltage worthiness/

synchronization and further before loading must be

provided with certificate of operational worthiness

for the facility.

Despitefully, Grid User must prove that

 37

communications needed, protection, and control

equipments have fulfill the standard in Grid Code

Facility to be built by Grid User must be checked

and agreed by a certification body that has been

accredited or which have been agreed by P3B Sumatra

and Grid User. Permit for connection in to Grid must

be given in writing by P3B Sumatra to Grid User, and

procedure of granting voltage must be followed by

the Grid User

CC 4.3 Obligation of P3B Sumatra

Before the date of energizing, Connection point, and

conditions of connection have been fulfilled, then

P3B Sumatra must:

a. specified a decision whether the facility of

Grid User have full met the conditions in Grid

Code;

b. preparing, approving and submitting to Grid

User, schedule of field covering information

i. list of equipments of P3B Sumatra and Grid

User Equipments at Connection point;

ii. list of activity to be conducted by P3B

Sumatra and Grid User at Connection point;

iii. clarification/schedule for

telecommunications, measurement meter,

 38

protection Grid, telemetry and equipments

control; and

iv. list of personnel P3B Sumatra who is

responsible give and accept data and

information that is needed According to

Code of Operation and Code of Planning and

implementation, operation, covering; name,

position/occupation, responsibilities, and

set of organization

c. preparing procedure of local working safety,

name of worker of working safety coordinator,

according to with conditions in Operation Code

CC 4.4 Inspection and Certification of Connection point

CC 4.4.1 P3B Sumatra and Grid User conduct agreement

time/dated for inspection of Connection point. On

not more early and dated asked by Grid User at

Connection Code CC 4.1, but cannot be delayed clear

gratuitously. P3B Sumatra must conduct inspection of

connection point together with related equipments

other its is including examination that is needed,

to assure that voltage gift (energize) connection

point will not bother security and continuity of

operation

CC 4.4.2 If P3B Sumatra express that condition of connection

point fulfill conditions of Grid Code and ready for

 39

energize, then P3B Sumatra must publish Certificate

of Connection point On the contrary, if P3B Sumatra

express that condition of connection point do not

fulfill conditions of Grid Code and do not slap for

energize, then P3B Sumatra must give statement

written to Grid User.

CC 4.4.3 In the case of P3B Sumatra have expressed that

connection point and/or the other related equipments

do not ready to accept voltage, Grid User must

conduct repair that is needed for connection point

and/or the other related equipments, and inform to

P3B Sumatra to conduct reexamining. P3B Sumatra and

Grid User then agree on time/dated execution

inspection of the money

CC 4.5 Energize of Connection point

After P3B Sumatra publish Certificate of Connection

point, Grid User and P3B Sumatra must together

perform agreement concerning procedure and time of

the energize

CC 5.0 Characteristic Registered Operation

Before energize of Connection point, Grid User must

submit all data which needed according to Code of

Data Requirement. Grid User must also submit to

revise for data operation enlisted to showing change

that happened in connection point and/or the other

 40

related equipments

CC 6.0 Data of Planning of Facility and Operation

Before energize of facility own Grid User, Grid User

must submit all data of planning and operation of

its facility to fulfill requirement of Code of

Planning and Execution Operation. After energize

take place, Grid User is obliged to be continuously

submit data that is needed According to schedule

expressed in Grid Code

CC 7.0 Nomenclature and identify Equipments

All Equipments connected with transmission Grid must

use numbering and identify as stated in Appendix 3

Connection Code this. This conditions is gone into

effect for all and P3B Sumatra Grid User.

Arrangement identify this made for minimization of

is possibility of operator mistake in operation of

because of definition mistake in catching

instruction (see Operating Code OC 13.0

CCAI Appendix 1: Conditions and Standardize Equipments At

Connection point

CCAI 1.0 General

All equipments connected with Grid must fulfill

international standard or Indonesia National

Standard is which the mould. This matter cover, but

 41

do not limited to, PMT (circuit breakers), PMS

(disconnects, switch disconnects), Land Equipments,

Energy Transformer, Voltage Transformer, Current

Transformer, Reactor, Arrester, Bushing, Neutral

Equipments, Capacitor, Line Traps, Coupling

Equipments, and coordinate insulation at Connection

point. Despitefully, the equipments must fulfill

standard ANSI/IEEE, Code (code) NEC/NEMA and/or IEC,

except for the certain equipments is which

explicitly is expressed to follow other standard

CCAI 2.0 Conditions which must be fulfilled by Connection

point consumer to P3B Sumatera

Each extension of between Grid User facility with

transmission Grid must be controlled by PMT capable

to decide maximum current short circuit at

Connection point. Pursuant to request, P3B Sumatra

must assign value current short-circuit time of next

connection, and rating PMT time take place and at

related Connection point to be built.

CCAI 2.1 Arrangement Protection

Protection for facility of Grid User and extension

of its extension To Grid of transmission must

fulfill conditions of minimum as in under this. All

setting must be coordinated by setting is protection

P3B Sumatra to minimize effect of trouble at

 42

facility of Grid User to transmission Grid

CCAI 2.2 Time of Disconnection of Trouble

a. Time of Disconnection of trouble for the

trouble beside Grid User connected directly

with transmission Grid, start and moment of the

happening of trouble till extinction of

electricity bow by opening PMT, must less and

or is amounting to:

i. 275kV: 1OO mille-second

ii. 150kV: 120 mili-second

iii. 66 kV: 150 mille-second

b. time of Disconnection of trouble for relation

20 kV must be determined by P3B Sumatra and/or

PT PLN (Persero) Regional, depend on location

of Connection point

c. In the case of occurrence of mistake equipments

of main protection of Grid User, then

protection reserve (back-up) for trouble in

connection point of high voltage of Grid User

provided by Grid User must be tuned with time

of disconnection of trouble less and 400 mille-

second. P3B Sumatra also must provide

protection of reserve to work with slower time

and protection of reserve of Grid User for the

 43

purpose of time discrimination. Protection of

Reserve of Grid User is also expected able to

hold out, without trip, to current of load of

arising out of during disconnection of trouble

in Grid of transmission by protection of

failure PMT’ (circuit breaker failure

protection) or protection reserve. This

condition will give opportunity of

discrimination of time of between protection of

reserve of Grid User by protection is reserve

of exist in transmission Grid.

Protection of Failure of PMT must be attached

at all of connection point of PMT 275 kV and

150 kV. In the case of occurrence of failure of

disconnection of current of trouble by the PMT,

then protection of PMT failure to trip all PMT

which direct connected to PMT is unsuccessful

mentioned in time less and 250 mille-second but

must be more than 200 mille-second. objectives

of Performance system protection (protection

system performance index) Grid is 99,0%

representing size measure of mean and ability

and efficacy of equipments of protection

precisely is tripped PMT at the time of

happened by trouble of system primary

 44

(dependability index) and size measure of

security of system of protection at the time of

is not happened by trouble in system primary

(security index). Grid User is obliged to

fulfill conditions of Grid Code to reach number

efficacy of the protection

CCAI 2.3 Equipments of Protection that is needed

CCAI2.3.1 Protection at Facility Interconnection of All

equipments protection Grid User which possible

influence transmission Grid facility must obtain and

P3B Sumatra approval/permission. Grid User must get

approval for equipments protection plan of before

attached. conditions Protection facility

interconnection transmission Grid grouped based on

source impedance comparison to pacified channel

impedance (SIR). channel defined as

- Short channel, if SIR > 4,0

- Channel, if 0.5 < SIR < 4,0

- Long channel, SIR < 0,5

a. Protection Channel 275 kV

i. using duplication philosophy (scheme

protection a and scheme protection b) with

provisions differ type protection or if

its type is of equal must use different

 45

measurement algorithm, different

manufacture. Telecommunications protection

system used for scheme protection a and

scheme protection b must use different

communications media namely fiber optics

and PLC (power line carrier); scheme

protection minimum for channel 275 kV -.

is such as at table A1. 1:

ii. provided with main Rele Out-Of-Step and

the reserve, for the block work distance

relay at energy oscillation condition

(power swing);

iii. each PMT transmission channel terminal

must be provided with protection failure

PMT (circuit breaker failure protection);

and,

iv. each transmission channel terminal must be

provided with scheme protection tripping

and recovering one phase and three phases.

Reclosure of Three phases must be

completed with rele synchro-check

 46

Table A1.1.

Scheme Protection Channel Minimum 275 kV

Protected Protection Scheme Telecommunication

Channel Line
PLC FO
Short Channel Protection Scheme (a)
(SIR>4) Main 1: Tele-protection CD
Reserve: Tele-protection Z
+DEF
Protection Scheme (b)
Main 2: Tele-protection CD
Reserve: Tele-protection Z
+DEF
Medium Channel Alternative I
(O,5<SIR<4) & Protection Scheme (a)
Long Channel Main 1: Tele-protection Z
(SIR<O,5) + DEF
Reserve: Z
Protection Scheme (b)
Main 2: Tele-protection CD
Reserve: Tele-protection Z
+ DEF
Alternative II (*)
Protection Scheme (a)
Main 1: Tele-protection Z
+ DEF
Reserve: Z
Protection Scheme (b)
Main 2: Tele-protection Z
+ DEF
Reserve: 7
 47

Remarks:

CD = Current Differential; DC = Directional Comparison

DEF= Directional Earth Fault; Z = Distance Relay; PLC= Power Line

Carrier

(*) scheme of distance relay use scheme transfer different trip such as
permissive under reach and permissive over reach

b. Channel Protection 150 kV and 66 kV

i. Short channel must protect by differential

using pilot of wire or protection current

differential through fiber optics or

protection directional comparison (type

non-impedance);

ii. Channel which is and the length, must

protected with scheme of distance relay

using to transfer trip, in the form of

permissive under reaching or permissive

over reaching, or scheme of directional

comparison. The scheme must also include

Protection zone-2 and zone-3 with its

time, is and provided with protection

Directional Earth Fault, and protection

Over-Current.

iii. Each rele in terminal of SUTT must capable

to tripping and reclosing’ three phases,

and special of protection SUTT 150 kV

capable to ‘tripping and reclosing one

 48

phase. execution of Reclosing of three

phases must through synchrony check relay.

iv. Media for scheme of distance relay using

to transfer trip is PLC by back is up

Fiber Optic v. For channel of transmission

by 2 or more section SKTT/SUTT of short

Channel of pattern of protection SKTT then

current differential must be provided with

distance relay in one rele and back up

over current relay/ground fault relay

CCAI 2.3.2Protection of Transformer of Energy must fulfill

table A1. 2 following

Table A1. 2: Protection of Energy Transformer

Protection Ratio and transformer capacity

150/66 kV, 150/20 kV, 66/20kV 275/150
< 10 MVA 10 up to > 30 MVA kV
30 MVA
HV LV HV LV HV LV HV LV
More temperature
Bucholz
Sudden pressure
Differential
More current
Thermal
Earth Fault
Restricted EF

*: for transformer which are grounded through big

resistant impedance
 49

Reserve Protection of transformer distribution such

as rele current more phase/ground phase (OCR/GFR)

must be coordinated by protection is feeder

According to the agreement between P3B Sumatra with

Grid User.

CCAI 2.3.3 Protection unit Generator

Protection of all Unit of Generator must be

coordinated by protection is Grid of transmission in

any case for protection of reserve to trouble of

land and short-circuit of such as rele of current

more (rele 50/51) and voltage of current more (51V),

protection to trouble of excitation more such as

rele over-excitation (rele V/Hz or 59/81 or 24),

protection to trouble which can cause generator

operate asynchrony of such as rele out-of-step (rele

78) and rele loss-of-field (rele 40), protection of

Voltage and Frequency of such as rele under/over-

voltage (rele 59) and rele under/over-frequency

(rele 81)

CCAI 2.3.4Bus of Protection High Voltage

All rails of high voltage connected to Grid of

transmission representing outlet of generating or

outlet IBT (275/1 50 kV or 150/66 kV) must be

provided with protection of bus differential

 50

CCAI 2.3.5Disturbance Fault Recorder

In the case of happened by the trouble utilize to

water down analysis of trouble then

i. each connection point to Grid 275 kV of besides

must be provided with external of disturbance,

Sequential Event Recorder (SER) is also

completed by internal disturbance and scheme

protection a and scheme protection b.

ii. each connection point to Grid 150 kV or 66 kV

must be provided with internal of disturbance

and Sequential Event Recorder (SER) and

protection.

iii. protection of transformer of distribution of

side of incoming and protection feeder must be

provided with internal of disturbance and

Sequential Event Recorder (S ER) and

protection.

CCAI 3.0 Meter Revenue

All Connection point must be provided with the

Voltage Transformer and Current Transformer for

measurement revenue According to specification in

Metering Code

CCA2 Appendix 2: Measurement, Telemetry, and Control at

Connection point
 51

Signal which must be sent/accepted to/from Load

Regulator Center and/or the Unit/Load Regulator Sub

Unit is such as Table A2.1 together with

Table A2.1 List of Signal

Table A2.1: Enlist Signal

Note:

GI: Central Power Station TS: Tele Signaling TM: Tele Metering

TRF: Transformer TSS: single Tele Signaling of TSD: Double Tele Signaling

GENTRF: Generator RCD Transformer: Digital Tele Control of RCA: Analogous Tele

Control

GENE: Generator IMPUL: Impulse REACT: Reactor

(“x" indication signal which must be reserved for by each extension type

CCA3 Appendix 3: Equipment Numbering and Code

Identification

CCA3 1.0 Code Identification

Code Identification consist of 18 character compiled

in 3 block representing Sub-Code Identification for

location, Sub-Code Identification for the and Sub-

Code equipments identify for the element. Its

 52

compilation shall be as follows:

A HHHHH A HHHHH A AA HH P

A B C

Block A: Sub-Code Identification location

Block B: Sub-Code Identification equipments

Block C: Sub-Code Identification element

A: figure/number

H: letter

P: number or letter

Permitted to use one space (blank) or without space

of each group of Number or letter.

Example: 3BKSAM 5KOPEL1 05 CB1

CCA3 2.0 Sub-Code Identification Location

Sub-Code Identification location consist of 6

characters, divided into 2 parts. Part of first

consist of 1 character showing Area code. Part of

second consist of 5 character showing location code.

code of Location is abbreviation of specific name of

location. Sub-Code Identification of location

expressed with the following formation:

 53

A HHHH

1 2

Part 1: area code

Part 2: location code

CCA3 2.1 Area Code

Area intended as Load Regulator Unit (Area

Control Center - ACC) what have location to Field,

Field and Palembang, with code of area of each:

Load Regulator Unit (ACC) Northern Sumatera: 1

Load Regulator Unit (ACC) Sumbagteng: 2

Load Regulator Unit (ACC) Southern Sumatera: 3

CCA3 2.2 Location Code.

Location shows a location of generating center or

main power station. Code to center new generating or

new main power station determined by P3B Sumatra.

Example s of Code of location shown at Table A3.1.

Example Sub-Code Identification location shall be as

follows

1 LANSA 3 BKSAM

1 : indicating ACC Northern Sumatera

LANSA: indicating Watchman station of Langsa

(under operation of ACC Northern Sumatera)

 54

3 : indicating ACC Southern Sumatera

BKSAM: indication Generating Center of Bukit Asam

(in check ACC Southern Sumatera

Table A3.1: Example Location Code

Location Code Location Code

ACC_Northern Sumatera ACC_Sumbagteng

Tualang Cut TLCUT Simpang Haru SHARU

Tebing Tinggi TBTGI Pauh Limo PLIMO

Bagan Batu BGBTU Bangkinang BNANG

Rantau Prapat RTPAT Lubuk Alung LBALG

Belawan BLWAN Koto Panjang KTPJG

ACC_Northern Sumatera

Bukit Siguntang BKSGT

Mariana MRINA

Tarahan TRHAN

Natar NATAR

Baturaja BTRJA

CCA3 3.0 Sub-Code Identification Equipments

Sub-Code Identification treatment consist of 9

divisible character in 4 parts. The first part

contain 1 character indicating voltage code. Part of

second contain 5 character of indicating equipments

 55

name. Third parts contain 1 character of indication

Number of code of location where the equipments

attached. Part to four containing 2 character of

indicating coordinate bay.

Sub-Code Identification equipments expressed with

formation the following

A HHHHP A AA

Part 1: voltage code

Part 2: code of equipments name

Part 3: code of equipments number

Part 4: coordinate bay

CCA3 3.1 Voltage code Reference

Code of Reference of Voltage showing voltage of

equipments residing in center of generating or main

power station, shown at Table A3.2

Table A3.2. Voltage code Reference

Name Range Code

Low voltage Up to 1000 V 0

Medium voltage 1 - 10 kV 1

10—30kv 2

30—60kV 3

High Voltage 60—90kV 4

 56

90—200kV 5

200—400kV 6

Extra High voltage 400 — 600 kV 7

600—1000kV 8

Above 1000 kV 9

CCA3 3.2 Code of Equipments Name

Equipments intended as part of generating center or

main power station. Code of equipments Name are

shown in Table A3.3

Table A3.3: Code of Equipments Name

Name of Equipment Code

A. Generating Center

Water Power Plant Center PLTA

Diesel Power Plant Center PLTD

Gas Power Plant Center PLTG

Gas Engine Power Plant Center PLTMG

Geo Thermal Power Plant Center PLTP

Nuclear Power Plant Center PLTN

Steam Power Plant Center

Coal Power Plant Center PLTUB

Natural Gas Power Plant Center PLTUG

Oil Power Plant Center PLTUM

 57

Gas/Steam Power Plant Center PLTGU

B. Main Power Station Equipment

Conductor Bay 1)

Generator Bay PBKIT

Rail/Busbar BSBAR

Busbar Section BSSEC

Kopel Rail KOPEL

Trafo TRFOX2>

Diameter DAMTR

Shunt Reactor SHTXL

Shunt Capacitor SHTXC

Extension EXTEN3>

Spare SPARE4>

Substation SUBST5>

RTU RTUTS6>

1) Location code of generating center or Main

Power Station to transmission connected

2) X is voltage code of secondary transformer

coil, According to Table A3-2

3) To plan not sure extension bay

4) Spare to plan not sure extension

 58

5) For alarm Main Power Station 6) For alarm RTU

CCA3 3.3 Code of Equipments Number

Number of Equipments is serial number of equipments

in location of equipments attached

CCA3 3.3 Coordinate Bay

Coordinate of Bay intended as number given as

coordinate bay. sequence of Coordinate of bay

determined is the following - than higher level

voltage to lower voltage - from left to right - from

top downwards, and - pursuant to rotation tail

clock.

Example Sub-Code Identification for the equipments

given the following

4 KOPEL 1 07

4: indication beside 66 kV center or

generating main power station.

KOPEL: equipments name

1: indication that COUPLE Number 1 (one).

07: indication that COUPLE reside in bay

number 7

CCA3 4.0 Sub-Code Identification Component

Sub-Code Identification component consist of 3

divisible character in 2 parts. Part of first

 59

consist of 2 character of indicating component type.

Part of second consist of 1 character of indication

Number of component in equipments where the

component attached. Sub-Code Identification

component expressed with the following formation:

HH P

1 2

Part 1: code of component type

Part 2: code of component number

Code of Component composed by dad 3 character may is

also used to identify data SCADA

CCA3 4.1 Code of Component Type

Type of Component is part of equipments showed by

Sub-Code Identification equipments.

Code of Type of Component shown at Table A3.4

CCA3 4.2 Code of Component Number

Number of Component is number given for component in

equipments. Number of Component may also represent

point of measurement or deviation set-point.

determination Number of component must harmony with

determination of bay so that position of component

may is easily identified. Among other

- odd number (1, 3, 5 etc) given for PMS-REI

 60

connected to Ret is odd number

- even number (2, 4, 6 etc) given for PMS-REI

connected to Ret is even number.

Table A3.4 of Code of Component Type

Component Types Code

Separator (PMS) Rail BI

Separator (PMS) Line LI

Separator (PMS) Ground ES

Separator /Disconnecting Switch DS

Circuit Breaker CB

Tap Changer TC

Trafo Voltage VT

Example code of component type

BI 2

BI: indication that component at equipment is Rail

separator

2: indication that PMS-REI is PMS-REI number 2

CCA3 5.0 Code Identification for the Specific purpose

CCA3 5.1 Code for Ret in VDU

Rail at Main Power Station one half of breaker

beside the Generator is Rail A, and the other is

Rail B.
 61

Rail at Main Power Station one half of breaker

beside Transformer Interbus (IBT) is Rail A, and the

other is Rail B. If Generator and Transformer of

both there are in one Main Power Station then

position of more dominant Generator in determining

Rail A

Example

CCA3 5.2 Code of PMT in VDU

Special Code Identification PMT (circuit breaker) at

Central Power Station one half of breaker which is

only intended for the oral communications among all

operator, shown in display draw Main Power Station

in VDU, and is not used in database. Code

Identification expressed with the following

formation

A HH A

Part 1: voltage code reference, 6 to 275 kV, and 5

to 150 kV.

Part 2: code PMT (circuit breaker)

A for PMT connected to Rail A

B for PMT connected to Rail B

AB for PMT residing in between PMT A and

PMT B
 62

Part 3: number bay

Example:

275 kV, bay Number 1 150kV, bay Number 4

CCA3 5.3 Example Code Identification

Example 1

1 BLVLAN 5 PBKIT3 07 BI 1

1: Load Regulator Unit (ACC) Northern

Sumatera

BLWAN: PLTU Belawan

5: connected in Grid 1 50 kV

PBKIT3: Generating Unit Number 3

07: bay Number 7

BI: Section of winnow Rail (isolator bus)

1: Busbar Number 1

Example 2

3 NTRHN 5 DAMTR1 04 CB 1

3: Load Regulator Unit (ACC) Southern

Sumatera

NTRHAN: Generating center of New Tarahan

5: connected in Grid 150 kV

DAMTR1: diameter Number 1

 63

04: bay Number 4

CB: PMT (circuit breaker)

1: number 1

Example 3

3 NATAR 5 TRFO22 04 TET

3: Load Regulator Unit (ACC) Southern

Sumatera

NATAR: Central Power Station of Natar

5: voltage 150kV

TRFO2: transformer with secondary coil 20 kV

2: transformer Number 2

04: in bay Number 04

TET: Temperature of Trip Transformer

(Transformer Temperature Trip)

Example 4:

2 SKRAK1SKRAK 1 PLTA.3 - MW

2: Load Regulator Unit (ACC) Sumbagteng

SKRAK: Generating center of Singkarak

1: connected in average voltage Grid (10 till

15 kV)

PLTA: generator of unit 3

MW: Active power (Megawatt) 2

 64

Example 5:

Generating Center/Main Power Station 150 kV of PLTGU

Belawan

Table A3.5. Tele Signal

Table A3.6. Tele Information

Table A3.7. Measurement and Indication

CCA3.6.0 Color Convention

Color convention at the screen is shown at Table

A3.8

Table A3.8. Color Convention on Screen

CCA3.7.0 Switch Convention

Switch convention on screen is shown at Table A3.9

Table A3.9. Switch Convention on Screen

Operating Code – OC

Operating Code explains on regulation and procedures

applied to guarantee reliability and efficiency

Sumatra operation System may be maintained at one

particular level

OC 1.0 Basis

This Part embrace principles of safe and reliable

 65

System operation which must be followed. This parts

also specify basic obligation and all Grid User in

order to have contribution to the safe and reliable

operation

OC 11 Condition of success Operation

System is stated in a condition of good operation if

a. frequency in boundary range of normal operation

(50 ± 0,2 Hz), except deviation in a short time

in allowing at range (50 ± 0,5 Hz), while

during trouble condition, frequency may be at

boundary 47,5 Hz and 52 Hz

b. voltage in Central Power Station stay in

boundary of is set in Connection Code (CC2.0).

This Boundary must guarantee that voltage at

all customer stay in range of voltage specified

as long as voltage regulator of Grid of

distribution from equipments of energy supplier

reactive work better. Operation at boundary of

this voltage is expected can assist to prevent

the happening of voltage collapse and problem

of stability of dynamic System;

c. Level of transmission Grid loading defended to

stay in boundary specified by through study

analysis stability steady state and transient

for all potential trouble (credible outage d.

 66

mount current loading in all watchman station

and transmission Grid equipments mains (and

switch gear transformer) staying in normal

boundary rating for all single contingency

equipments trouble; and e. System configuration

in such a manner so that all PMT (circuit

breaker) in transmission Grid will be able to

break trouble current which is possible

happened and disturb equipments isolation

OC 1.2 Contingencies Classification

a. Contingency is occurrence which is because of

release or failure and one or more generator

and/or transmission

b. Credible Contingency is occurrence which is by

Unit or Load Regulator Center/Load Regulator

Sub Unit assumed by to have a potency to be

happened, and economically the System may

protected to condition do not serve of load

(loss of load as effect of the occurrence. Its

moustache is occurrence trip-one generator unit

or one transmission segment

c. Non-credible Contingency is occurrence which is

by Load Regulator Center or Unit/Load Regulator

Sub Unit assumed to minimize the possibility of

to be happened or the occurrence economically

 67

improper protected. Among other, its trip

simultaneously some generating unit, trip-two

or more transmission by crumpling of tower or

existence of some occurrence of trouble of

simultaneous by storm

d. In a state of below par such as storm or fire,

Load Regulator Center or Load Regulator

Unit/Sub Unit can chosen to specify whereas,

non-credible contingency (among other trip-more

than one transmission or annoying of some main

power station) as a(n) credible contingency,

which must protected. Load Regulator Center or

Unit/Load Regulator Sub Unit must inform all

Grid User of if reclassification is such as

that happened by following time end it

OC 1.3 Condition of Safe Operation

System assumed to stay in safe condition if a.

System stay in condition of operation

satisfactorily; or b. Returnable system to condition

of operation satisfactorily after the happening of

credible contingency, without existence of load

disconnection

OC 1.4 Maintaining System Security

To maintain System security, the following

regulation must be followed

 68

a. practical to a point, System must be operated

in such a manner so that reside in and will

remain to a state of safe operation

b. After occurrence of credible contingency or

change of condition in System, possible the

safe System becoming not to other contingency.

In This Case, Load Regulator Center or

Unit/Load Regulator Sub Unit must take steps of

adjustment of condition operation to bring back

System to safe condition.

c. Load which can be released (interruptible-load)

must be released to prevent condition operation

at low frequency or condition of reserve which

fall short. Load which can be released by is

load determined by PT PLN (Persero) Regional or

load which is according to contract may be

released in manual and automatically in order

to maintaining System security. The Load

generally will be released by before working of

release of load automatically by rele low

frequency of first level

d. Way of most effective to prevent to extinguish

of all System (total of grid blackout) is

guaranteed that balance of Generating with load

is always defended in all condition estimated

 69

will be happened. Must be made available by a

facility release of adequate load automatically

by rele is low frequency to bring back

condition of System to normal operation after

occurrence of contingency which is significant

e. Scheme of Separating Grid of transmission must

be defended for guaranteeing that if happened

big trouble in System resulting difficult to

maintain integration, then the System of is

broken to be some “electricity island" that is

each may reach balance of capacities of

Generating with load, to most trouble multiple-

contingency

f. Capability of black start facility must be

available in System to enable recovery of

System to condition of safe operation after

total extinct occurrence

OC 1.5 Condition of Reliable Operation

System is in the condition of reliable operation if

a. System stay in condition of safe operation

b. According to opinion Load Regulator Center or

Unit/Load Regulator Sub Unit, mount reserve of

capacities short-range and medium at least is

amounting to level of minimum of is set in OC

 70

of 2.2 this; and

c. There no abnormal condition such as storm or

fire which is or estimated will be happened,

what possibly will result occurrence of non-

credible contingency

OC: 1.6 Responsibilities and Obligation of System Security

Load Regulator Center or Load Regulator Unit/Sub

Unit hold main role in coordinated operation of

System in order to maintaining security and

reliability of System for the sake of all Grid User

and customer. All Grid User obliged to obey

instruction Load Regulator Center or Load Regulator

Unit/Sub Unit in order to accomplishment of security

responsibilities.

As this responsibilities and parts, Load Regulator

Center or Load Regulator Unit/Sub Unit must conduct

periodic test to equipments operation System to

guarantee that any its function both utilize to

reach reliable operation. Others, Load Regulator

Center or Load Regulator Unit/Sub Unit must test

emergency procedure and procedure of recovery of

System to guarantee execution which sprier and safe

if happened by trouble and extinction in System.

Load Regulator Center or Load Regulator Unit/Sub

Unit must specify program and schedule of

 71

examination assumed by a need to guarantee security

and System reliability. All Grid User obliged to

coordinate with Load Regulator Center or Load

Regulator Unit/Sub Unit in execution of the

examination.

OC 1.6.1 Responsibilities of Load Regulator Center for the

security of System

Load Regulator Center must

a. continuously watch status operation of Grid 275

kV and take steps which need to maintain on

safe and reliable condition

b. executing ‘PMT’ switching in Grid 275 kV

c. informing Load Regulator Unit/Sub Unit of on

existence of problem in Grid 275 kV which

possible affect reliability in parts of System

becoming Unit responsibilities/Sub units

Regulator of pertinent Load

d. coordinated Unit activity/Load Regulator Sub

Unit, PLN Generating/Generating Company, Big

Consumer, and PT PLN (Persero) Regional, that

is needed to reach objectives (a); and

e. always inform to all Grid User of on status of

security of System which underway and expected

will be happened, and the participation

 72

expected and the Grid users

OC 1.6.2 Responsibilities Unit /Load Regulator Sub Unit for

the security System

Load Regulator Unit/Sub Unit is responsible operate

part of System residing in scope of its operation

Load Regulator Unit/Sub Unit must

a. executing operation “PMT" switching in Grid 150

kV and 66 I

b. coordinated activity of PT PLN (Persero)

Regional, PLN Generating/Generating Company,

and Big Consumer is connected to Grid 150 kV

and 66 kV

c. reporting problem of related to channeling of

output power of Generating Unit connected to

Grid 150 kV or 66 kV

d. coordinated conservancy and operation “PMT"

switching Grid 150 kV and 66 kV by PLN is

Generating/Generating Company, PLN (Persero)

PIKITING, Big Consumer, and PT PLN (Persero)

Regional, if needed

e. following instruction Load Regulator Center in

a condition the emergency and in course of

System recovery (restoration); and

f. release load interruptible According to command

 73

Load Regulator Center

OC 1.6.3 Transmission Service Unit Responsibilities (UPT) for

System Security

Transmission Service Unit (UPT) is responsible

execute transmission equipments repair and

conservancy/and cable Central Power Station in its

area. Transmission Service Unit (UPT) is responsible

a. executing operation switching for the

installation facility 275 kV of if commanded by

Load Regulator Center

b. executing operation switching for the

installation facility 150 kV and 66 kV; if

commanded by Load Regulator Unit/Sub Unit

c. maintain and operate equipments supplier energy

reactive to fulfill the energy reactive

requirement According to objectives specified

by a Load Regulator Center; or the Load

Regulator Unit/Sub Unit

d. installing and maintain automatic load release

equipments by rele of low frequency of low and

rele voltage at crossing distribution utilize

to fulfill objectives specified by a Unit or

Load Regulator Center/Sub - Load Regulator Unit

in order to minimization affect System trouble

 74

time extinction and prevent the happening of

extinguishing total

e. working repair and conservancy which need to

transmission facility in installation areas

f. maintain data communications facility and voice

at System operational, including facility phone

operation, facility Code, facility SCADA, and

the communications facility for protection

g. executing setting rele protection according to

instruction P3B Sumatra

h. executing examination rele protection

periodical;

i. watch and transmission equipments condition

Central Power Station including rele, and make

declaration for status/equipments installation

or condition; and

j. watching status of all communications facility

and equipments, and repair ruined

communications equipments in order to guarantee

that operation System is not annoyed

OC 1.6.4 Responsibilities of Transmission Plane of P3B

Sumatra Responsibilities of Transmission Plane of

P3B Sumatra cover

a. planning and coordinated System protection all

 75

component in System, including main protection

reserve and (back-up), and the load automatic

release scheme by rele is low frequency at

transmission facility

b. coordination with all Grid User, for all System

protection at all of Connection point in System

c. specifying the specification of equipments

protection for all Grid development, such as

transmission channel development, watchman

station and mains equipments of main power

station

d. coordinated all activity setting rele with

Transmission Service Unit (UPT)

e. planning data communications facility and voice

at System operational, including facility phone

operation, facility Code, facility SCADA, and

the communications facility for protection; and

f. coordinated telecommunications extension

conservancy and operation with all Grid User

OC 1.6.5 Responsibilities PLN Generating/Generating Company

with Medium and Big Thermal Unit for System security

Generating of Medium and Big Thermal provide big

portion for requirement of energy and energy in

System of Electricity Power Sumatra. Operation

 76

generating which is reliable of vital importance for

reliability operation System. PLN Generating/Company

of Generating with Unit of Big Thermal of Medium den

is responsible

a. able to give service which is reliable as

expressed in sales contract Electricity power

(Power Purchase Agreement - PPA) related or

provisions of effective operation

b. declaration of all changes in ability operation

and the characteristic which is from the

beginning expressed to P3B Sumatra

c. coordinated activity of conservancy with Load

Regulator Center or Unit/Sub units Regulator of

related Load

d. follow the Code Load Regulator Center or Unit/

Load Regulator Sub Unit in the case of

synchronization and release of unit to/from

System, and change of loading to fulfill the

System requirement (in technical boundary of

equipments agreed on

e. each unit give contribution at quality control

of frequency and voltage (in boundary of unit

ability what the declaration

f. follow the Code Load Regulator Center or Load

 77

Regulator Unit/Sub Unit in activating or

killing function of Automatic Generation

Control (AGC) of Unit provided with AGC

g. maintain ability of black-start of unit having

facility black start. operator of the Unit must

be drawn up to conduct test of black start of

if asked by Load Regulator Center or Load

Regulator Unit/Sub Unit

h. for the unit expressed able to shoulder

separate load (isolated), follow the Code and

Load Regulator Center or Load Regulator

Unit/Sub Unit to participate in course of

recovery of System after trouble occurrence;

i. during trouble or emergency, avoiding release

of unit and System, except if provable that

serious damage will be became of by equipments

of generating of if do not is immediately

released and the System

j. Providing release of load of usage by itself

Generating Unit by rele is low frequency for

insignificant load in generating unit

k. Reporting to Load Regulator Center or Load

Regulator Unit/Sub Unit loading of daily

generator of hours period; and

 78

l. Providing medium of black start to quicken

process of system recovery

OC 1.6.6 Responsibilities of PLN Generating/Company of

Generating with Unit of Water Power in Security of

System of Generating of water power play role

important in operation of normal System through

ready of capacities of energy of regulation and peak

load/load taker. In a condition the emergency,

ability of generating of water power for started

quickly represent all important apparatus for Load

Regulator Center or Load Regulator Unit/Sub Unit to

overcome energy insufficiency. In a condition

extinguish total, ability of generating of water

power to shoulder separate load of vital importance

for starting step process cure. PLN

Generating/Company of Generating with unit of water

power hold responsible in

a. Giving service which is reliable as expressed in

purchasing and selling agreement of related

electricity power (PPA) Or provisions of

effective operation

b. Declaration of all changes in ability of

operation and characteristic which is from the

beginning expressed to P3B Sumatra

c. Coordinated activity of conservancy with Load

 79

Regulator Center or Load Regulator Unit/Sub

Unit

d. Following instruction Load Regulator Center or

Load Regulator Unit/Sub Unit in the case of

synchronization and release of unit to/from

System, and in the case of change of load

according to System requirement;

e. Each unit give appropriate contribution at

process of quality control of voltage and

frequency

f. follow the Code Unit or Load Regulator

center/Load Regulator Sub Unit in the case of

activating or killing function AGC generating

unit completed by AGC

g. follow the Code and Center Unit or Load

Regulator/Load Regulator Sub Unit to conduct

separate loading in total extinct condition

h. maintain facility black start ability (black-

start) unit having it. the Unit operator must

ready for doing/conducting test black start

according to the request Center Unit or Load

Regulator/Load Regulator Sub Unit

i. avoiding System and unit release, except if

provable that serious damage will be became of

 80

by the generating equipments of if do not is

immediately released and the System; and

j. submitting to daily loading report Load

Regulator Center have period to of clock and

the daily condition anticipate face irrigate,

incoming water and irrigate accumulating basin

exit

OC 1.6.7 Responsibilities PLN Generating/Small Unit

Generating Company for the security of System.

Small Generating as a whole give contribution

meaning in serving System load. At certain area of

small generating centers may also the playing

important role locally in taking care of service

reliability. PLN Generating/Generating Company with

small unit hold responsible in

a. giving service as stated in purchasing and

selling agreement of Electricity power of

agreement interconnection or

b. declaration of all changes in ability operation

and the characteristic which is from the

beginning expressed to P3B Sumatra

c. coordinated conservancy activity with Load

Regulator Unit/Sub Unit

d. follow the Code Load Regulator Unit/Sub Unit in

 81

the case of unit release and synchronization

to/from System, and in the case of loading

change according to requirement;

e. giving contribution at quality control of

voltage and frequency. In the case of induction

generator, maintain and operate facility

supplement energy reactive to fulfill the

System requirement

f. during trouble or emergency in System, avoiding

System and unit release of except if provable

that serious damage will be became of by the

generating equipments of if do not is

immediately released and the System; and

g. submitting to Unit/Sub units of daily loading

report Load Regulator have the period to clock

OC 1.6.8 Responsibilities PT PLN (Persero) Regional in System

Security

PT PLN (Persero) Regional of big sharing in taking

care of System security of because they control

better part of load and own and control most supply

energy reactive. PT PLN (Persero) Regional hold

responsible in

a. discharging load which have been determined

(predefined) for mandatory to protect System

 82

security by Unit or Load Regulator Center/Load

Regulator Sub Unit

b. maintain and operate equipments supplier energy

reactive to fulfill the energy reactive

requirement According to objectives specified

by a Unit or Load Regulator Center/Load

Regulator Sub Unit in all main power station

c. coordinated planning supply energy reactive

with Unit or Load Regulator Center/Load

Regulator Sub Unit is so that obtained by a

optimum combination between ‘Generating’,

‘transmission’ and ‘distribution’

d. determining cross distribution for the

automatic load release by rele of low frequency

of low and rele voltage at cross distribution

utilize to fulfill objectives specified by a

Unit or Load Regulator Center/Load Regulator

Sub Unit in order to minimization affect System

trouble time extinction and prevent the

happening of extinguishing total;

e. coordinated recovery of collective responsibility

Load Regulator Unit/Sub Unit after occurrence

of trouble and/or the energy insufficiency. Way

of recovery of load should not result the

happening of worse extinction and trouble

 83

f. managing interaction by PLN is

Generating/Company of Generating which unit of

its generating connected to distribution Grid;

and

g. providing forecast of load required in Grid

Code

OC 1.6.9 Responsibilities of Big Consumer in Security System

of Big Consumer as a whole represent very important

part of load of System and possibility of

representing dominant load in its area. Big consumer

follow playing a part in of responsibilities of

security of System with P3B Sumatra and User of

other Grid. Their responsibilities is

a. fulfilling objectives of load of energy of

reactive specified by P3B Sumatra or in

agreement interconnection

b. avoiding often change of load which quickly

causing flicker of voltage and impinge standard

of is set in Connection Code (CC 2.0 -

Characteristic of Grid Performance

c. free of load prepared to be broken

(interruptible load) if commanded by PT PLN

(Persero) Regional or the Load Regulator

Unit/Sub Unit
 84

d. installing and maintain equipments release of

automatic load by low frequency and/or the low

voltage, utilize to fulfill objectives

specified by P3B Sumatra in order to protect

System security; and

e. providing forecast of load required by Grid

Code

OC 2.0 Operational Reserve Margin

OC 2.1 Operation Reserve is

a. Rotated reserve, defined as total capacity of

energy of Generating which is made available

and is not encumbered, operating in System.

Generating which can be started and

synchronized to System during 10 minute and

load of interruptible which can be released

during 10 minute, depended and the option

selected by Load Regulator Center, can be

considered to be by a reserve rotate

b. Cool reserve, defined as generating which can

be started and synchronized to System during

four hours; and

c. Long-Range reserve, defined as generating which

can be started and synchronized by into time

more than four hours of but less and two-day

 85

OC 2.2 Margin Reserve (minimum requirement) must be made

available by any time a. Reserve rotate > capacities

unit of biggest generating is connected to System b.

Reserve rotate added by a cool reserve > two unit of

biggest generating is connected to System; and c. ‘

Rotated Reserve added’ cool reserve ‘ added ‘ long-

range reserve > two biggest generating is connected

to System added by margin reliability. Additional

margin of this reliability can be expressed in

percentage to daily peak load in MW; what its

calculation pursuant to study of energy do not be

served and/or loss of load probability. This

criterion must be re-evaluated and renewed

periodical to guarantee expense effectiveness

OC 3.0 Frequency Operation

Frequency in System will be constant if total the

well-balanced Generating totally is load added by a

Grid loss. If Generating exceed load added by a

loss, then frequency of System go up. If load added

by a loss exceed Generating, then frequency of

System descend. Span arrangement of tight frequency

needed to provide frequency of stable supply for all

User of final customer and Grid.

Frequency of System defended in range > 0,2 Hz

around 50 Hz, except in period of brief transient,

 86

where deviation amounting to > 0,5 Hz permitted, and

during emergency condition. operation of Frequency

reached by through:

a. action of governor of generating unit

(regulation primary

b. Generating Unit having automatic generation

control (secondary operation)

c. govern Load Regulator Center to Generating to

boost up or degrade point of setting governor

in anticipating load change

d. decreasing voltage in order to degrading System

load

e. mitigation in the manual

f. equipments release of automatic load by rele is

low frequency; and

g. releasing generator by more rele frequency

OC 3.2 Time Error

In order to providing indication of time which is

reliable for equipments of customer

counting/calculating hours of pursuant to frequency,

Load Regulator Center must be out for avoid time

error more than 30 second

OC 3.3 Action of Generating governor

 87

All Generating Unit must operate by governor is

which the block do not except permitted by Load

Regulator Center. All Generating Unit must tune

characteristic of droop governor do not exceed 5%

except permitted by Load Regulator Center to tune at

other level

OC 3.4 Generating Having Automatic Generation Control

(AGC).

Operator of Generating Unit having capable facility

of AGC at unit of its generating must immediately

follow the Code Load Regulator Center to activate or

kill AGC. Span arrangement and generating using AGC

must be taken care of by minimum amounting to 2,5%

and the System load. Load Regulator Center must

avoid reaching of boundary of operation of AGC at

condition of normal operation.

OC 3.5 Voltage Reduction To Lessen System Load

If Load Regulator Center contend that frequency have

or will descend under 49,7 Hz and reserve made

available to fall short to bring back frequency to

normal range, Load Regulator Center must inform

condition of emergency in System. In This Case Load

Regulator Center must command Load Regulator

Unit/Sub Unit and operator of Generating to lessen

voltage as explained in Connection Code (CC 2.0). If

 88

System have been cured to condition satisfactorily,

then Load Regulator Center must command return of

voltage to normal range

OC 3.6 Mitigation In Manual

If during condition of emergency Load Regulator

Center contend that frequency have or will descend

under 49,5 Hz and reserve of existing Generating

fall short to bring back frequency to normal range,

then Load Regulator Center must command to Unit/Sub

units of Regulator of Big Consumer and Load to the

free manual of load which is the including category

‘ can be broken’ (interruptible).

Load Regulator Center or Load Regulator Unit/Sub

Unit may also command release of load in manual in

area experiencing of very low voltage or when

threatened System experience of voltage problem

(voltage collapse

OC 3.7 Equipments of Release of Load Automatically by Low

Frequency

In order to guarantee balance of between load and

Generating in a condition emergency, at least 50%

and load of System must be controlled by equipments

release of automatic load by rele is low frequency.

Sensitive load what is specified by PT PLN (Persero)

Regional, may not the included in program of load

 89

release (load shedding) by rele low frequency.

Maximum ten step of load to release of the size

which is much the same to but is geographically gone

the round of must be provided and is always defended

by a Release load of first phase must be set at

frequency which enough lower so that escaping of

biggest generating in System will not cause to work

of the first phase. Last phase of release of load

must be set at above frequency of highest setting

under frequency and the generator completed by rele

low frequency, so that there no Generating Unit

escaped by before release load of last phase work

OC 4.0 Voltage Control

Taking care of voltage of System at on needed to

nominal level lessen loss of Grid and threat of

voltage collapse and problem of stability of

transient and steady state. Voltage control is also

needed to avoid damage of equipments connected to

transmission Grid, good by too high and too low

voltage, and to guarantee that voltage beside the

customer stay in level which can be accepted.

Others, imbalance of voltage and harmonics must be

controlled also to give service satisfactorily to

customer

OC 4.1 Voltage Control reached with step together with

 90

a. generator synchronize equipped by voltage

regulation. addition of Stabilization control

loops (Power System Stabilizer - PSS) at

voltage regulation repair stability of dynamic

and System

b. synchronous condenser

c. compensator VAR static

d. parallel capacitor (shunt)

e. reactor shunts; and

f. change of axle journal transformer

g. operation/release SUTT/SUTET Code-Oc)

OC 4.2 Load Regulator Center is responsible to specify

level voltage of safe operation for all Central

Power Station and to submit the information to

Generating and Load Regulator Unit/Sub Unit. Load

Regulator Center is responsible instruct operation

of System in such a manner so that voltage of System

stay in safe level. Operator and equipments of

controller of voltage as elaborated at OC 4.1 is

obliged to follow the Code Load Regulator Center to

operate the equipments. If any internal issue

fulfill this requirement must be reported to Load

Regulator Center or Load Regulator Unit/Sub Unit

OC 4.3 Voltage Imbalance

 91

Transmission Service Unit (UPT) is responsible

balance impedance of phase of Grid utilize to limit

voltage imbalance. All Grid User is obliged to

balance current of phase at connection point utilize

to limit voltage of negative sequence less and 1% as

determined in CC 2.1 (d)

OC 4.4 Voltage Harmonious of All Grid User must obey that

their contribution to distortion of harmonious at

point of their extension less and 3% as determined

in CC 2.1 (c)

OC 4.5 Blink and Flicker voltage of Blink of voltage of

because of starting motor must be limited by

amounting to 5% under normal stress at all of

Connection point. All Grid User must obey that their

operation do not cause flicker of voltage or blink

repeatedly exceeding boundary specified at CC 2.1.

If the boundary skipped over, P3B Sumatra and

Transmission Service Unit (UPT) is obliged to look

for cause of the problem and take necessary actions

to repair collision of this criterion.

OC 5.0 Protection Grid

Equipments Protection Grid and coordinate adequate

protection needed to protect Grid components and to

limit trouble impact of if happened by the

equipments failure or trouble. Requirement detailed

 92

visible at Connection Code CCAI 2.3 Equipments

Protection That Is Needed

OC 5.1 All Grid User must deliver scheme protection change

plan to P3B Sumatra to be learned and ratified

OC 5.2 Scheme protection Grid must give the possibility of

for Exploitation rating Thermal short-range the and

conductor equipments Central Power Station of if the

rating determinable

OC 5.3 If all or some of scheme protection fail or do not

work, P3B Sumatra must set mind on

a. extinguishing equipments which protected by the

scheme protection

b. letting fixture with voltage, without

protection primary of during specified period

of during protection reserve made available and

adequate; or

c. installing scheme protection whereas

OC 6.0 System Stability

System face some big trouble type related to

stability problem, including among other things

a. instability transient happened by if parts of

part and isolated not to dip and end in

breaking of System (generally in a few second).

Such trouble is generally happened by after big

 93

trouble short-circuit or escaping of some

generating unit

b. instability dynamic, where small oscillation do

not immersed happened which is early on the

score of ill defined, that is because System

operated by too close to unstable condition;

and

c. voltage instability, that is decline it.

voltage of lower System and level where

equipments of controller of voltage can bring

back voltage to level which can be accepted. In

the case of loss increase of energy of reactive

make worse problems so that extend and quicken

decreasing voltage of all System, aiming to

voltage collapse

OC 6.1 Coordination Analysis Stability

P3B Sumatra is responsible conduct or arrange its

well-held is study that is needed to determine

boundary of safe operation which can protect System

and threat of instability problem, including which

is because of credible outages. All Grid User is

obliged to provide data and information that is

needed to support the study

OC 6.2 Obligation of Operational of In The Case Of

Stability of Obligation of various party in

 94

concerned in operation of System to maintain

stability operation, among other

a. Load Regulator Center is obliged to operate

System in boundary of safe operation specified

by through periodic study on stability

b. PLN Generating/Company of Generating is obliged

to maintain equipments of controller of voltage

and appliance conduct other to guarantee that

support energy of full reactive (detail of

requirement relate to Connection Code) made

available by for System. PLN Generating/Company

of Generating also is obliged to maintain

ability of Generating of energy of reactive

according to design of equipments in any time.

Generating Unit may not be released and System

of during the happening of trouble of except

condition of frequency or voltage at that time

exceed or very less so that can destroy

equipments or if Load Regulator Center have

agreed doing/conducting of the release

c. PT PLN (Persero) Regional is obliged to look

after equipments of controller of voltage in

their installation so that equipments will work

is such as those which wanted to utilize to

support voltage of Grid of transmission and

 95

voltage of distribution Grid; and,

d. Big Consumer is obliged to look after all

voltage controller equipments required in

accordance with Agreement Sell Bell Electricity

so that equipments will work matching with

wanted to utilize to support System voltage of

during normal condition and the trouble

condition

OC 7.0 Emergency Procedure in System

Emergency at System assumed happened by if

a. Margin capacities System voltage or reserve

descend downwards the level which can be

accepted

b. trouble have caused separate System and/or

extinction of some of or total; and

c. storm, earthquake, riot etcetera menace System

security.

P3B Grid User and Sumatra is obliged to follow

procedure elaborated at OC 7.2 until OC 7.6 to bring

back System condition as soon as to safe condition

OC 7.1 Emergency Procedure Guide in System

Load Regulator Center must look after and distribute

a Emergency Procedure Guide of System together with

list rind of all party which must be informed by

 96

that System in a state of emergency, including

number phone on tasks and home phone and alternative

is forwarding of other if they are not in house. The

guide also must specify place where main worker must

go to report for the recovery execution

OC 7.2 Announcement of Power Insufficiency

Load Regulator Center must announce condition of

Lacking of Power if

a. reserve operation to decline under minimum

requirement and is not made available by a

energy to overcome it; or

b. reserve operation in, monthly plan estimated

will less and the minimum requirement and is

not made available by a energy to overcome it.

In last case, then Load Regulator Center must

announce condition of Power Insufficiency at

least one week before.

OC 7.3 Notification of Power Insufficiency

Immediately after Insufficiency of Energy announced,

Load Regulator Center must

a. informing PT PLN (Persero) Regional that have

been happened by insufficiency of energy and in

order to draw up release of load which can be

broken (interruptible-load) utilize to maintain

 97

level of reserve operation minimum. Level of

load of interruptible which must be released by

each PT PLN (Persero) Regional must pursuant to

objectives specified by Load Regulator Center.

The Objectives must be exploited proportional

with load joined by each PT PLN (Persero)

Regional

b. informing PLN Generating/Company of Generating

that have been happened or possibly will be

happened by insufficiency of energy and out for

to order to add energy made available in each

generating unit; and

c. informing Board Of Directors of PT PLN

(Persero)

OC 7.4 Announcement of Condition of Emergency in System

Load Regulator Center announce existence of

emergency condition when

a. reserve rotate in System descend to level under

minimum requirement

b. high loading at joint transmission, so that can

cause System instability

c. voltage of low System and can bring to

condition of voltage collapse and all existing

business have been conducted to overcome

 98

problem

d. trouble of Grid have caused breaking of System

and/or extinction of some of or total; or

e. according to consideration Load Regulator

Center, there is storm threat, earthquake,

fire, riot etcetera to System security.

OC 7.5 Emergency Notification in System

Immediately after emergency in System announced,

Load Regulator Center must immediately conduct

notification together with

a. informing all Grid User through facility

Operating Code (grid operations message system)

that in System have been announced

b. informing PT PLN(PERSERO) Regional, big of

mitigation that is needed (if (it) is true

requiring to

c. informing telephonic to Board Of Directors of

PT PLN (Persero); and

d. informing Head Load Regulator Center of on

storm existence, earthquake, fire, riot

etcetera so that importance of activating Space

Operation Emergency.

Notification must shortly and clear mention problem

that happened and the action expected and the

 99

notification receiver

OC 7.6 Space Operation Emergency

If Load Regulator Center conclude that in a

condition the emergency needed by a Space opening

Operation Emergency (ROD), Load Regulator Center

must contact party holding responsible listed in

Emergency Procedure Guide in System and ask

activating of ROD

OC 7.7 Emergency Training

Emergency Training must be done at least once in one

year to accustom all personnel holding responsible

in emergency procedure execution and the System

recovery procedure. Training Simulation must be

realistic emergency and follow the scent Emergency

Procedure. Evaluate to this training must be done

and lacking of in procedure and respond must be

identified and repaired

OC 8.0 System Recovery Procedure

All Grid User must follow guidance Center Unit and

Load Regulator/Load Regulator Sub Unit to ensure

that System recovery take place quickly, safe and

avoid problem which needn’t be happened

OC 8.1 Recovery Procedure and breaking of System (Island

Operation)
 100

In the case of one or more the stable operation

island have been happened, sequence together with

must be followed

a. Unit and Load Regulator Center/Load Regulator

Sub Unit must as soon as assess System

condition and determine level and nature and

the equipments facility damage. Grid

transmission User must assist to provide

information that is needed Center Unit and Load

Regulator/Load Regulator Sub Unit in making the

assessment

b. Stabilizing island apart at 50 Hz and

synchronize the island as soon as possible

c. Curing supply to all broken big generating

center/extinguish to start process. Unit

synchronization to System conducted by after

commanded by Unit or Load Regulator Center/Load

Regulator Sub Unit

d. generating Unit Shoe which do not operate which

is according to consideration Center Unit or

Load Regulator/Load Regulator Sub Unit needed

to facilitate recovery process. Electricity

Power System Grid Code Unit synchronization the

Sumatera to System conducted by after commanded

by Unit or Load Regulator Center/Load Regulator

 101

Sub Unit

e. generating Unit Shoe having black start ability

in extinctive area and synchronize the unit

when supply to Connection point center

Electricity have been cured and have been

permitted by Unit or Load Regulator Center/Load

Regulator Sub Unit to be synchronized

f. Boosting up energy go out Generating Unit

According to the instruction of Load Regulator

Center or Load Regulator Unit/Sub Unit. Require

to be paid attention to Code not to conduct

excessive loading at conductor and/or the

loading resulting condition of low voltage

g. Curing supply to watchman station of extinct

mains as soon as possible utilize to prepare

equipments for execution switching PMT. Need

special attention is not happened by the

voltage more which is because of current of

charging of when closing the joint long

transmission

h. Under guidance Load Regulator Center, Load

Regulator Unit/Sub Unit command PT PLN

(Persero) Regional to start recovery of cross

distribution to avoid loading more joint

transmission and condition of low voltage, and

 102

avoid descending of reserve rotate to level

which is not safe. After extinguishing

sufficiently long, is possible needed by

loading of cross step by step to avoid the

happening of load more at cross;

i. Avoiding to connect Generating Unit which

insulation to local load is which insulation of

except if not possible (to) synchronize

Generating Unit beforehand for stability of

island operation, and the unit have been

expressed able to shoulder separate load

j. Grid User which do not follow instruction of

Load Regulator Center and Load Regulator

Unit/Sub Unit of during process of recovery

must be given on to a enforcement process

(enforcement) as stated in GMC 5.0.

OC

8.2 Recovery Procedure of Total Blackout

Recovery of System after total blackout is much more

difficult process and takes longer time than partly

blackout. In case of total blackout, the following

measures shall be added to the recovery procedure of

partly blackout.

a. Generator Unit equipped with asut-gelap and

independent load pickup must be asut and followed by

 103

energizing process of conductor, energizing of relay

station and local load. This formed small island

must be expanded by adding local power station,

conductor, relay station and load. When expanding,

special attention must be paid to the avoidance of

voltage instability.

b. Following the formation of independent and stable

island, the islands must be expanded that the

islands, which were firstly separated, are

synchronized with the neighborhood island; and

c. As the duration and scope of total blackout is much

more than the partly blackout, unit loading must be

made periodically to avoid overload and made it

possible for loading stability. In addition, many

storage energy facilities at relay stations and

power center must be refilled prior to the operation

of those facilities.

OC

9.0 This part explains PTM switching procedures and release

of installation part to secure that work in transmission

network or at installation of Network’s User may be

safely done. This is applied if work and/or test to be

performed requires work and equipment safety coordination

between Load Regulator Center and Network User.

Further, this part also outlines the procedure line that

must be observed when maintenance and test activity will

 104

be conducted at transmission network by P3B Sumatra

and/or Network’ User in accordance with Working Permit

Process contemplated in OC 9.2.1.

OC 9.1 Work Safety Coordinator

Prior to energizing a new line point, every P3B Sumatra

and the relevant Network’s User must appoint a Work

Safety Coordinator and the alternative.

P3B Sumatra and the relevant Network’s User must mutually

notify in writing concerning the identity of the

appointed Safety Coordinator. In case of any intention to

replace the appointed Work Safety Coordinator, the other

party herein shall be notified in writing the identity of

new Work Safety Coordinator.

Work Safety Coordinator must be responsible for all

matters pertaining to safety covering connection points.

OC 9.2 Maintenance Procedure of High Voltage Device

A Working Permit Process has been specified to secure the

enforcement of maintenance procedure of high voltage

device. This process covers coordination between Load

Regulator Center, Load Regulator Unit/Sub-unit, work

safety personnel and maintenance personnel, and transfer

of authority from one group to other group during the

maintenance activity and testing through the use of

working permit special form. Load Regulator Center issues

working permit for work of 275 kV and Load Regulator

Unit/Sub-unit issues working permit for work of 150 kV

 105

and 66 kV.

O]C 9.2.1 Work safety procedure in relation to the network

maintenance of 66 kV, 150 kV and 275 kV is

described in the document “Work Performance

Procedure at High/Extra High Voltage Electric

Installation” applicable in Sumatra System.

Every periodic maintenance work resulting in a

blackout must be informed to the relevant Network

User at the latest one week prior to the work done.

Working Permit Process for High Voltage Device

Maintenance must cover the following steps:

a. The process is started from application for

working permit form addressed to the Load

Regulator Center or Load Regulator Unit/Sub-unit

for maintenance or certain test.

b. Load Regulator Center or Load Regulator

Unit/Sub-unit shall learn the maintenance

schedule in its relation to the “switching of

PMT” and reconfiguration of transmission network

to ensure that the reliability and security

level will remain secured. If the schedule is

deemed qualified, the Load Regulator Center or

Load Regulator Unit/Sub-unit shall issue the

requested working permit;

c. Load Regulator Center or Load Regulator

Unit/Sub-unit will specify the maneuver of “PMT

 106

switching” required to shutdown part of the

maintenance workplace network or of the testing

to be done.

d. Personnel of Transmission-Service Unit (UPT)

fills the relevant part of Work Schedule Form,

then send it to Work Safety Coordinator for

approval, and to the responsible operator of

relay station to separate and ground the device.

e. Relay station operator fills the relevant part

of the Working Schedule Form and sent it to the

maintenance staff that will be responsible for

work performance.

f. Relay station operator then performs local

grounding and installs necessary signs at

switching device.

g. Maintenance staff will conduct maintenance work;

h. Maintenance staff fills the relevant part of

Working Schedule Form and returns it to the

relay station operator. The operator then is

responsible for releasing signs of the switching

device, uncovering the grounding and covering

the separator.

i. Work Safety Coordinator will ratify the

completion of Relay Station Operator activity

and returns Work Schedule Form to Transmission

Service Unit (UPT), stating that the work has

 107

been completed and energizing of device was

executable. Personnel of Transmission Service

Unit then notifies the Load Regulator Center or

Load Regulator Unit/Sub-unit that the device is

operable; and

j. Load Regulator Center or Load Regulator

Unit/Sub-unit leads the maneuver of PMT

switching to re-energize the facility and

reconfigure the transmission network for its

reinstatement.

OC 10.0 Liaison Operation

This part provides the outlines of general

procedures of coordination and exchange of

information between the relevant parties with

interconnection to the System.

OC 10.1 Requirement to Inform on Operation

P3B Sumatera is responsible for specifying safe

operational level for all System facilities and

communicating the information to internal division

of P3B Sumatera and to PLN Power Station, PT PLN

(Persero) of Regional and Major Consumer that are

connected to the transmission network. P3B Sumatera

must provide information regarding activity or

condition of operation that affects the security and

reliability of the System to the relevant parties.

The relevant parties with the interconnection are

 108

responsible to inform P3B Sumatera any planned event

that has impact on normal operation of each of part

of the System.

If the Load Regulator Center is notified on

operation or any potential event that affects other

Network User, then the Load Regulator Center is

obliged to inform the Network User.

When receiving the notice on the operation or event,

the receiver may contact the Network User who issues

the notice for clarification and the Network User

must:

a. provide the answer; and

b. circulate the copy of question and answer to all

receiving news.

OC 10.1.1 The operation to be reported includes but not

limited to:

a. Taking out of power generator and/or

distribution device of the System operation for

maintenance or testing that might reduce the

reliability of the System;

b. Testing to the generator unit device should not

make the service stopped.

c. Operation of power breaker, separator or

grounding device that has not obtained permit

from Load Regulator Center or Load Regulator

Unit/Sub-unit; (in certain case, the operation

 109

of device should be performed regardless the

permit for the purpose of protecting personnel

or the device; in that case the operation and

the causal factors must be reported to Load

Regulator Center or Load Regulator Unit/Sub-unit

immediately);

d. Any kind of sudden and non-standard operation,

except under permission of Load Regulator Center

or Load Regulator Unit/Sub-unit; and

e. If operation problem could not be solved soon,

the estimated length of the resolution and the

potential impact must be reported.

OC 10.1.2 Necessary notice for the fulfillment of OC 10.0

must contain the detailed operational description

in order the receiver will be capable of evaluating

the operation and the impact. The notice must

contain name and phone number of personnel

reporting to the operation and the receiver of the

news may ask question for explanation. The notice

must be presented as early as possible.

OC 10.2 The Interest of Load Regulator Center to Notify the

Network’s User regarding the Event of the System

The Load Regulator Center shall be responsible to

present information of events at the System to the

Network’s User affected with the event. The Load

Regulator Center as the System Operator must supply

 110

information of the events that have impacted the

reliability of the System to the affected Network’s

User.

All Networks’ Users are required to inform the Load

Regulator Center or Load Regulator Unit/Sub-unit

regarding the unexpected event that has or might

have impact on the normal operation of part of the

System. If necessary, Load Regulator Center as the

System operation must investigate the unscheduled

events together with the reasons thereof.

OC 10.2.1 The report of event and answers on all questions

regarding the event may be presented orally which

will then be followed up in writing. The written

report shall contain:

a. name, position and organization of the personnel

that issues the report and the date and time of

the issuance;

b. implication and operational risk that might

arise of the event in details, so that the

receiver is enable to analyze it; and

c. when an event has instigated an accident to a

personnel, the details of the accident and the

impact thereof.

OC 10.2.2 Event that must be reported includes but not

limited to:
 111

a. failure or error of operation of the controller,

communication, measuring device and capability

alteration of electric center facility and the

conductor;

b. time of a power station or the device is

operated over the capacity;

c. climate condition that impacts on or might

affect the operation.

OC 10.2.3 If report of event is provided verbally:

a. the report must be dictated by the sender to the

receiver; and

b. the receiver must record and repeat any word at

the time of receiving and all reports fully, the

receiver must reread all reports to the sender

for accuracy confirmation.

OC 10.3 Milestone

Milestones are events to which the evaluation of

Load Regulator Center or Lead Regulator Unit/Sub-

unit has significant impact on the System.

In addition, milestone also covers events which are

convinced by the Network User to have significant

impact on its facility. Reporting of milestones

must be in writing in accordance with OC 11.0.

OC 10.3.1 Events that need to be reporting in writing to the

Load Regulator Center or Lead Regulator Unit/Sub-

unit are the causal factors, but not limited to:

 112

a. Instability of system;

b. Deviation of frequency beyond the specified

limit;

c. Consumer load blackout due to operation.

OC 10.4 Operational Communication Facility

All interconnected parties to the System must

provide and maintain main communication facility

and the reserved required, amongst other things:

sound, operational data and communication of SCADA.

OC 10.4.1 Operational communication Facility

a. The Network’s User must establish a

representative office for operational

communication with respect to its facility. The

office is responsible for operation and

maintenance of communication means; and

b. Representative office must provide the following

information:

i. name of the liaison personnel;

ii. phone number of that personnel;

iii. e-mail address of the personnel

iv. facsimile number and the facility; and

v. the location facility

OC 10.4.2 The following is minimum provision in relation to

the record of operational communication:

a. Load Regulator Center or Lead Regulator

Unit/Sub-unit must immediately record any

 113

telephone operational communication in writing

in the log book or other auditable permanent

method following the making or receiving an

operational communication.

b. Load Regulator Center or Lead Regulator

Unit/Sub-unit shall use reliable sound recording

to record conversations between dispatcher and

operational personnel of Network’s user.

c. Operational communication record must cover time

and content of every communication and shall

provide identity to any communicating parties;

d. Except communication requiring quick response,

the receiver must record and repeat any words at

the time of receiving and rereading to the

dispatcher all reports that he received for

accuracy confirmation.

e. Dispatcher shall keep all operational

communication records including the sound

recording, at least for five years for written

recording and one year for sound recording

between dispatcher of Load Regulator Center or

Lead Regulator Unit/Sub-unit, relay station

operator, power unit operator. This record is

kept and maintained for dispute settlement

material and evaluation of operational

 114

procedure, both for normal operation, emergency

and recovery process of the System.

OC 10.5 Meeting of Network Operator Coordination with the

Network’s User.

a. Coordination meeting between the Operator and

Network’s User at the working area of

Transmission Service Unit (UPT) shall be held on

monthly basis. This meeting is not required for

Major Consumer.

b. Coordination meeting between the System Operator

and Network’s User in working area of regional

PT PLLN (Persero) shall be held at least once in

a year, be obliged to be attended by Major

Consumer.

OC 11.0 Reporting of Event

Milestone covering accident or extraordinary event

that has impeded the operation of System or has

caused or in fact may generate damage to the device

or blackout shall be analyzed together by P3B

Sumatera and the affected Network’s User. The

analysis shall be conducted ultimately to add the

knowledge of the Network’s User regarding the

System operational characteristic so that the equal

event might be prevented in time to come. The

result of analysis must be made available for all

affected Network’s Users.

 115

OC 11.1 Reporting Procedure of Event

Based on the seriousness level and length of an

event or milestone, the relevant Network’s User

with the event must promptly provide a written

report including the additional detail of

conditions in where the event occurs, complete any

possible verbal report that might have been

presented.

The relevant Network’s User with a milestone must

provide written report after the event. A Draft

preliminary repot shall be delivered as soon as

possible, but not less than four hours after the

event. The report shall at least contain necessary

information set forth in OC 11.2. Within not more

than 24 hours, the Network’s User shall submit a

final written report on the event.

OC 11.2 Written report of Milestone

Written report of milestone shall cover, but not

limited to the following information:

a. time and date of event;

b. description of event;

c. duration of event;

d. specific device (including System controller and

protection means) that is directly involved in

the event;
 116

e. Number of (in MW and MWh) load and/or blackout

power; and

f. Estimated time and date of service recovery and

estimated schedule of follow-up that must be

made for avoidance of the same occurrence.

OC 11.3 Milestone Review

a. P3B Sumatera may conduct a review on an event or

operational condition in the System for the

purpose of feasibility of operational procedure

and Network Code to maintain the acceptable

reliability level of the System.

b. All Network’s Users must cooperate with P3B

Sumatera in the review or analysis of an event

at the System or operational condition of the

System, including the supply of the relevant

record and information; and

c. All Networks’ Users shall provide information to

P3B Sumatera with respect to the performance of

their device during and after an event or

operational condition as P3B Sumatera requires

it to analyze and/or report the event or

operational condition.

OC 11.4 Inspections and Access

a. P3B Sumatera may inspect all devices of

Network’s Users that are connected to the

Network for the purpose of:

 117

i. analyzing the fulfillment of operational

obligatory of all Network’s Users that

are interconnected to transmission

network in line with the Network Code;

ii. Investigating any threat or something

that might happen to the System security;

or

iii. Analyzing the performance of periodic

training with respect to the operational

need of devices.

b. P3B Sumatera shall notify at least two days

before the intention of the investigation. The

notice shall cover the details of:

i. name of the representative who will

conduct the investigation in the name of

P3B Sumatera;

ii. time when the investigation is made and

the estimated time of investigation; and

iii. the reasons of investigation (in

details).

c. P3B Sumatera may not conduct an other kind of

inspection for the purpose of analysis of

Network’s User compliance with the operation set

forth in Network’s User within 6 (six) months

after the previous inspection, except any non-

compliance that is found beforehand;

 118

d. P3B Sumatera shall ensure that inspection is

conducted as per required, and it takes not more

the two days;

e. P3B Sumatera shall ensure that the inspector

representative is qualified thereto;

f. All Network’s Users shall allow the

representative of P3B Sumatera to enter the

premises for the inspection;

g. During an inspection of a facility, P3B Sumatera

must certify that its representative:

i. will not case damage to the device of

Network’s User connected to the Network;

ii. Except otherwise set in Network Code,

ensure that the placement of storage of

device, vehicle or material shall only be

provisional;

iii. only inspect the operational of Network’s

User device that is connected to the

transmission network if deemed necessary

and approved by the Network’s User (the

approval shall be not be unreasonably

withheld);

iv. observe the interest of Network’s User in

relation to physical activity, work

health and safety as well as matters

pertaining labor mattes; and

 119

v. follow all protocol rules to enter the

installation of Network’s User, if such

protocol rules are not intended to

suspend any approval for the access.

h. All Networks’ Users shall appoint an authorized

personnel to accompany and observe the

inspection conducted by representative of P3B

Sumatra in the installation area of Network’s

User.

OC 12.0 This part specifies testing procedure and

activities, monitoring and in section in relation

to the following parameters:

a. performance of certain power station unit;

b. inspection to test the conformity of Network

Code and the relevant connection agreement;

c. test for verification of performance of

Controller System and protection both at

Network’s User device and P3B Sumatera device

with respect to a connection point.

d. Installation of test device to monitor the

Network’s User device performance in normal

operation condition;

e. Test of device requiring temporary blackout of

device or operation of the device by different

method of the normal operation condition; and

 120

f. Test as P3B Sumatera and Network’s User request

to.

OC 12.1 Testing

This part presents the vesting in equal right to

P3B Sumatera and Network’s User for mutual testing

of other’s device with respect to connection point

of P3B Sumatera and Network’s User device.

a. in case a connection point, the party believing

that a device operated by other party is likely

unqualified for Network Code, may suggest a test

to the device upon written notice thereof;

b. if such notice set out in letter (a) has been

given, the suggesting party shall conduct a test

on agreed time by the owner;

c. both parties shall cooperate for the test

referred to in letter (a):

d. cost of test set out in letter (a) shall be

borne by the suggesting party, except of the

test result indicates that the device is

unqualified for Network Code. If so, alls cost

of test shall be borne by the owner;

e. cost of test is excluded cost of damage due to

non-sale energy but P3B Sumatera is obliged to

minimize such damage during the testing process.

Load Regulator Center of Load Regulation

Unit/Sub-unit shall not make any deduction on

 121

the preparation of power station that is

declared as the consequence of the test;

f. test described in this part shall be conducted

using testing procedure that both parties agree

to. The parties may not suspend unreasonably the

approval of testing procedure. However, if the

parties disagree with the testing procedure,

then upon good utility practice basis, the

suggesting party shall specify the testing

procedure;

g. The suggesting party shall convince the owner

that only skilled and experience personnel is

allowed to conduct the test;

h. The testing personnel shall firstly notify Load

Regulator Center of Load Regulation Unit/Sub-

unit regarding the purpose of testing and only

conduct the test on the time approved by Load

Regulator Center of Load Regulation Unit/Sub-

unit;

i. The non-testing personnel shall appoint its

representative to witness the test and the

testing party shall allow the representative to

be present at the time of the test is being

conducted;

j. The testing personnel shall submit the testing

results and other relevant reports to the other

 122

party after the test period is over, within

proper period of time;

k. The testing party may mount test device (and/or

monitoring device) to the equipment operated by

the other party or ask other party to install

test device (or monitoring equipment); and

l. The monitoring party as part of a test shall

ensure that the monitored device performance

shall all the time be in accordance with the

Network Code and the relevant connection

agreement.

OC 12.2 Test of Electric Power Station

Test for power station performance may be

conducted:

a. at any time, upon the proposal of Load Regulator

Center of Load Regulation Unit/Sub-unit to

confirm the operational characteristic of power

station, except any specific impediment;

b. if based on the monitoring of certain power

station performance by Load Regulator Center of

Load Regulation Unit/Sub-unit is deemed that the

power station unit can not be operated in line

with the declared operational characteristic

including the capability for asut-gelap, load

pick-up, frequency support function and voltage;

or
 123

c. if based on the monitoring result of certain

power station unit performance by Load Regulator

Center of Load Regulation Unit/Sub-unit is

deemed that the power station unit can not be

operated in line with the declared operational

characteristic including the capability for

asut-gelap, load pick-up, and frequency support

functions and voltage; or

d. If PLN Enterprise requests for test to its power

station unit after a renovation done on damage

that generated a change of the declared

operational characteristic. In this case, a test

must be witnessed by representative of Load

Regulator Center of Load Regulation Unit/Sub-

unit in order the test is legally done to revise

the declared operational characteristic.

OC 12.2.1 Test Procedure and Power Station Unit Monitoring

PLN Enterprise may ask a test request for a power

station unit in writing to the Load Regulator

Center of Load Regulation Unit/Sub-unit which

contains as follows:

a. date of request;

b. earliest date of test begins; (the earliest test

date is 5 (five) working days after the date of

request);

c. name of identification of power station unit;

 124

d. operational characteristic to be tested;

e. value of operational characteristic to be

verified through the test; and

f. specific load condition for the test.

If the System condition is impossible to test based

on the requested schedule, the Load Regulator

Center may reject the schedule after consulting

with the Network’s User, to reschedule the test.

The Load Regulator Center of Load Regulation

Unit/Sub-unit may any time conduct test to one or

combination of several operational characteristic

of a power station unit. However, the Load

Regulator Center of Load Regulation Unit/Sub-unit

is not allowed to conduct a test to a power station

unit more than two times within a year if the

following events occur:

a. test result indicates that value of one or

number of operational characteristics is not in

line with the declaration of PLN Enterprise

(regardless whether the previous test is

designed for the operational characteristic or

not); or

b. System condition requires a test to be stopped

and such condition is mutually agreed that the

occurrence is unpredictable by Load Regulator

 125

Center of Load Regulation Unit/Sub-unit (in

this case the test result is deemed none).

During the monitoring to the test, Load Regulator

Center of Load Regulation Unit/Sub-unit shall have

record of power station unit performance in such a

way that is enabling to conduct independent

verification thereof. In addition, if the response

of power station unit requires a test to the

frequency or voltage of the System, the Load

Regulator Center of Load Regulation Unit/Sub-unit

shall keep the records of the quantity of frequency

or voltage that were monitored during the test.

Load Regulator Center of Load Regulation Unit/Sub-

unit at any time may monitor (using SCADA data) the

performance of power station unit by comparing the

actual output (or response) with the output (or

response) that should be reached in line with the

declared operational characteristic.

If through a test or monitoring to the power

station unit performance, the Load Regulator Center

of Load Regulation Unit/Sub-unit specifies that the

tested power station fails to meet the declared

operational characteristic, the Load Regulator

Center of Load Regulation Unit/Sub-unit shall

notify PLN Enterprise regarding such failure,

including the details of test and monitoring

 126

results.

Upon the receipt of such notice, PLN Enterprise

shall immediately inform the Load Regulator Center

of Load Regulation Unit/Sub-unit:

a. explanation of the failure;

b. suggested revision of the unmatched operational

characteristic as prerequisite in the Operation

Schedule and Implementation Code (SDC); and/or

c. suggested schedule to cope with the problem.

Load Regulator Center of Load Regulation Unit/Sub-

unit and PLN Enterprise shall seek to come to terms

on the suggestion of PLN Enterprise regarding the

revision of the declared Operational Characteristic

value. If an agreement is reached, PLN Enterprise

shall declare the revised values, otherwise, Load

Regulator Center of Load Regulation Unit/Sub-unit

shall schedule retest and both parties must

acknowledge the results of retesting.

OC 12.3 Protective Device Test

a. at the latest on 31st July every year, P3B

Sumatera shall present to every Network’s User a

realization report of the preceding year

detailing the network performance at every

connection point of Network’s User, including

the comparison with a benchmark performance of

agreed comparison party.

 127

b. For every connection point, both P3B Sumatera

and Network’s User shall check and/or test the

operation of protection device with respect to

the connection point prior to the new initial

operation date and then on every once in two

years thereafter.

c. The Network’s User connected to a connection

point shall cooperate with P3B Sumatera for

inspection or test on the operation of

protection device;

d. Every Network’s User shall bear cost of test

described herein except otherwise specified in

Purchase and Sale Agreement or Interconnection

Agreement.

OC 12.4 Test of Network’s User Device

Every Network’s User shall obtain approval from

Load Regulator Center of Load Regulation Unit/Sub-

unit to conduct a test to its device that:

a. impact on the reliability of System operation;

b. threatens the System security;

c. requires specific System operation; or

d. will affect the normal electric measurement at

the connection point.

OC 12.5 Notice of Test

Network’s User suggesting a test on its device in

relation to a connection point shall inform the

 128

same in writing to Load Regulator Center of Load

Regulation Unit/Sub-unit at the latest 5 (five)

working days before. Such notice shall contain:

a. details of suggested test schedule;

b. estimated time for suggest test;

c. Identification of tested equipment;

d. System condition required to be tested;

e. Details of possible impact of the suggested test

to the System; and

f. Name of responsible person to coordinate the

suggested test in the name of the Network’s

User.

If system condition is impossible to make a test as

per the schedule, the Load Regulator Center shall

consult with the relevant Network’s User for

rescheduling.

Load Regulator Center of Load Regulation Unit/Sub-

unit shall notify other Network’s Users that are

likely affected with the suggested test and

consider the interest of other Network Users in

giving the approval thereto.

Network’s User intending to conduct the test shall

ensure that the responsible person in coordinating

the test shall obtain reconfirmation from Load

Regulator Center of Load Regulation Unit/Sub-unit

prior to the test is done.

 129

The responsible person coordinating the test shall

also immediately inform Load Regulator Center of

Load Regulation Unit/Sub-unit if the test is over.

OC 12.6. Inspection and Access

This part explains the situations in where:

a. P3B Sumatera may enter the installation premises

of Network’s User for inspection or test;

b. Network’s User may enter installation premises

of P3B Sumatera; and

c. Procedure and obligation are related to the

entry of premises and inspection of

installation.

OC 12.7 Right to Inspect

a. This Part vested in equal right to P3B Sumatera

and Network’s User to mutually inspect the other

party’s device at the connection point. Right to

inspect shall be valid for making an effort to

convince the suitability of device with the

Code;

b. If the inspecting party considers that the other

party fails to comply with the Network Code and

that the inspecting party will be or possibly

might be the victim thereof, then the inspecting

party may enter the installation premises of the

other party for an inspection;

 130

c. The inspecting party intending to inspect the

other party’s device shall notify the said party

at the latest five days beforehand the intention

of the inspection;

d. For validity, notice in line with letter (c)

shall cover the following information:

i. name of the representative inspector

acting on behalf of the inspecting party;

ii. time of inspection to start and estimated

inspection time to end; and

iii. property of unsuitability of device

against the Code that is suspected by thee

inspecting party.

e. The inspecting party may not conduct an

inspection within six months after the prior

inspection except for verification of device

performance of the correction act result done to

remedy the unsuitability with the Network Code

found during the previous inspection.

f. The inspected party shall appoint a competence

personnel to accompany the representative

inspector who enters its premises;

g. The inspecting party shall confirm that the

inspection shall be completed within two days.

If longer time is needed, both parties must be

mutually agreed thereof;

 131

h. The inspecting party shall ensure that the

representative it was appointed shall be capable

of doing the inspection; and

i. Cost of inspection shall be borne by the

inspecting party except any deficiency is found.

In this case, cost shall be borne by the party

suffering from this deficiency.

OC 13.0 Numbering and Naming of Device

A uniform approach to identify the device with

respect to the facility and equipment in the System

shall be specified in this Network Code (see

Appendix 3 in Connection Code) to minimize

operation fault due to misunderstanding on order in

operating certain device in the System.

OC 13.1 Application

Uniform Identification Code (see CCA3) is applied

to P3B Sumatera and Network’s User. The element of

Uniform Identification Code covers:

a. geographic location of device (with respect to

the Load Regulator Unit/Sub-Unit;

b. code of power station and relay station names;

c. code for voltage level;

d. code for specific component; and

e. code fro other specific usage;

Appendix 3 in Connection Code contains the details

of Uniform Identification Code.

 132

OC 14.0 Rating of Device

All devices of conductor and relay station at the

System shall have specified and recorded normal and

emergency loading limit. In addition, Constanta of

short-term thermal time and method of loss of life

analysis is applicable to specify the rating of

device of the analysis is made in line with the

electricity power standard and the approval of

device manufacturing.

Rating of conductor of air channel type must

consider the minimum limit of conductor and reality

maximum environment temperature as well as input

and sun radiation.

 133

Scheduling and Dispatch Code – SDC

SDC 1.0 Basic Principle

SDC 2.0 Long-term Operational Scheduling

SDC 3.0 Monthly Schedule

SDC 4.0 Weekly Schedule

SDC 5.0 Daily Dispatch

SDC 6.0 Real-Time Operation and Re-dispatch

SDC 7.0 Power Station Load

SDC 8.0 Pos-operation and Evaluation Activity

SDCA1 Appendix 1: Load Prediction

SDCA2 Appendix 2: Maintenance Schedule

SDCA3 Appendix 3: Declaration of PLN Enterprise

SDCA4 Appendix 4: Dispatch Orders

 134

Scheduling and Dispatch Code

Scheduling and Dispatch Code explains the rules and

procedures for transaction and allocation of power

station plan, amongst other things cover:

a. Long-term Operational Schedule for every 6

months with planning horizon of 1 year;

b. Monthly Schedule;

c. Weekly Schedule

d. Daily Dispatch

e. Real Time for Re-dispatch

SDC 1.0 Operational Schedule preparation needs information

on estimated power station preparation (covers

rotation reserve and cool reserve) and estimated

load need.

Procedure that is set in this SDC is for making

operational scheduling that:

a. consolidate information on estimated load and

preparation of power station, including the

proper operational margin;

 135

b. provide opportunity to outage of power station

and transmission by considering economic

condition of operation of the System and the

interest to keep the stability of the System;

c. optimum operation of hydro and thermal power

station is made possible by considering the

fuel, environmental limit and compliance with

needs of water for irrigation; and

d. assist and identify and accomplish operational

problems.

Procedures of more detail load estimation as

described in Appendix 1-SDC.

Procedures for more details of maintenance schedule

described in Appendix 2-SDC.

Procedures of declaration of more detail power

station characteristic described in Appendix 3 –

SDC.

Details of Dispatch Order described in Appendix 4-

SDC.

SDC 2.0 Long-term Operational Schedule

Long-term operational schedule shall be prepared by

Load Regulator Center at the latest 15th December

for the next coming one year. This operational

schedule shall cover the following information:

a. estimated monthly allocation of net production

of power station and loading rate of the System;

 136

b. outages schedule of power station unit;

c. monthly operation of reservoir (PLTA) by

attention paid to the environmental condition

and irrigation need;

d. projected energy price;

e. estimated non-served energy;

f. allocation of minimum energy offtake from take-

or-pay contracted power station;

g. specification of permanent transmission

impediment; and

h. allocation of proper rotation reserve and

cooling reserve level and monthly reliability

rate in line with the reliability margin set out

in Operational Code (OC .2.2).

This mid-year revision on long-term operational

schedule shall be issued on 15th June. The revision

must cover the remaining current year activity.

Estimation of the System performance covering

voltage quality and disturbance of each relay

station for next coming one year shall be issued by

P3B Sumatera on 15th December every year and the

revision shall be published on 15th June.

SDC 2.1 Long-term Operational Schedule Procedure

Load Regulating Center shall schedule the System

operation to obtain power station condition at

least cost in the fulfillment of predicted load

 137

with due observance to the network impediment and

service quality standard.

Network impediment and network configuration as per

specified by Load Regulator Center is based on the

power flow study, shot-circuit and stability.

Regional PT PLN (Persero) shall present the

predicted load of each relay station for the next

coming one year at the latest 1st September and the

revision is on 1st March of the following year.

SDC 2.2 Long-term Operational Schedule Draft

Load Regulator Center shall publish long-term

operational schedule draft at the latest 1st October

every year. In the draft is contained information

of the monthly need of power station with weekly

details thereof. Load Regulator Center shall

provide information to all Network’s Users. Mid-

year revision on the long-term operational schedule

draft shall be at the latest after the issuance on

1st April of the following year.

SDC 2.3 Maintenance Schedule

Based on the long-term operational schedule draft,

PLN Enterprise shall deliver the maintenance

schedule draft of power station unit for the period

of 1 coming year to the Load Regulator Center with

the suggested date and period of maintenance of

unit at the latest on 1st September.

 138

Based on the maintenance schedule proposal of the

power station unit, the Load Regulator Center shall

prepare the final maintenance schedule of all power

station units and the relevant transmission

facilities, and must be delivered to all Network’s

Users at the latest 15th December.

Final maintenance schedule may change the outages

maintenance date of power station unit within

proper limit of time, but the period of maintenance

can not be shortened without an approval of the

owner.

PLN Enterprise shall deliver any change of revision

in the mid-year maintenance schedule at the latest

1st April. Load Regulation Center shall have

published the Revised Maintenance Schedule at the

latest 1st June.

SDC 2.4 Study of Electric Power System

The purpose of this study described in this chapter

is to evaluate all impediments in the network and

power station margin that needs to be considered in

monthly, weekly and daily operational schedule.

Long-term operational schedule shall engage studies

on power System as follows:

a. study on power current and stability to

determine the current limit at the transmission

 139

and the need of load and automatic load

blackout;

b. short-circuit analysis to specify the suitable

network configuration;

c. specification of reliability margin buildup in

accordance with code set out in OC 2.2, so that

the margin can be determined by considering

estimated un-served energy and load loss

probability (LOLP) is still within the permitted

operational scheduling standard.

SDC 2.5 Long-term Operational Schedule

Upon the receipt of long-term operational schedule

draft, the maintenance schedule and study on

electric power System, the Load Regulator System

shall prepare final long-term operational schedule.

This schedule shall have been received by all

Network’s Users at the latest 20th December and the

mid-year final revision shall be on 15th June of the

next coming year.

The purpose of monthly schedule is to schedule

operation of all power stations, transmissions and

relay stations including the outages schedule.

Power generating schedule shall be capable of

fulfilling the estimated needs of the System with

minimum variable cost and considering the

reliability criteria and electric power System

 140

quality (grid).

SDC 3.1 Monthly Schedule Process

Monthly schedule process is used to meet the need

of electric generator that is not made available by

basic-load thermal generator, renewable energy,

run-of-river and must-run unit. The need of

information for monthly schedule shall be received

on:

a. the 5th day of the current month – PLN Enterprise

shall present the readiness of power station

unit and the maintenance date for the next

coming one month;

b. the 10th day of current month – Load Regulator

Center shall provide the estimated need of

electric generator for the next coming one

month;

c. the 15th day of current month – PLN Enterprise

shall provide information on energy variable

cost to the Load Regulator Center to be used in

economic energy allocation for the next coming

one month;

d. the 20th day of current month – Load Regulator

Center shall make capacity and energy purchasing

schedule for the next coming one month.

SDC 3.2 Economic Criteria for Monthly Schedule

Economic criteria for allocation of generating unit

 141

load in monthly schedule are based on:

a. energy production of generating unit that must

be operated is due to the System impediment as

per required;

b. energy production that is committed by PLN

Enterprise on condition that the minimum offtake

to the electric generating under take-or-pay

contract.

c. Energy production that is committed by PLN

Enterprise for Renewable Energy;

d. Variable cost of power station under power

purchase agreement (PPA); and

e. Variable cost of power set out in the monthly

schedule for non-committed portion of power

station center in the PPA purchase contract.

Load Regulator Body shall schedule the operation of

all power station units in the System to fulfill

the estimated load with minimum cost (variable cost

+ outage cost) by considering reserved margin as

defined in the long-term operational schedule. If

the readiness of power station is insufficient to

supply load with the required reserved level, the

Load Regulator Center shall make operational

schedule to minimize blackout risk.

Load Regulator Body shall obtain up-to-date

information from Network’s User regarding the

 142

readiness of power station unit, reservoir surface

water estimation, estimated water debit into the

reservoir and estimated production of PLTA run-of-

river. Network’s User shall provide the information

by using a form set out in Data Requirement Code

(DRC). Additional information in relation to the

testing and commissioning must also be made

available by Network User using the form set forth

in the Date Requirement Code (DRC).

a. estimated energy production of each PLTA

reservoir by considering the non-electric need

and other environmental obstacles;

b. estimated energy production of PLTA run-of-

river;

c. estimated energy production of PLN Enterprise

using the renewal energy;

d. list of thermal power station that is

estimated to make start-up or shut down in

weekly period following merit-order in the

relevant month and the estimated energy

production;

e. list of power station center as cooling

reserve in the relevant month; and

f. un-reserved energy estimation and/or lower

reserve margin.

Minor correction to maintenance schedule can be

 143

made at this time, but the same shall be approved

by each of Network’s User and Load Regulator

Center.

Monthly schedule must be capable of fulfilling the

following purposes:

a. optimum of start-up and shut down of basic load

thermal power station in weekly period,

estimation of operation whether the power

station operates constantly or only five working

days or blackout for the week;

b. allocation of PLTA reservoir generating within

weekly period by considering the need of water

for non-electric and other impediment;

c. regulation of fuel supply obstacles;

d. entry of testing schedule of new power station

operation;

e. specification of need to operate power station

that must-run and non-economic to produce

reactive power in the framework of maintaining

voltage or protecting an area;

f. allocated rotation service, secure that the

reserve shall be ready for use;

g. allocated minimum generating for each area to

secure the continuity of service in case of

disturbance on the imperative transmission, and

the separation of the System; and

 144

h. specification of maintenance schedule of

transmission for the next coming month.

SDC 3.3 Monthly Schedule Procedure shall cover:

a. consideration of transmission barrier due to

non-readiness of transmission device, voltage

regulator or compensator;

b. estimated revision of inlet water debit, as

informed by PLTA;

c. estimated revision of energy production from PLN

Enterprise for Renewal Energy;

d. estimated revision of load.

SDC 3.4 Model used in making monthly schedule

a. hourly-chronology load model for working day

load way and holiday (typical);.

b. Simplified network model for production

simulation study will be used to consider

imperative interconnection transmission;

c. Power current study to identify possible limited

transfer that requires must-run (forced

dispatch) unit; and

d. Simplified model for study of loses of

distribution.

SDC 3.5 Response of Network’s User and Revised Monthly

Schedule

Network’s User shall be allowed to present its

response on final monthly operation schedule to the

 145

Load Regulator Center until the 25th day prior to

the dispatch month.

The Load Regulator Center may consider accepting or

rejecting the response, but never neglected it

anyway.

If necessary to make a revision, then the revised

final monthly schedule shall be published on 28th

day prior to the dispatch month.

SDC 4.0 Weekly Schedule

The purpose of Weekly Schedule is to schedule the

operation of all power station units and

transmission as well as relay stations to

accommodate unexpected short-term expenses of the

transmissions and relay stations. Weekly schedule

period shall start on Friday to Thursday of the

next coming week.

SDC 4.1 The Load Regulator Center shall schedule weekly

operational optimum, estimate production of every

power station unit to minimize total variable cost

and network outage cost. The result of weekly

schedule, that must be used in the daily dispatch

covers:

a. total energy production of every PLTA reservoir

by considering water consumption factor for non-

electric and environment need;

 146

b. estimated energy to produced by every must-on

PLTA;

c. total energy production generated by PLN

Enterprise with Renewable Energy;

d. list of thermal station that is estimated for

start-up and shut down in the relevant week,

following merit-order produced in the optimation

process;

e. list of power station centers specified as

cooling reserves in the relevant week; and

f. estimated unserved energy and/or lower reserve

margin.

SDC 4.2 Weekly Schedule shall satisfy the following

targets:

a. time specification for start-up and shut down of

basic load thermal stations;

b. allocation of generating/production of all PLTA

reservoirs in daily period, reflects the

consumption of water for non-electric and

environmental needs;

c. allocation of generating/production of the

renewable energy station;

d. consider fuel supply impediment that is reported

to PLN Enterprise;

e. ready-operable power station units with AGC;

 147

f. identification of must-run unit (forced

dispatch) requirement to produce reactive power

to support the voltage and avoid overload

transmission;

g. allocation of minimum energy to be produced by

new power station having the testing been

conducted;

h. allocation of rotation reserve to secure the

readiness if necessary;

i. allocation of minimum generating in an area

having less power capacity to secure consistent

supply in case of disturbance to the imperative

transmission or separation of the System;

j. specification of weekly maintenance schedule of

the transmission.

SDC 4.3 Weekly Schedule Procedure shall cover:

a. consideration of network impediment due to non-

readiness of transmission, voltage regulator or

compensator device;

b. correction of estimated water debit based on

information from PLN Enterprise;

c. generating schedule for renewable energy station

based on the estimated readiness;

d. generating beyond the schedule due to a testing

of new generator unit;

 148

e. statement on readiness of capacity in MW of

every generator unit and specific time on the

commencement and end of the readiness period;

f. upgrade the operational characteristic of

generator unit which is stated ready. Upgrading

process shall cover the following information:

i. identification of operational

characteristic (see Appendix 3 of SDC);

ii. new parameter value of operational

characteristic; and

iii. when the new parameter value is

implemented; and

iv. limitation of operation that is potentially

arising out of environmental consideration.

SDC 4.4 Model Applied in making weekly schedule

a. load characteristic for working day and holiday

chronologically per hour;

b. simplified network model for simulation study of

production by consideration of important

transmission-interconnection only;

c. study on power current to certify potential

limitation of transfer that requires must-run

unit;

d. simplified model for losses of transmission.

SDC 4.5 Scheduling for Weekly Schedule Process

PLN Enterprise shall present estimated readiness

 149

revision of generator unit at the latest on Tuesday

at 10.00 am prior to the week period of weekly

schedule implementation.

The Load Regulator Body shall consider the revision

delivered by PLN Enterprise and issues weekly

schedu8le to all Network’s Users at the latest on

Wednesday at 12.00 prior to the week period of

weekly schedule implementation.

Response on Weekly Schedule of Network Users must

be delivered to the Load Regulator Center at the

latest on Thursday at 10.00 am prior the

implementing week period. The Load Regulator Center

shall consider comments from Network User as to

whether the published weekly schedule shall be

changed or not.

Load Regulator Center shall have published Revised

Weekly Schedule at the latest on Thursday at 15.00

prior the implementing week period of weekly

schedule.

PLN Enterprise shall follow weekly schedule of

generating except any other instruction delivered

by Load Regulator Center.

Load Regulator Center shall prepare daily schedule

of generating allocation for the following next

day. This schedule shall show loading of each

generator unit within half-hour basis. Generating

 150

rate must fulfill the load need of the System,

minimum variable cost and other condition that has

impact on the specific event of the state or

holiday and so on.

SDC 5.1 Information from PLN Enterprise

All PLN Enterprises shall notify the Load Regulator

Center regarding any change of information sent in

the preparation process of Weekly Schedule, and

every change of characteristic of the generator. Up

to date information must be presented to the Load

Regulator Center at the latest 10.00 am prior to

the schedule implementation.

PLN Enterprise for Hydro shall inform the Load

Regulator Center regarding water debit realization

of reservoir and estimated loading per hour of PLTA

run-of-river for the next following day.

SDC 5.2 Estimated Daily Load

The Load Regulator Center shall make load

estimation of each working area of Load Regulator

Unit/Sub-unit per half-hour for the next coming one

day.

SDC 5.3 Identification of Network Impediment

The Load Regulator Center is required to analyzes

load current, short-circuit and stability to verify

that the economic dispatch allocation will not

bring about sensitivity to the System condition. If

 151

any network impediment is identified, then the load

schedule shall be adjusted to confirm secured

System operation.

SDC 5.4 Daily Dispatch

Load Regulator Center shall make daily dispatch in

such a way that minimizes total variable cost of

generator with simulation of production.

Consideration of loss of network and System

impediment at voltage 275 kV and 150 kV must be

accommodated in the daily dispatch.

Total hydro generation in the Weekly schedule must

be allocated in every-half hour loading basis. In

case of any change of water debit into the

reservoir and change of water debit in run-of-

river, then the load rate of the relevant PLTA is

subject to revise.

SDC 5.5 Daily Dispatch Schedule

Daily Dispatch schedule shall cover:

a. generating active power (MSW) every half-hour of

each thermal generating unit, including the

start-up and shut down time;

b. generating total active power (MW) for every

half-hour of hydro generators;

c. generating total active power (MW) for every

half-hour of renewable energy generators;

 152

d. rotation reserve sources and capacity and

operating units with automatic power code (AGC);

e. time of entering and releasing of static

reactive compensation device;

f. times of energizing or transmission blackout;

g. identification of unites specified as cooling

reserve;

h. maintenance schedule of network for that day;

i. identification of unit that will supply minimum

reactive power to keep voltage quality; and

j. reduction of load if it is estimated that will

be imbalance between the load and generating.

Load Regulator Unit/Sub-unit shall inform the

Regional PT PLN (Persero) if reduction of load

is deemed necessary.

SDC 5.6 Presentation Schedule of Generator and Publishing

of Daily Schedule

All PLN Enterprise shall deliver the Load Regulator

Center up to date information on the readiness of

unit before 10.00 am one day prior to the daily

dispatch. Such notice is sent through a form

specified set out in Data Requirement Code – DRC_.

Load Regulator Body shall deliver final daily

dispatch to all Network User at the latest 15.00

one day prior to the dispatch.

PLN Enterprise is obliged to follow load schedule

 153

per half-hour included in the Daily Schedule plan,

except any change of dispatch ordered by Load

Regulator Center. If due to a technical reason, a

generator unit fails to perform load order of the

Load Regulator Center, then the condition must be

immediately reported to the Load Regulator Center.

SDC 6.0 Real-Time Operation and Re-Dispatch

SDC 6.1 Real-Time Operation

During real-time operation, Load Regulator Center

shall be guided with Daily Dispatch and use

operating units with automatic power code to follow

load variation from time to time. The frequency of

system and voltage must be controlled to satisfy

Operating Code – OC). In case of any operating

units with automatic power code (AGC) will reach

the control limits, then the dispatcher will order

certain generator to increase or decrease the

loading from the scheduled load to fulfill the

System load.

During real-time operation, Load Regulator Center

may revise the daily-dispatch schedule to keep

secured System operation, if any sufficient

different between the estimated condition for the

next one day and the actual condition.

If required to maintain economic and reliable

System operation, the Load Regulator Center may re-

 154

dispatch the generator units.

Re-dispatch covers:

a. startup of cooling reserved generator unit to

supply more load of the estimation, or due to

unscheduled take-off of the generator unit or

transmission;

b. add generator unit having AGC facility to keep

the range of load control;

c. decreasing of generator load level or releasing

of generator units due to change of readiness of

generator;

d. change of hydro generating due to change of

unpredictable water-in debit;

e. entry and release of transmission, voltage

regulator or reactive compensator device to cope

with network capacity (grid).

New generating schedule shall be reported to the

Network’s User and will replace the preceding daily

schedule. Load Regulator Center shall verify that

all Network’s Users will be able to satisfy the new

loading schedule prior to the issuance.

SDC 6.2 Criteria for Re-dispatch Procedure

Load Regulator Center may conduct re-dispatch if

one of the following events occurs:

a. one or more units supplying more than 5% the

load will be disturbed (unscheduled release);

 155

b. transmission is or will have overload;

c. increase of water-in debit to PLTA requiring the

increase of PLTA load of more than 5% of the

System load, avoid water runoff.

SDC 7.0 Loading of Generator

This part sets procedure for Load Regulating Center

for the purpose of:

a. ordering generator’s unit loading level;

b. provide approval to PLN Enterprise to release

the generator unit for the purpose of planned

maintenance;

c. implementation of re-scheduling optimation of

daily dispatch.

SDC 7.1 The Purpose

The purpose of generator dispatch is set the Load

Regulator Center to specify the operation directly

so that the supply may fulfill the load

economically with proper reserve by considering:

a. matters included in the Daily Schedule,

including the need of releasing of generator

units for the purpose of maintenance (planned

release);

b. merit order based on the manners set out in SDC

Code;

c. security and reliability;

 156

d. operating standard like System frequency and

voltage regulation.

SDC 7.2 Information sued in dispatch/loading of generator

In making decision on generator operation and

generator releasing schedule, Load Regulator Center

shall consider:

a. Daily schedule, prepared and published in line

with the procedure set out in SDC Code;

b. Up-to-date readiness and characteristic of each

generator;

c. Frequency and voltage of System received by Load

Regulator Center through SCADA;

d. Other information deemed relevant in the

implementation of System operation.

SDC 7.3 Permit for Releasing Generator Unit

Every PLN Enterprise shall report to the Load

Regulator Center if any problem that generates the

release or derating of major and mid generator.

In this case, Load Regulator Center shall evaluate

the consequence of approval for releasing the

unscheduled unit of the System by considering

security, service quality and economic.

If evaluation result indicates that releasing or

derating is acceptable, then Load Regulator Center

will give the permit to PLN Enterprise to change

the generating schedule for remedy of problem of

 157

the reported generator unit.

If small generator unit has trouble that generates

the unit must be taken out or the load is derating,

PLN Enterprise shall report the case to the

relevant Load Regulator Unit/Sub-unit. This

regulator unit shall evaluate the consequence of

releasing the unit to the generating schedule

(System condition). If the evaluation result

indicates that the release or derating is

acceptable, then the Load Regulator Unit/Sub-unit

may give the permit for the renovation work of the

generator unit.

SDC 7.4 Dispatch Order

All PLN Enterprise shall follow the dispatch order

from the Load Regulator Center or Load Regulator

Unit/Sub Unit without suspension.

Dispatch order must be delivered by Load Regulator

Center or Load Regulator Unit/Sub Unit directly to

Users and shall cover also the information of the

name of operators. Order must be delivered by phone

or other media that is mutually approved by Load

Regulator Center or Load Regulator Unit/Sub Unit

and Network Users. If possible, dispatch order is

given in the form of from set out in Appendix 4

SDC.

Receipt of dispatch order shall be immediately and

 158

officially notified by Network’s Users, and state

agree or disagree with the order. PLN Enterprise

may not reject the order given by Load Regulator

Center or Load Regulator Unit/Sub Unit except:

a. matters pertaining to personnel or device safety

that such matters must be substantiated;

b. orders that will cause the Network’s Users

operate its unit beyond the capacity of the

device it is stated thereto.

If certain Network’s Users have trouble to perform

the order to loading, the Users shall soon report

it to the Load Regulator Center or Load Regulator

Unit/Sub Unit.

SDC 7.4.2 Form of Order

Dispatch order covers:

a. Order to make reserve available to keep the

System frequency;

b. Order to activate or shutdown AGC facility;

c. Order to absorb or produce reactive power for

keeping voltage quality;

d. Notice and change of notice on synchrony time;

e. Order for synchrony or release;

f. Order in relation to energizing or change of tap

from voltage regulator;

 159

g. Order in relation to the operation of switching

that may affect interconnection condition

between generator and the System;

h. Order in relation to the operation of controller

device that may affect interconnection condition

between generator and the System (where the

responsibility hereof shall be borne by PLN

Enterprise);

i. Order to add fuel (this must be set in an

agreement between PT PLN (Persero) and PLN

Enterprise;

j. Order to operate generating governor.

SDC 7.4.3 Matters to be made by Network’s User

Every Network’s User shall fulfill all operation

orders of Load Regulator Center or Load Regulator

Unit/Sub-unit without delay, except any matters

occur in line with the description of SDC 7.4.1.

Load Regulator Center or Load Regulator Unit/Sub-

unit shall consider the statement of PLN Enterprise

regarding: start up and shut down time; loading

speed rate and derating at the time of order makes

synchronization, change the load and/or shutdown

the generator unit.

In the operation of the generator, PLN Enterprise

shall meet the load performance level as follows:

 160

a. synchronization or release of generator unit

within less than 5 minutes of the targeted time

specified by Load Regulator Center based on the

information from PLN Enterprise;

b. if no specific targeted time is given, then the

loading level must be reached within less than 2

minutes of the estimated time based on the

ramping rate declaration basis;

c. if the targeted time is specified, then the

loading level as per the order must have been

fulfilled within less than 2 minutes of the

targeted time; and

d. if ordered to reach the certain loading level,

the level must have been reached within the

range of more or less 2% of the declared unit

power.

SDC 8.0 Post-operation and Evaluation Activity

SDC 8.1 Load Regulator Center shall prepare an evaluation

of operational condition of the previous day

covering:

a. discuss/analyze any failure in the fulfillment

of security criteria and reliability of the

System;

b. comparison between realization of total cost of

electric power that is purchased and estimated

 161

cost of dissimulation on estimated basic load of

the System and the readiness of generating;

c. Discuss/analyze the different between daily

schedule and realization of operation;

d. Number of matters that can be concluded or new

maters as the learning material (if any);

e. Summary and note of System operation including

generating date and switching.

SDC 8.2 Evaluation Report of Consolidated Post-operation

Evaluation report of daily post-operation shall be

consolidated to be evaluation report of monthly and

annually post-operation. The Load Regulator Center

shall publish consolidated monthly and annually

Evaluation Report of Post-operation, and deliver

them to all Network’s Users on the agreed time.

SDCA 1 Appendix 1: Estimated Load

SDCA 1 1.0 Introduction

This Appendix explains the preparation of estimated

load for the following purpose:

a. preparation of long-term operational schedule;

b. preparation of monthly schedule;

c. preparation of weekly schedule;

d. preparation of daily dispatch schedule.

Estimated loads in every connection point shall be

computed from the connection point factors (as

specified by Load Regulator Center) and multiplied

 162

with the total estimated load of the System.

SDCA 1 2.0 The Purpose

The purpose of this Appendix is to:

a. specify main source of information that will be

used by Load Regulator Center in the preparation

of estimated load;

b. describe factors to be considered by Load

Regulator Center in the preparation of estimated

load;

c. specify procedures to secure that estimated load

for different period of time shall be made on

consistent basis.

SDCA1 3.0 Estimated Load for Long-term Operational Schedule

Load Regulator Center shall make long-term

operational schedule for every month, the

estimations are as under:

a. peak load (MW) of Distribution Business Units

and Major Consumers, based on estimated energy

need (MWh) and estimated annually peak load of

each relay station of Regional PT LN (Persero);

b. peak load of each connection point and losses of

transmission; and

c. need of reserved margin.

Estimated loads must be completed on 15th September

prior to the preparation of Annual Operational

Schedule.
 163

SDCA1 3.1 Consideration in Making Long-term Load Estimation

In making long-term load estimation, the Load

Regulator Center shall consider the following

factors/data:

a. estimated load used in making one-year

operational schedule;

b. annual estimated load and annual load factor

that is obtained form estimated load for the

System;

c. electric sale statistic to Regional PT PLN

(Persero) and Major Consumers;

d. daily peak load statistic;

e. record of daily load of the System;

f. policy on operational reserve specified in

Operating Code (IC); and

g. other relevant information.

SDCA1 4.0 Estimated Load for Monthly Schedule

Load Regulator Center shall prepare the following

estimations for daily operation of a Monthly

Schedule:

a. energy requirement (MHw) and peak load (MW) of

the three Areas;

b. energy requirement (MHw) and peak load (MW) at

every connection point and losses of network;

and

c. need of reserve margin.

 164

The estimated loads shall be completed on 10th day

of each month prior to the monthly Operational

Schedule.

SDCA1 4.1 Consideration on Making Monthly Load Estimation

The Load Regulator Center shall consider the

following factors/date for making the Monthly

Schedule:

a. estimated load used in making Annual Schedule;

b. electric sale statistic to Distribution Business

Units and Major Consumers;

c. peak load need statistic and daily minimum load;

d. policy on operation specified in Operating Code

(IC); and

e. other relevant information.

The estimated loads shall be completed prior to the

end of week before entering into the weekly

Operational Schedule

SDCA1 5.0 Estimated Load for Weekly Schedule

Load Regulator Center shall prepare the following

estimations for daily operation of a Weekly

Schedule:

a. estimated loads used to prepare Monthly

Schedule;

b. electric sale statistic to Regional PT PLN

(Persero) and Major Consumers, especially detail

note of the recent week data;

 165

c. need of operational reserve specified in

Operating Code (IC); and

d. other relevant information.

CDCA1 6.0 Estimated Load for Daily Dispatch

Load Regulator Center shall prepare the following

estimations for dispatch per ½ hour of a Daily

Schedule/Pre-dispatch:

a. peak load (MW) of Distribution Business Units

and Major Consumers based on estimated energy

needs in Weekly Schedule;

b. Need of energy (MWh) and peak load (MW) at every

connection point and losses of network;

c. Need of total load (MW) for every half hour; and

d. Need of reserve margin.

SDCA1 6.1 Estimation Completion Schedule

Estimated load made for daily dispatch shall be

prepared at 15.00, one day before the dispatch.

SDCA1 6.2 In the preparation of Daily Schedule, the Load

Regulator Center shall consider number of the

following factors:

a. estimated load used in the preparation of Weekly

Schedule;

b. electric sale statistic to Regional PT PLN

(Persero) and Major Consumers;

c. day and night peak load statistic, especially

the recent day data;

 166

d. holiday peak load statistic and other specific

holidays;

e. atmosphere condition estimation;

f. need of operational reserve specified in

Operating Code (OC); and

g. Other relevant information

SDCA2 Appendix 2: Maintenance Schedule

SDCA2 1.0 Introduction

SDCA2 1.1 This Appendix explains the coordination for

maintenance of generator units, main relay

stations and transmissions, as well as

generators grid facilities outages for purposes

of constructions, repairs, testing and

maintenances works.

SDCA2 1.2 Maintenance Scheduled prepared by the Load

Control Centre must consider on other relevant

schedules, in order to guarantee the

fulfillment of generating capacity which meet

with load predictions, including its reserve

requirements.

SDCA2 1.3 If information required in this Appendix shall

be for non business day (non working day), then

such information must be extended on the last

working day before the referred day.

SDCA2 1.4 The Load Control Centre must provide its effort
 167

to accommodate requirements from PLN’s

Generating Units/Generating Companies to outage

their generators in specified days.

Nevertheless, such requirements may be refused

by the Load Control Centre in order to protect

security as well as economic efficiency of the

System. If requirements from PLN’s Generating

Units/Generating Companies are not being

accomplished, and consultation as well as

procedure for dispute resolution included under

this Appendix have been conducted, then PLN’s

Generating Units/Generating Companies must

accept such decision of the Load Control Centre

which decides the outage day as final and

binding.

SDCA2 2.0 OBJECTIVE

SDCA2 2.1 Objective of this Appendix is to determine

regulation for the Load Control Centre to

coordinate all outages for generator units as

well as planned grid facilities (planned-

outages), by way of:

a. Maintain generating capacities as well

as proper griding to meet the load

prediction, including reserves for

operations; and
 168

b. Minimizing the System’s operation cost

for outage of generating units or a grid

facility for maintenance or repair.

SDCA2 3.0 Annual Maintenance Plan/Schedule

SDCA2 3.1 On 1 September, every PLN’s Generating

Units/Generating Companies must submit in

written to the Load Control Centre. Proposal of

unit outage program for he next following 1

(one) year for their each generating unit. Such

proposal must include:

a. Identification of generating units;

b. Capacities (MW) of the related

generating units;

c. Reasons for outage the units and the

Work accomplishment date;

d. Estimations for power outage, in “days”

and “week”;

e. The initial date for such required

outage; and

f. If the schedules are flexible, the

earliest commencement date for

implementation of power outage, and the

latest accomplishment date.

SDCA2 3.2 On every 15 December, the Load Control Centre

must:
 169

a. Issue the Maintenance Plan/Schedule by

considering:

i. Prediction of the System (grid)

load;

ii. Previous maintenance schedule;

iii. Proposals from PLN’s Generating

Units/Generating Companies ;

iv. Requirements for outages of

System Components (grid);

v. Requirements to minimize total

System operation cost related

with such outages of System

Components (grid); and

vi. Other relevant factors.

b. Submit in written to every PLN’s

Generating Units/Generating Companies ,

the allocation date for commencement and

settlement from each required outage of

the related generators.

SDCA2 3.3 If PLN’s Generating Units/Generating Companies

disagree with the outage programs allocated for

their generator units, the related PLN’s

Generating Units/Generating Companies may

submit their written objections to the Load

Control Centre within the latest of 20 December

 170

to explain reasons thereof. If the required

changes by PLN’s Generating Units/Generating

Companies shall not threaten the System’s

security or not effect for any significant

additional of operational cost, then the Load

Control Centre must agree on such proposal of

changes. In the event settlement upon this

problem shall require for involvement from

other PLN’s Generating Units/Generating

Companies , then the Load Control Centre may

conduct meetings by inviting the relevant

parties. If occurring any changes related with

the Maintenance Schedule, then the most up-to-

date schedule must be immediately issued by the

Load Control Centre.

SDCA2 3.4 On every 1st May, each PLN’s Generating

Units/Generating Companies must submit for

correction upon the provisional unit outage

schedules addressed to the Load Control Centre

which shall reflect each revision including

changes have been agreed with the Load Control

Centre according to the SDCA2 3.3

SDCA2 3.5 On every 1st June, the Load Control Centre

should:

a. Revise and issue the most up-to-date

 171

Maintenance Schedule, by considering:

i. The Maintenance Scheduled

arranged based on the SDCA2 3.2;

ii. Each and every amendment upon the

previous agreed Maintenance

Schedule, at the SDCA2 3.3;

iii. Each and every revision upon the

outage schedules of PLN’s

Generating Units/Generating

Companies submitted to the Load

Control Centre according to the

SDCA2 3.4;

iv. Reasons of outages upon the

System’s facilities (generators

or grids);

v. The needs to minimize total

System’s operation cost for such

outage; and

vi. Other relevant factors.

b. Submit in written to every PLN’s

Generating Units/Generating Companies ,

the very latest allocation date for

commencement and settlement for each

applications of outages have been

revised by the Load Control Centre.

 172

SDCA2 3.6 If PLN’s Generating Units/Generating Companies

disagree with the outage programs revised by

the Load Control Centre for their generator

units, the related PLN’s Generating

Units/Generating Companies may submit their

written objections to the Load Control Centre

within the latest of 10 June to explain reasons

thereof. The Load Control Centre and PLN’s

Generating Units/Generating Companies must

discuss such problem for settlements. If the

changes required by PLN’s Generating

Units/Generating Companies do not threaten

security of the System or not effect for any

significant additional of operational cost,

then the Load Control Centre must agree on such

proposal of changes. In the event settlement

upon this problem shall require for involvement

from other PLN’s Generating Units/Generating

Companies , then the Load Control Centre may

conduct meetings by inviting the relevant

parties. If occurring any changes related with

the Maintenance Schedule, then the most up-to-

date schedule must be immediately issued by the

Load Control Centre.

SDCA2 4.0 Maintenance Schedule of the Current Year

 173

SDCA2 4.1 Maintenance Schedule of the Current Year must

be based on the Final Maintenance Schedule

issued on 20 December of the previous year. In

the event that the relevant Maintenance

Schedule has been issued on month of June, then

such referred Maintenance Schedule must be

maintained for the remaining period of the

relevant year.

SDCA2 4.2 Shall there any outages of generator units not

included under the Final Maintenance Schedule

or such matter will effect for changes of

condition, then each PLN’s Generating

Units/Generating Companies must immediately

notify in written the following information to

the Load Control Centre:

a. Identification of generating units;

b. Capacities (MW) of the related

generating units;

c. Reasons for outage the units and the

Work accomplishment date;

d. Estimations time as well as the time

agreed for power outage, shall be

included under the Final Maintenance

Schedule, if necessary in units of

“days” and “week”;

 174

e. The initial date as well as the time

agreed for such required outage, shall

be included under the Final Maintenance

Schedule; and

f. If the schedules are flexible, the

earliest commencement date for

implementation of power outage, and the

latest accomplishment date.

SDCA2 4.3 Monthly Maintenance Schedule

SDCA2 4.4 On the 4th week for each month of the current

year, the Load Control Centre must check for

the Maintenance Schedule of the next following

month and perform for necessary revisions by

considering:

a. The Final Maintenance Schedule for month

of the relevant current year;

b. Each revision upon load prediction;

c. Each application for new outages or

revisions toward the existing schedule

based on the SDCA2 4.2; and

d. Other relevant factors.

SDCA2 4.5 By end of the 4th week on each month, the Load

Control Centre must:

a. Make for Final monthly Maintenance

Schedule for the next following month;

 175

and

b. Submit in written to every PLN’s

Generating Units/Generating Companies ,

the very latest allocation date for

commencement and settlement for

performance of work for each generator’s

outage required by PLN’s Generating

Units/Generating Companies the next

following month.

SDCA2 4.4 Weekly Maintenance Schedule

SDCA2 4.4.1 If there are any PLN’s Generating

Units/Generating Companies require for

alteration upon their outage schedules

(including un-planned outage schedules) within

the next 2 weeks, then such referred PLN’s

Generating Units/Generating Companies must

submit for their proposal at the latest of

Wednesday at 16.00. Such referred proposal must

include data mentioned under SDCA2 4.2.

SDCA2 4.4.2 After the receiving of change proposal related

with the outage schedules from PLN’s Generating

Units/Generating Companies (submitted based on

SDCA2 4.4.1) then within 12 hours, the Load

Control Centre must check for the Maintenance

Schedule of the next following week and perform

 176

necessary revisions by considering:

a. The Monthly Maintenance Schedule for the

relevant week;

b. Each revision upon load prediction for

the relevant week;

c. Estimation concerning readiness of the

available capacities from generator

units, as well as risk assessment from

any possibilities that some capacities

estimated in ready condition become

unready under out off planned reasons;

d. Each proposal for generator’s outages by

PLN’s Generating Units/Generating

Companies , in accordance with the SDCA2

4.4.1; and

e. The go off or being disturbed of

facilities (grids) from the referred

schedule; and

f. Other relevant factors.

SDCA2 4.4.3 On every Thursday at 15:00, the Load Control

Centre must:

a. Make for Weekly Maintenance Schedule for

the next following week; and

b. Submit in written to every PLN’s

Generating Units/Generating Companies ,

 177

the date for commencement and settlement

for outage required by PLN’s Generating

Units/Generating Companies the next

following week.

SDCA3 Appendix 3: Statement / Declaration by PLN’s

Generating Units/Generating Companies

SDCA3 1.0 Introduction

SDCA3 1.1 This Appendix will explain the operational

characteristic parameters for each unit of

generators have to be stated/declared by PLN’s

Generating Units/Generating Companies . Such

referred statement must reflect the real

operational characteristic over unit of

generators, which will be determined based on

generally accepted practices.

SDCA3 1.2 For thermal generating units, PLN’s Generating

Units/Generating Companies must notify to the

Load Control Centre concerning its readiness

characteristic as of defined under SDCA3 2.1.1

SDCA3 1.3 For the hydro generating units (Water Power

Plant), the category of units’ readiness as of

defined under SDCA3 2.1.1 shall not prevail and

may be neglected.

SDCA3 2.0 Statements from PLN’s Generating

Units/Generating Companies
 178

SDCA3 2.1 Readiness of the Thermal Units for

Synchronizations

SDCA3 2.1.1 Definition of Readiness of Units

PLN’s Generating Units/Generating Companies

must provide for information concerning the

readiness of units for synchronizations within

4 (four) conditions: cool, warm, heat, and

overheating.

Their definitions shall be as follows:

Cool : Temperatures of Turbine and

Boiler are under possible

level for the units to be

synchronized within period

of more than 5 (five) hours.

Warm : Temperatures of Turbine and

Boiler are under possible

level for the units to be

synchronized within period

of more than 1 (one) hour

but less than 5 (five)

hours.

Heat : Temperatures of Turbine and

Boiler are under possible

level for the units to be

synchronized within period

 179

of less than 1 (one) hour.

Overheating : Temperature and pressure of

Turbine and Boiler are under

possible level for the

rolling of turbine for the

units to be synchronized

after receiving instruction

for synchronization.

SDCA3 2.2 Characteristic of Operation

SDCA3 2.2.1 The first set for Characteristic of Operation

is concerning its capability for output power

and capability for active & reactive power

conversion, including:

a. Maximum and minimum capability for

active power for some operational

configuration possibilities (such as:

numbers of BFP, numbers of mills for

units using coal fuel, numbers of gas

turbine and HRSG for Steam Geothermal

Power Plant, and others);

b. Capabilities for reactive power,

producing (pf-lagging) and absorbing

(pf-leading) at certain loading levels;

c. Limitation for governor’s loading

levels as well as droop’s setting;

 180

d. Time for start up, cost for start up,

minimum exit time and cost to maintain

the readiness of units to have

synchronization under cool, warm, heat,

and overheating conditions;

e. The load level a moment after

synchronization;

f. load increment speed (in MW/minute) for

different load levels;

g. Load declining speed (in MW/minute) for

different load levels;

h. Minimum operation time; and

i. Maximum fuel conversion may be carried

out within period of 24 hours, whenever

required.

SDCA3 2.2.2 The second set for Characteristic of Operation

is concerning the economic operation over

generator units. PLN’s Generating

Units/Generating Companies must submit for

economic operation over their generator units,

pursuant to the provisions under SDCA3 2.2.3 or

SDCA3 2.2.4. This Characteristic of Operation

in general named as Economic Operation

Characteristic.

SDCA3 2.2.3 The Economic Operation Characteristic of

 181

Thermal Generator Units.

There are 2 (two) choices for deliverance of

the Economic Operation Characteristic of

Thermal Generator Units.

The first choice, PLN’s Generating

Units/Generating Companies must provide for

the following information each unit of their

thermal generators:

a. Fuel; statement of type of fuels used

by the generator units;

b. Specific energy contents for each

types of fuel, they are BTU contents,

kilocalorie per unit volume or weight;

c. Energy required for start up; the

needs of energy in BTU per start up or

kilocalorie per start up for various

conditions related with readiness for

unit synchronization;

d. Energy for full turn; the needs of

energy in BTU per hour or kilocalorie

per hour, to maintain the units in

synchronization;

e. Heat rate data; speed for energy

conversion in BTU per MWh or

kilocalories per MWh required for

 182

conversion of the generator units

output power;

f. Heat rate conversion data; speed for

energy increment in BTU per MWh or

kilocalories per MWh required to

result for conversion of the generator

units output power;

g. Standby start up energy; energy in BTU

or kilocalories required to heat

Boiler and Turbine from cool condition

into very ready condition;

h. Heat standby energy: energy in

BTU/hour or kilocalorie/hour required

to maintain for Boiler and Turbine

under ‘ready-heat’ condition;

i. O&M Start-up cost: non fuel O&M cost

in Rp or related with start-up

process;

j. O&M power (output) cost: non fuel O&M

cost within process to produce output

power, in Rp/MWh;

k. O&M Start-up standby cost: non fuel

O&M cost within process to heat the

Boiler and Turbine into ready

condition, in Rp/start-up; and

 183

l. O&M heat standby cost: non fuel O&M

cost in Rp/hour, to maintain the

readiness of Boiler and Turbine under

‘ready-heat’ condition;

The second choice, PLN’s Generating Units/Generating

Companies will provide the following information for

each thermal generating unit:

a. Generating Unit’s Start up cost in

Rp/hour, for some condition levels

related with readiness of unit to

synchronize;

b. Minimum loading cost – cost in

Rp/hour to maintain the unit keeps

operating (synchronous), under minimum

load;

c. Incremental cost – output cost in

Rp/MWh as additional to the minimum

load cost;

d. Standby start-up cost – cost in

Rp/start up, to heat the boiler and

turbine from cold condition into very

ready condition;

e. Heat readiness cost – cost in Rp/hour,

to maintain boiler under synchronous

condition.
 184

SDCA3 2.2.4 The Economic Operation Characteristic of

Hydro Generator Units.

A Hydro Power Plant with run of river will

require no economic operation

characteristic.

Operating data for reservoir Hydro Power

Plant units should include:

a. Water Surface Height and/or

reservoir’s volume during reporting

time;

b. Entrance and exit water’s speed for

requirement of non electricity.

SDCA4 Appendix 4: Dispatch Instructions

SDCA4 1.0 Introduction

SDCA4 1.1 Dispatch instructions should include (at

least) the following information:

a. Operator’s names;

b. Identification of upon the

appointed/required generator units as

per Dispatch instructions;

c. Tasks that must be carried out by each

generator units or loading level for

units as per instruction;

d. Time for the related units to be

turned on based on instruction (if the

 185

required time is different with the

instruction time); and

e. If deemed necessary, extend for time

target whenever certain loading levels

need to be achieved or instructions

have to be completed of its

performance.

The Party receives for verbal instructions,

to be requested to repeat the contents of

thereof to guarantee that such referred

instructions completely being understood.

Dispatcher must record such instruction as

well as instruction time under his log book.

SDCA4 1.2 Examples of kinds of main instructions from

dispatcher will be described. Within such

each of example, to be deemed that the needs

to notify each operator’s name have been

well performed. An instruction may include

starting time and targeting time.

SDCA4 2.0 Instruction to Change the Loading Level.

On each example, ‘instruction’ is for the

Unit 3 to change the load into 100 MW, with

instruction time at 13:00:

a. In case ‘instruction’ must be

 186

immediately implemented:

“Unit 3 changed into 100 MW, now”;

b. In case ‘instruction’ starts to be

carried out within 1 (one) hour later:

“Unit 3 changed into 100 MW, will be

start at 14:00”;

c. In case the instruction is to achieve

for load level as per instructed at

13:30:

“Unit 3 changed into 100 MW at 13:30”.

SDCA4 3.0 Instruction for Synchronizations

SDCA4 3.1 In case of “Instruction for

Synchronizations”, in common to be directly

followed by instruction for loading. If the

load level excluded from such instruction,

then generator unit must be synchronized

into minimum load level (in accordance with

the current prevail loading speed), and then

immediately report to the Load Control

Centre. In extending such Instruction for

Synchronizations, the Load Control Centre

should always pay attention on time for

Synchronization process informed by PLN’s

Generating Units/Generating Companies and

provide for tie target upon such

 187

Synchronization.

SDCA4 3.2 On the next following example, Unit 3 has

been ordered to be synchronous and had

minimum load, and instruction time was

08:00. Period as of deliverance of such

notification to PLN’s Generating

Units/Generating Companies for such

synchronization was 4 hours.

In this example, time required for

synchronization shall be pursuant to the

notification time:

“Unit 3 to be synchronous at 12:00, under

the load of 100 MW”.

SDCA4 4.0 Instructions for Shut down or Discharge the

Unit from the Operation System.

SDCA4 4.1 Instruction to discharge from Operating

System should be interpreted as instruction

to release the PMT generator Unit, and

discharge the unit from System (grid).

Example of such instruction shall be as

follows:

a. If Unit 1 requested to out from the

Operating System as fast as possible,

then the instruction is:

“ Discharge the Unit 1 now”

 188

And operator of the generator unit

must immediately release the PMT

generator Unit;

b. If Unit 1 requested to out from the

Operating System within the next

certain times, then the instruction

is:

“ Discharge the Unit 1 at 11:30”

SDCA4 4.2 Instruction for shut down the unit should be

interpreted as requirement for reducing

output power of the relevant generator unit

into minimum load level before discharge the

unit from system. Under an instruction to

discharge for unit, must be considered the

unit’s load decreasing speed, and/or whether

has been included under the instruction. The

following examples describe that Unit 1 is

operating with load of 70 MW, and having its

load decreasing speed for 3 MW/minutes and

its minimum load level is 10 MW.

a. “Start the discharge process Unit 1 at

10:00 and discharge the Unit at

10:20”; or

b. “Start the discharge process Unit 1 at

10:00, load decrement is 2 MW/minutes

 189

and discharges the Unit at 12:30”.

SDCA4 5.0 Frequency Control

SDCA4 5.1 Instruction to activate or turn off the

Automatic Load Control (AGC)

SDCA4 5.2 Example of instructions to activate or turn

off the AGC are:

a. “Unit 1 to be operated with AGC at

12:00”; and

b. “Unit 1 to be operated without AGC at

12:00”.

SDCA4 6.0 Instruction to Provide for Operational Back

Up Instruction for providing operation back

up usually being given as part of loading

instruction. For example:

“Load of Unit 4 is now 100 MW and maintain

it at 150 MW for back up”

SDCA4 7.0 Instruction to Provide for Voltage Support

In order to maintain the System’s voltage,

the Load Control Centre may order Generators

in some ways.

Examples of the instructions are as follows:

a. “Unit 2 generates for maximum reactive

power”;

b. “Maintain the voltage at 155 kV at

generator’s bar of 150 kV”; and

 190

c. “Maintain for Unit 2 in its maximum

voltage”.
 191

Settlement Code - SC

Settlement Code shall explain rules and

procedures related with calculation for

collection and payment upon sales and services

for energy.

SC 1.0 Introduction

Payment and charges applied upon transaction for

system may be calculated based on data collected

from transaction meter, generators scheduling

and loading reports, as well as based on

provisions of contract between the parties. All

transaction over electricity power must be based

on such referred contractual mechanism. This

rules must be renewed in line with the change

and development of types of contract and market

of the referred electricity power.

SC 2.0 Collection and Payment

SC 1.0 Minutes Schedule for Settlement of Generator

The collection period for all Grid Users will be

started from 10:00 of the first day on each

month until 10:00 of the first day on the next

following month. Meters to be read at 10:00 on

the first day of each month and to be included

under Minutes of Meter Reading. If there are no

 192

disputes related with such read data, then P3B

Sumatra will issue for Minutes of Transaction

for Electricity Power between the party of

PLN’s Generating Units/Generating Companies with

PT. PLN (Persero) within the latest of 9 working

days after receiving the Minutes of Meter

Reading or earlier if required by Power

Procurement Agreement.

P3B Sumatra shall provide for PT. PLN (Persero)

with calculations of monthly energy produced by

each PLN’s Generating Units/Generating

Companies pursuant to the Minutes of Meter

Reading between P3B Sumatra with PLN’s

Generating Units/Generating Companies.

SC 2.2 Payment to Generating Companies

Payment for long term and monthly procurement of

electricity power from PLN’s Generating

Units/Generating Companies shall be based on

provisions under Power Procurement Agreement or

other contractual agreements with PT. PLN

(Persero).

SC 2.3 Minutes Schedule for Power Transaction with PT.

PLN (Persero) and Regional

Collection period for all Grid Users to be

started at 10:00 of the first day on each month

 193

until 10:00 of the first day on the next

following month. Meters to be read at 10:00 of

the first day on each month and included under

Minutes of Meter Reading. If there are no

disputes related with such read data, then P3B

Sumatra will issue for Minutes of Transaction

for Electricity Power between the Party of

Regional Unit with PT. PLN (Persero) within the

latest of 15 working days after receiving such

Minutes of Meter Reading.

P3B Sumatra will provide for PT. PLN (Persero)

with calculation of monthly energy consumed by

each Regional Unit based on Minutes of Meter

Reading between P3B Sumatra and the related

Regional Unit. Big Consumers connected into the

Grid shall be treated as consumers of the

Regional Unit.

SC 3.0 Dispute Resolution for Transactions

Copy of transaction meter data, generators

scheduling and loading record as well as each

data and other information require for

collection and payment to be provided based on

request. Shall there are any questions or

objections toward a supporting data, then such

referred questions or objections must be

 194

provided in written and addressed to P3B Sumatra

as contract management.

In the event there are any dispute resolution

procedures under the Power Procurement Agreement

for PLN’s Generating Units/Generating Companies

and Power Selling Agreement for PT. PLN

(Persero) Regional Unit and Big Consumers then

provisions under such referred Agreements shall

prevail.

In case of process for such dispute resolution

not being specified under such above mentioned

agreements or in case the problems arisen out

not being treated under such agreements, then

the process for such dispute resolution shall be

as follows:

a. Effort to be performed in order to

settle the problems under informal

ways by means of phone conversation or

meeting in a certain agree place;

b. If such informal resolutions are not

worked then each disputed party will

state their positions in written and

submit the dispute including

documentations thereof to their

superiors; and
 195

c. Within the stage of process for

dispute resolution, superiors involved

must meet and give their best efforts

to settle the dispute. Shall there any

settlement thereof, then position of

P3B shall prevail. If other parties

rare willing to further settle this

dispute then such parties may file

the case to arbiter appointed by

Management Committee (if has been

formed). Arbitrator’s decision shall

be final and binding.

SC 4.0 Processing of Meter Data

SC 4.1 Processing of Generator Meter Data

Processing of Generator Meter Data shall go

along with the following steps:

a. Within three working days after end of

collection period, P3B Sumatra has

received and performed meter data

validation of all generators which

will be included under Minutes of

Meter Reading;

b. Main meter data to be compared with

standard meter data by using a

consistent data validation method;

 196

c. P3B Sumatra will send to PLN’s

Generating Units/Generating Companies,

such Minutes of Power Transaction

within nine working days after

receiving the Minutes of Meter Reading

and shall not exceed the 17th days of

the current month. All such Minutes

will then become basis for submission

of collections to PT. PLN (Persero);

d. In case the transactional meter data

are not complete, or there any

mistakes, then the standard meter data

will be used. If such standard meter

data also incomplete, or there any

mistakes, P3B Sumatra will use an

appropriate method to provide for

estimation which may mutually agreed;

e. P3B Sumatra will issue special Minutes

related with corrections toward the

mistakes of such meter data and submit

the related minutes to PLN’s

Generating Units/Generating Companies

as soon as possible after mistakes are

being identified; and

f. All meter data collected, and

 197

validation as well as correction

information to be kept in a secure

server for at least three years.

SC 4.2 Meter Data Processing for PT. PLN (Persero)

Regional Unit

Meter data processing for Regional Units shall

go along with the following steps:

a. Within three working days after end of

collection period, P3B Sumatra has

received and performed meter data

validation of all meter data from all

Regional Units’s transformers at the

main station of P3B Sumara ;

b. Main meter data to be compared with

standard meter data by using a

consistent data validation method;

c. P3B Sumatra will send Minutes of Power

Transfer to Regional Units and will

not exceed the 25th days of the current

month. All such Minutes will then

become basis for calculation of Power

Transfer from P3B Sumatra to

Regional Units;

d. In case the transactional meter data

are not complete, or there any

 198

mistakes, then the standard meter data

will be used. If such standard meter

data also incomplete, or there any

mistakes, P3B Sumatra will use an

appropriate method to provide for

estimation which may mutually agreed.

P3B Sumatra will issue special Minutes

related with corrections toward the

mistakes of such meter data and submit

the related minutes to PLN’s

Generating Units/Generating Companies

as soon as possible after mistakes are

being identified; and

e. All meter data collected, and

validation as well as correction

information to be kept in a secure

server for at least three years.

SC 4.3 Meter Data Processing for Big Consumers of PT.

PLN (Persero) Regional Units

Regional Units shall be responsible toward the

data meter processing of all their big

consumers. In this case P3B Sumatra will witness

for meter reading process to be included under

Minutes of Meter Reading, but will not join in

 199

the next following data processing.

SC 5.0 Settlement Process Equipments

P3B Sumatra develop and apply a settlement

process software pursuant to provisions of Power

Procurement Agreement and such referred software

must be validated and accepted by the parties

involving for transaction before implementation.

SC 6.0 Settlement Process Audit Procedure

SC 6.1 Audit Upon Request of Grid Users

Grid User shall reserve their rights to request

for audit for the purpose of settlement process

in connection with their calculation under the

following conditions:

a. Every Grid Users shall reserve their

right to choose for independent third

party, that comply with qualification

for performing audit for settlement;

b. The entire audit cost will be borne to

the party request for such audit

performance; and

c. Audit results to be extended to the

Grid Users and P3B Sumatra, and then

P3B Sumatra will establish for respond

toward such audit report, including

each adjustment in calculation for

 200

payment of collection resulted from

such audit. All details of audit must

be opened for Grid Users upon request.

SC 7.0 Availability of Meter Data for Other Parties

Meter Data of Grid User to be categorized as non

confidential and shall be available for other

parties upon request. The requested data shall

be included:

a. Numbers of sold and bought electricity

power for every half hour;

b. Average prices of sold and bought

electricity power for every half hour;

and

c. Metered and estimated data at each

interconnection point.

SC 8.0 Others

All settlement’s conditions and procedures not

being specified under this rule will be further

arranged under a Settlement Permanent Procedure

agreed by the parties in transaction.

Metering of transactions not yet able to comply

with conditions under point 7.0 will be arranged

with agreement of the related parties.

 201

Metering Code – MC

Metering Code shall explain both technical and

operational minimum requirements for meter

Transaction which is the main meter and comparison

meter to be installed by P3B Sumatra and

transmission Grid Users at the connection points.

MC 1.0 Metering Criteria

MC 1.1 Units to be Metered

Meter should be installed through the current

transformer and voltage transformer at each

connection point to meter the following units:

a. kWh import;

b. kWh export;

c. kVArh import;

d. kVArh export;

e. Maximum kVA demand (no need for connection

to generator).

MC 1.2 Accuracy

MC 1.2.1 Meter accuracy for all connection point (except

for generator < 10 MW).

Each and every Meter component must comply with

the following minimum accuracy standards:

a. Instrument Transformer

Voltage transformer must have its accuracy

in accordance with class 0.2, IEC Standard

 202

186. Current Transformer must have its

accuracy in accordance with class 0.2, IEC

Standard 185.

b. kilowatt-hour Meter (kWh-active Meter).

Each kWh meter must consist of three current

element type, solid state, three phase four

wire, possess export and import

registration, accuracy for class 0.2, IEC

Standard 687. The meter should be completed

with pulse equipment which is able to be

accessed by reading for remote reading and

recording, as well as has facility to store

information data as of explained under MC

2.3.2.2.

c. kiloVAr-hour Meter (kiloVAr - reactive

Meter).

Specifically for Big Consumers and or High

Voltage Consumers, each kVAr meter must

consist of three current element type, solid

state, three phase four wire, possess export

and import registration, accuracy for class

0.2, IEC Standard 1268. The meter should be

completed with pulse equipment which is able

to be accessed by reading for remote reading

and recording, as well as has facility to

 203

store information data as of explained under

MC 2.3.2.2.

d. maximum kVA demand Meter

Each kVA demand meter must consist of three

current element type, multiple tariff, solid

state with registrations, accuracy for class

0.5S, IEC Standard 687. The meter should be

completed with pulse equipment for

transmission to a recording equipment or

posses facility to store information data as

of explained under MC 2.3.2.2.

MC 1.2.2 Meter Accuracy for Generator < 10 MW

Each and every Meter component must comply with

the following minimum accuracy standards:

a. Instrument Transformer

Voltage transformer must have its accuracy

in accordance with class 0.5, IEC Standard

186. Current Transformer must have its

accuracy in accordance with class 0.5, IEC

Standard 185.

b. kilowatt-hour Meter (kWh-active Meter).

Each kWh meter must consist of three current

element type, solid state, three phase four

wire, possess export and import

registration, accuracy for class 0.5S, IEC

 204

Standard 687. The meter should be completed

with pulse equipment which is able to be

accessed by reading for remote reading and

recording, as well as has facility to store

information data as of explained under MC

2.3.2.2.

c. kiloVAr-hour Meter (kiloVAr - reactive

Meter).

Each kVAr meter must consist of three

current element type, solid state, three

phase four wire, possess export and import

registration, accuracy for class 2.0, IEC

Standard 1268. The meter should be completed

with pulse equipment which is able to be

accessed by reading for remote reading and

recording, as well as has facility to store

information data as of explained under MC

2.3.2.2.

MC 1.2.3 Accuracy at connection point

a. Meter for generator must be designed to

meter the energy-net distributed into the

Grid and its installation will be at net

points.

b. Meters installed for small generator units

may be excluded from requirements as of

 205

mentioned under MC 1.2.3.a. In this case,

compensation must be estimated by using

algorithm which is calculated losses between

the metering points and connection points.

The algorithm used for such purpose is to be

created by P3B Sumatra, to be reviewed and

agreed by Grid Users.

MC 1.2.4 Accuracy of Reading

The difference between numbers of distributed

active or reactive energy during certain period

over the reading result compared with display of

recorder at the early and end of such period must

be within the ranges of ± 0.5% (under fully loaded

condition).

MC 1.2.5 Accuracy of Time Recorder

All meter installations must record the time at

West Indonesia Time (zone). Limits of total fault

for demand meter Time Recorder are as follows:

a. Initial time for each period must be at

specified standard time under tolerance of ±

2 minutes; ,and

b. Re-programming for meters must be

immediately performed if time fault reach

for 5 minutes or more, and within period of

6 months if such time fault exceed for 2

 206

minutes and less than 5 minutes.

MC 2.0 Requirements for Meter Equipments

MC 2.1 Meter

Active and reactive energy meter for export and

import, either main meter or standard meter,

should be installed at each connection point. This

thing must be fulfilled by usage of the following

bidirectional meters:

a. Main active energy meter;

b. Standard active energy meter;

c. Main reactive energy meter;

d. Standard reactive energy meter;

e. Maximum kVA demand meter (no need for

generator and connection of distribution

transformer)

MC 2.2 Instrument Transformer

MC 2.2.1 Each and every Grid User must install at least one

set of voltage/current transformers with separated

coil or core for protection and metering. Such

transformers may also used as main meter and

standard meter at the same time. To be suggested

(but not as a must) to install separated voltage

transformer and current transformer only for

metering.

MC 2.3 Data Collection

 207

MC 2.3.1 Data Recording

MC 2.3.1.1 Impulses resulted by Meter must be recorded by

such meter.

MC 2.3.1.2 If there are more than one connection point to one

or more Grid Users within one location, maybe will

be required for installation of separated

recorders for totaling the active and reactive

energies from all main meters and standard meters

according to the statement under Interconnection

Contract and/or Power Purchase Agreement.

MC 2.3.1.3 Metering period for pulses adding shall be varied

within ranges of 5 minutes until 60 minutes.

MC 2.3.1.4 All meters must have capability to maintain data

for at least 7 (seven) days in the event of

occurring any faults in supplying of auxiliary

power.

MC 2.3.2 Communication

MC 2.3.2.1 Each meter should have capability for electronic

data transfer, and complete with modem and

dedicated line provided by Grid User and able to

be accessed automatically, remote or manual remote

by P3B Sumatra or by Grid User.

MC 2.3.2.2 If because of any reasons automatic or manual

remote readings are unable to be performed, then a

local down-loading must be conducted by P3B

 208

Sumatra. The installed storage must be able to

accommodate data for 35 days to anticipate the

occurrence of fault within communication link.

Daily data to be down-loaded from such meters must

be stored in a certain database for P3B Sumatra.

MC 2.3.2.3 Communication protocol, information format and

software used at the communication equipments

to/from the Metering equipments must compatible

with the equipments used by P3B Sumatra and should

previously receive for approval from P3B Sumatra.

MC 2.4 Requirements for Installation

MC 2.4.1 All main meters must be installed beside the main

PMT installation of P3B Sumatra, while the

standard meter must be installed beside the Grid

User of such main PMT.

MC 2.4.2 Proper cubicles must be provided for such meters

in every connection point. The cubicles’

construction should comply with the national

standard and/or PT. PLN (Persero) and/or P3B

Sumatra, and should at first obtain for approval

from P3B Sumatra. The referred Meter Cubicle must

have front and back doors which are able to be

locked and sealed, and completed with sealable

terminal blocks.

MC 2.4.3 Meter installation may be attached at the front

 209

door or at the inner plate behind the front door.

MC 2.4.4 Auxiliary power supply to Meter must be secured by

using the following methods as agreed by the

parties:

a. Supply through inverter from the available

dc-batteries source;

b. Supply through the continue Power

Transformer voltage (PT Bus or PT Bay);

c. Supply from a UPS (un-interrupted power

system) with internal batteries and

connected into ac source supply.

Requirement for power limit: power limit range

variation is ± 10%.

Each metering equipments to be completed with

under voltage relay or disturbance detection tools

to monitor phase voltages enters to meters and

generate for alarm if occurring any low voltages.

The real burden of current Transformer and voltage

Transformer must be maintained within the range of

25% - 100% from their ratings.

Diameter of voltage connection cable must be big

enough thus voltage drops must be lower than 1%.

Metering voltage into each main meter and standard

meter must be separated and to be completed with

MCBs which are installed on their marshalling

 210

kiosk.

MC 2.4.5 Secondary connection for current transformer and

voltage transformer must be directly connected

into meter terminal, and voltage cable must be

equipped with screen.

MC 2.5 Ownership

Main Meter to be provided / installed and owned by

the seller party and Standard Meter to be provided

/ installed and owned by the buyer party. Each

parties must operate and maintain their meters

(except has been specified under the Electricity

Power Procurement Agreement).

MC 2.6 Metering Data Process for Payments

MC 2.6.1 P3B Sumatra shall perform maintenance and

management for metering database which include all

connection point metering data. P3B Sumatra

obligates to collect such metering data in remote

from all meters at the connection points, and

store such data under database for the purpose of

sell and buy calculations. If such data collection

in remote is fail or the facilities to perform

such collection have not available yet, then P3B

Sumatra will try to collect such data by way of

local down loading/local reading to be further

entered in database.
 211

MC 2.6.2 P3B Sumatra should use the metering data stored

under the database of the first day of the next

following month for calculation of the collection

month.

MC 2.6.3 Data used for such calculation of sell and buy

collection shall be record of data from the main

meter. If being found out that have been occurred

any faults on such main meter, then data being

used shall be data under the standard meter.

The mentioned faults shall include:

a. Disorder data;

b. Incomplete data;

c. Significant time errors, and/or;

d. Difference between data recording and the

main meter and the standard meter for one or

more reading periods or for one whole month,

exceed the accuracy class of such main meter

and standard meter.

MC 2.6.4 If case being found out any differences but

impossible to determine the wrong meters or

perhaps both meters are wrong, then the data used

for collection calculation process must be agreed

by both parties, and to be notified under Minutes

signed by both parties.

MC 3.0 Commissioning
 212

MC 3.1 Before the distribution of voltage at connection

points, the Grid Users must submit to P3B Sumatra

the following documents for Metering System:

a. Single line diagram which indicates

connection points and Metering equipments

according to the installed ones;

b. Initial testing certificate and calibration

certificate for current transformer, voltage

transformer and meters;

c. Voltage drop calculation in the voltage

connection;

d. Burden calculation at the meter connection.

MC 3.2 P3B Sumatra and Testing Agency must inspect and

test the Metering Equipments / Metering Systems

and to be witnessed by Grid Users. Such

inspections include conformity with the Metering

Code, and good practices for electricity

installation. Other matters need to be conducted

are:

a. Meter Programming and calibration, by

following the IEC Standards;

b. Measuring for voltage drop and burden within

the metering connection; and

c. Attachment of seals.

MC 3.3 Such inspection and testing results must be

 213

included under certificate signed by the related

party and by the Testing Agency.

MC 3.4 Inspection cost for Metering Equipments / Metering

Systems to be borne by the meter owner.

MC 4.0 Testing after Commissioning

MC 4.1 Periodic Testing

MC 4.1.1 After commissioning, Meter equipments must be

inspected and tested in accordance with national

standard of IEC and/or PT. PLN under the following

time interval:

a. Current transformer and voltage transformer:

at the first time of its operation;

b. Metering Equipments: every 5 years.

MC 4.1.2 Periodic testing cost upon such Meter equipments

to be borne by owner.

MC 4.1.3 Payments for repairing or replacement of parts

damage cost to be borne by each meter owners.

MC 4.2 Unscheduled Testing

MC 4.2.1 One party may submit fro written request to

another party to perform re-calibrations toward

main meters and standard meters, by attaching

detail analysis of faults have been found;

MC 4.2.2 If the meter owners agree to conduct such re-

calibrations, then re-calibrations must be

performed by Testing Agency or other testing

 214

institutions agreed by both parties (except has

been specified under the Power Procurement

Agreement).

MC 4.2.3 If the testing results from such re-calibrations

indicate the Meters’ condition has been in

accordance with its class standards, then the

relevant testing institutions must issued for

calibration certificates. If being found will be

impossible to perform such re-calibrations then

the testing institutions must provide for

observation reports and recommend for further

actions.

MC 4.2.4 The testing is to be witnessed by P3B Sumatra and

Grid Users. Will be established for formal report

related with such testing and signed by the

related parties;

MC 4.2.5 If the re-calibrations being found impossible to

be conducted because of damage with the result

that the relevant meters must be replaced, then

such meters must be replaced upon charges on the

meters owner.

MC 4.2.6 Testing payments to be arranged as follows:

a. If the first testing indicate that such

meters are in conformity with their calss

standards, the party requests for such

 215

testing should pay the cost; or

b. If the first testing indicate that such

meters are required for re-calibrations,

then the meters owner should pay the cost.

MC 5.0 Seal and Re-Programming

After the performance of testing upon the Meter

equipments, P3B Sumatra and Grid User will put for

seals with clear identifications.

The break of such seal by one party may be

conducted under permission from other parties.

Meter re-programming may only be performed by

owner of the meters and to be witnessed by other

parties.

Replacement of seal and meter re-programming must

be accompanied with formal reports signed by all

attendance parties.

MC 6.0 Inspection for Meter Data and Equipments

MC 6.1 Access Right into Meter Data

Grid User shall reserve their right to access

their metering data under the electronic data base

or at the Office of P3B Sumatra.

MC 6.2 Access into the Metering Equipments

Owner of the metering equipments must provide for

access for P3B Sumatra and Grid Users obtaining

for any consequences at the connection point for

 216

verification upon the metering equipments compared

with the Metering Code, as well as to witness such

inspection, read for registers and/or checking for

seals.

The Grid User shall be prohibited to perform an

activity that influence the meter operation,

except being required to fulfill its obligation

pursuant to provisions under the Grid Code.

MC 6.3 Access and Inspection

This section will explain some of the following

conditions:

a. P3B Sumatra may enter into the Grid User’s

location for the purpose of inspection and

testing;

b. The Grid User may enter into the P3B

Sumatra’s location;

c. Arrangements of procedures and activities

for entering a party’s location and

performing for inspection.

MC 6.4 Right for Inspection

Scope for this Inspection shall be excluded meter

checking for the purpose of Electricity Current

Control at Customer’s place.

a. This section will extended for right to P3B

Sumatra to check each Grid User’s Meter

 217

equipment and vice versa, whose heir Meter

Equipment are connected with the Grid, the

mutual right to check each Meter equipment

of other parties at the connection points.

b. If one party feels sure that other party is

not comply with requirements of the Grid

Code and such matter inflicted for losses,

or being suspected inflict for losses, then

the relevant party may request for

inspection/checking toward the suspected

Meter equipments.

c. The party requires for such inspection

toward other party’s Meter equipments, must

notify its intention to the related party at

least within 5 working days before the

performance of such inspection.

d. For effectiveness of the above mentioned

notification at point (c), such notification

must be completed with the following

information:

i. Name of representative will conduct

such inspection who is represent the

party requires for inspection;

ii. The inspection time and estimation

time for completion;

 218

iii. Conformity with the suspected

Metering Code.

e. The suspected party must assign its capable

personnel to assist representative of the

inspector party who will enter into the

related location for inspection.

f. The inspector party must guarantee that

inspection which will be conducted just for

whatever extend necessary, and the time

shall not exceed for 24 hours.

g. The inspector party must guarantee that its

inspector representative is capable to

perform such inspection.

h. Inspection cost to be borne by the party

requires for inspection, except being found

any faults, then the inspected party will

bear for the cost.

MC 7.0 Meter Installation and Data Security

MC 7.1 Changes on Metering Equipments

All changes will be conducted toward the metering

equipments including the meter equipment,

parameters and/or setting, must receive for

approval from P3B Sumatra and the related Grid

Users;

MC 7.2 Changes on Metering Data

 219

Any changes upon the original data stored in a

Meter shall be prohibited except during

implementation of site accuracy test.

MC 7.3 Password Protection in Metering Data

The data stored in database must be protected (by

using password) against any prohibited direct,

local or remote electronic accesses. P3B Sumatra

as database manager has its obligation to monitor

such accesses to database in order to guarantee

that all data are well protected against any one

having no right for accessing and/or using.

MC 8.0 Exception and Grace Period

a. To be suggested (but shall not a must) to

comply with provisions under MC 1.2.1.a and

MC 1.2.1.b for the installed installations

before the commencement of this Grid Code.

b. Standard Meter for connection points with

the Generating PLN and PT. PLN (Persero)

Regional Units may be allowed from electro

mechanic types under minimum 0.5 (to be

functioned as back up meter) with grace

period of 5 (five) years as of the

prevailing of this Grid Code.

c. Will be extended a grace period for 2 (two)

years as of the prevailing of this Grid Code

 220

for meters at the connection points

connected with Generating Companies and Bid

Consumers / High Voltage Consumers that

have been installed before the commencement

of this Grid Code, to comply with

requirements in MC 1.2.1.

MC 9.0 Others

Other matters identifying both technical and

operational which are not stipulated in detail

under this Grid Code, will be arranged under the

Metering Permanent Procedure

 221

Data Requirement Code – DRC

DRC 1.0 Specific Data Needs

DRC 2.0 Obligations of Network Users in

Providing Data Needs

DRC 3.0 Procedures for Data Submission based

on the Request of P3B Sumatera

DRC 4.0 Un-submitted Data

 222

Data Requirement Code – DRC

The Data Requirement Code summarises data needs as stated in

the Network Code. It is the detailed technical data needed by

P3B Sumatera of all Network Users, including

Generator/Generator Company PLN, Regional PT PLN (Persero),

and Major Consumers. The Load Management Plant needs these

detailed data to evaluate its appropriateness against various

operational and technical standards set in the Network Code in

order to guarantee the security, reliability, and efficiency

of the operation of the System.

The need for certain additional data (e.g. data of the

maintenance schedule of the generator unit etc.) clearly

stated in the Appendix of the individual provisions of the

other Codes within the Network Code is no longer listed within

this Code. If there exists any inconsistencies of specified

data needs between the requirements of each Section of the

Network Code to those existing within these Codes, then it is

the requirements existing within the Section of the Network

Code which shall be adhered to.

DRC 1.0 Specific Data Needs

The main data needs are elaborated on in the following 6

sections:

Section 1 Data of Generator Unit Design

This section explains the data needs for the technical design
 223

of each Generator unit, including the general technical data,

reactance and resistance data, saturation parameters, trafo

data, active and reactive capabilities, characteristics of

excitation and governor devices, prime mover data, and power

system stabilizer data.

Section 2 Data of Generator Unit Setting

This section contains the setting data of the generator unit,

including the settings for protection, data control, and the

setting of control equipment for each generator unit.

Section 3 Response Parameters of the Generator Unit

This section contains the response parameters of each

generator unit, such as normal output capabilities,

notification for synchronisation time, latest shutdown time

from the operation, unit flexibility, speed of load change,

and parameters for regulation and precision in fulfilling

dispatch target.

Section 4 Data of Network User’s Installation

This section refers to the installation data of Network Users

(facilities and equipments which are connected to the

Network), including voltage rating, coordination of

insulations, current rating, grounding, contribution of short-

circuit current to the network, and load capability.

 224

Section 5 Data of Network User’s Installation Settings

This section covers the setting data of Network Users’

installations, such as protection data, tap change control

data, and control of reactive compensation.

Section 6 Characteristics of Load at Connecting Points

This section covers the details of load data at each

connecting point, including the projected need for active and

reactive and load characteristics – such as load fluctuations

and dynamic responses to voltage and frequency changes.

DRC 2.0 Obligations of Network Users in Providing Data Needs

Network User DRC 1.0 Section

Large and medium-sized generators 1, 2, 3

Small generators 1, 2

Regional PT PLN (Persero) and Major 4, 5, 6

Consumers

P3B Sumatera shall submit the installation technical data

forms according to requirements.

DRC 3.0 Procedures for Data Submission based on the Request

of P3B Sumatera

DRC 3.1 Each Network User must submit the required data in

accordance to the division in accordance to the

division stated in DRC 2.0. The format of this data

structure is the standard form for data submission.

This format is used for submission of written data

 225

to Load Control Plant unless otherwise stated in a

different section in another section of the Network

Code.

DRC 3.2 The name of the personnel appointed by the Network

User parties must be stated in writing.

DRC 3.3 If there is a computer data link line between the

Network User and the Load Control Plant, data can be

submitted through this facility. In this case, the

Load Control Plant is obligated to provide a common

computer file format in order to enable the Network

User to submit all of its Network User data in

accordance with the requirements of DRC 2.0.

DRC 3.4 Network Users may request the Load Control Plant to

approve of other means of submitting data – such as

magnetic tapes or diskettes – when the computer data

link is obstructed or unavailable.

DRC 3.5 Changes in Network User Data

If the Network User is aware of any change in the

data of equipment already listed at the Load Control

Plant, the Network User is obligated to notify the

Load Control Plant of these changes with the

procedures and within a time frame as stated in the

Network Code sections.

DRC 4.0 Un-submitted Data

All Network Users are obligated to submit data in accordance

to what is stated in the individual sections of the Network

 226

Code and summarised in the Data Requirement Code. If the

Network User does not submit the required data, then the Load

Control Plant shall make estimated data if necessary. This

action does not exempt the Network User from its obligation to

submit the required actual data as soon as possible, unless

the Load Control Plant agreed in writing that actual data is

not required.

Tabulation 1 Design Data of the Generator Unit (Page 1 of 7)

Owner Plant Location Unit Type

Data
Description Unit Value
Item

1.1 General Technical Data

1.1.1 MVA Rate MVA

1.1.2 Capacity Rate MW

1.1.3 Rated Gross MW MW

1.1.4 Terminal Voltage kV

1.1.5 Auxiliary Load in Rate Capacity MW

1.1.6 Reactive Power (output) Rate MVAr

1.1.7 Minimum Load MW

1.1.8 Inertia Constant Rate of Turbo MW-sec

Generator

1.1.9 Short-circuit Ratio

1.1.10 Stator Current (rated) amps

 227

1.1.11 Rotor Current of Rated MVA and power amps

factor, rated terminal voltage, and

rpm

1.2 Resistances

1.2.1 Stator Resistance Rs per

unit

1.2.2 Negative Sequence Resistance R2 per

unit

1.2.3 Zero Sequence Resistance R0 per

unit

1.2.4 Grounding Resistance Re per

unit

1.3 Reactance (unsaturated)

1.3.1 Direct Axis Synchronous Reactance Xd per

unit

1.3.2 Direct Axis Transient Reactance Xd’ per

unit

1.3.3 Direct Axis Sub-transient Reactance per

Xd’’ unit

1.3.4 Quad Axis Synchronous Reactance Xq per

unit

1.3.5 Quad Axis Transient Reactance Xq’ per

unit

1.3.6 Quad Axis Sub-transient Reactance Xq’’ per

 228

unit

1.3.7 Stator Leakage Reactance per

unit

1.3.8 Zero Sequence Reactance X0 per

unit

1.3.9 Negative Sequence Reactance X2 per

unit

1.3.10 Potier Reactance Xpot per

unit

1.3.11 Grounding Reactance Xe per

unit

Tabulation 1 - Design Data of the Generator Unit (Page 2 of 7)

Owner Plant Location Unit Type

Data
Description Unit Value
Item

1.4 Reactance (saturated)

1.4.1 Direct Axis Synchronous Reactance per

Xdsat unit

1.4.2 Direct Axis Sub-transient Reactance per

Xd’’sat unit

1.5 Gross Power (Rate) MW

1.5.1 1.0 PU Saturation Parameter per

 229

unit

1.5.2 2.0 PU Saturation Parameter per

unit

1.6 Time Constant (unsaturated)

1.6.1 Direct Axis Short-circuit Transient Td’ sec

1.6.2 Direct Axis Short-circuit Sub-transient sec

Td’’

1.6.3 Quad Axis Short-circuit Transient Tq’ sec

1.6.4 Quad Axis Short-circuit Sub-transient sec

Tq’’

1.7 Trafo-Generator (Step-up) 1 2 3

1.7.1 Number of Coils

1.7.2 MVA Rate per Coil MVA

1.7.3 Tap Main Voltage Rate kV

1.7.4 Resistance per Coil per

unit

1.7.5 Positive Sequence Reactance per per

Coil unit

1.7.6 Negative Sequence Reactance per per

Coil unit

1.7.7 Zero Sequence Reactance per Coil per

unit

1.7.8 Minimum Tap Voltage kV

1.7.9 Maximum Tap Voltage kV

 230

1.7.10 Tap Change Type (on-load/off-load)

1.7.11 Tap Changer Cycle-time sec

1.8 Reactive Capability (in terminal)

1.8.1 Lagging Reactive Capability at Rated MVAr

Capacity

1.8.2 Lagging Reactive Capability at Minimum MVAr

Generation

1.8.3 Temporary Lagging Reactive Capability MVAr

Tabulation 1 - Design Data of the Generator Unit (Page 3 of 7)

Owner Plant Location Unit Type

Data
Description Unit Value
Item

1.9 Characteristics of Excitation Devices

1.9.1 Field Voltage at Rated MVA and power per

factor, rated terminal voltage, and unit

RPM

1.9.2 Maximum Field Voltage Efdmx per

unit

1.9.3 Minimum Field Voltage Efdmn per

unit

1.9.4 Maximum Field Voltage Increase Speed V/sec

1.9.5 Maximum Field Voltage Decrease Speed V/sec

 231

1.9.6 Maximum Excitation Current Curmx amps

1.9.7 Minimum Excitation Current Curmn amps

1.9.8 DC Gain of Excitation Control Loop PU

Vspp

1.9.9 Regulator Input Filter Time Constant sec

Tvm

1.9.10 Regulator Integration Time Constant sec

P3Bi

1.9.11 Regulator Amplifier Time Constant Tvs sec

1.9.12 Maximum Internal Voltage Regulator PU

Signal Urmax

1.9.13 Minimum Internal Voltage Regulator PU

Signal Urmin

1.9.14 Regulator Stabilizing Gain Vss PU

1.9.15 Regulator Stabilizing Circuit Time sec

Constant Tst1

1.9.16 Regulator Stabilizing Circuit Time sec

Constant Tst2

1.9.17 Excitation Constant Kerr PU

1.9.18 Excitation Time Constant Terr sec

1.9.19 Excitation Saturation Constant 1 Aerr PU

1.9.20 Excitation Saturation Constant 2 Berr PU

1.9.21 Regulator Time Constant Ta Sec

1.9.22 Coefficient of Ceiling Regulator to PU

Terminal Voltage Kc
 232

1.9.23 Voltage Gain from Shunt Self- PU

excitation KP

Tabulation 1 - Design Data of the Generator Unit (Page 4 of 7)

Owner Plant Location Unit Type

Data
Description Unit Value
Item

1.10 Power System Stabilizer

1.10.1 PSS Gain for Mech. Speed Input Signal per

kaom unit

1.10.2 Time Constant for Mech. Speed sec

Measurement Taom

1.10.3 PSS Gain for Elec. Freq. Measurement per

Kafe unit

1.10.4 Time Constant for Elec. Freq. sec

Measurement Tafe

1.10.5 PSS Gain for Elec. Power Input Signal per

Kape unit

1.10.6 Time Constant for Elec. Power Input sec

Signal Measurement Tape

1.10.7 PSS Gain for Terminal Voltage Input per

Signal Kaui unit

1.10.8 Time Constant for Terminal Voltage sec

Input Signal Measurement Taui

 233

1.10.9 Steady State PSS Gain Kpss per

unit

1.10.10 PSS Gain for Turbine Torque Input per

Signal Ktro unit

1.10.11 PSS Gain for Valve Position Input per

Signal Kayt unit

1.10.12 Time Constant for Valve Position Input sec

Signal Measurement Tayt

1.10.13 Stabilising Time Constant Tss sec

1.10.14 Water Hammer Filter Time Constant Tw sec

1.10.15 Output Signal Magnitude Limit Upsmx per

unit

1.11 Unit Governor

1.11.1 Time Constant for Elec. Power sec

Transducer Tp

1.11.2 Freq. Shifted Power Controller Static %

Droop bpf

1.11.3 Freq. Shifted Power Controller %

Transient Droop bpf

1.11.4 Time Constant tdf sec

1.11.5 Power Controller Gain kf per

unit

1.11.6 Power Controller Integration Time sec

Constant Tip
 234

1.11.7 Speed Controller Static Drop bp %

1.11.8 Speed Controller Transient Drop bp %

1.11.9 Regulator Time Constant (Pilot Value) sec

Tr

1.11.10 Main Servo Dead Band Dband per

unit

1.11.11 Main Servo Time Constant Ty sec

1.11.12 Main Servo Max Opening Time Tyo sec

1.11.13 Main Servo Max Closing Time Tyc sec

1.11.14 Max. Main Servo Position Ytmax per

unit

Tabulation 1 - Design Data of the Generator Unit (Page 5 of 7)

Owner Plant Location Unit Type

Data
Description Unit Value
Item

1.11 Unit Governor (cont’d)

1.11.15 Valve Characteristic Yyt %

1.11.16 Elec. Freq./Speed Input Signal Switch

ippc

1.11.17 Power Setpoint Integration Time grdpu sec

1.11.18 SCO Participation Factor bpace per

unit

1.11.19 Pilot Value Opening Time (Hydro) Tro sec

 235

1.11.20 Pilot Value Closing Time (Hydro) Trc sec

1.11.22 Speed Controller Input Speed Time sec

Constant Tm

1.11.23 Temperature-speed Dependency alft

1.11.24 Temperature Input Filter Time Constant sec

Tvr

1.11.25 Temperature-controller [unclear] per

unit

1.11.26 Temperature-controller Integration

Time Constant Tit

1.11.27 Speed-power Controller Amplification sec

Gain Vn

1.11.28 Speed-power Controller Time Constant sec

Tn

1.12 Unit Governor

1.12.15 Sustained Response to Frequency Change MW

1.12.16 Non-sustained Response to Frequency MW

Change

1.12.17 Load Rejection Capability MW

1.13 Prime Mover

1.13.1 High Pressure Turbine Time Constant sec

(GT) Thp

1.13.2 First Reheater Time Constant Tlp sec

1.13.3 Second Reheater Time Constant Tlp sec

 236

1.13.4 High Pressure Turbine Ratio alfhp per

unit

1.13.5 Low Pressure Turbine Ration alfhp per

unit

1.13.6 Boiler Capacity Time Constant P3Bi sec

1.13.7 Heat Transfer Time Constant Tkes sec

1.13.8 Fuel Controller Amplification Kmbr per

unit

1.13.9 Fuel Controller Integration Time sec

Constant Kmbr

1.13.10 Water Starting Time Constant (Hydro) sec

TW

Tabulation 1 - Design Data of the Generator Unit (Page 6 of 7)

Owner Plant Location Unit Type

Data
Description Unit Value
Item

1.13 Prime Mover (cont’d)

1.13.11 Half Reflection Time of Tube (Hydro) sec

Tl

1.13.12 Allievi-constant Zw (Hydro) Zw

1.13.13 Initial Water Pressure (Hydro) Ho per

unit

1.13.14 Turbine Water Flow Dependency to Mech per

 237

Speed komwp unit

1.13.15 Dynamic Pressure Losses (Hydro) rbdyn per

unit

1.13.16 Static Pressure Losses (Hydro) rbsta per

unit

1.13.17 Water Flow for Point wip 1 (min) per

(Hydro) wqmin unit

1.13.18 Water Flow for Point wip 5 (max) per

(Hydro) wqmax unit

1.13.19 Turbine Efficiency (Hydro) wip %

Data Submission
Description
Item Format

1.14 Charts

1.14.11 Capability Charts graphical

data

1.14.12 Open Circuit Characteristics graphical

data

1.14.13 Short-circuit Characteristics graphical

data

1.14.14 Zero Power Factor Curve graphical

data

1.15 Trafo Generator

1.15.1 Tapped Winding text,

diagrams
 238

1.15.2 Vector Group diagrams

1.15.3 Grounding Arrangement text,

diagrams

1.16 Reactive Capability (at Generator Terminal)

1.16.1 Overload at Rated Capacity diagram as a

function of

time

1.17 Excitation

1.17.1 Generator and Exciter Saturation diagram, 50-

Characteristics 120% teg.

rated

1.17.2 Dynamic Characteristics of Over- text, block

excitation Limiter diagram

1.17.3 Dynamic Characteristics of Under- text, block

excitation Limiter diagram

Tabulation 1 - Design Data of the Generator Unit (Page 7 of 7)

Owner Plant Location Unit Type

The following data must be submitted (for each Power plant):

Data
Description Unit Value
Item

1.18 Power Plant Technical Data

1.18.1 Voltage at Connection Point kV

 239

1.18.2 Maximum Total Central Capacity MW

1.18.3 Maximum Current Injection of kA

Symmetrical 3-phase Short-circuit

1.18.4 Maximum Current Injection of kA

Unsymmetrical 3-phase Short-circuit

1.18.5 Minimum Impedance Zero Sequence of per

Generator unit

1.18.6 Minimum Impedance Negative Sequence per

of Generator unit

Apart from that, a single-line diagram of each connecting

point – be it for the power plant or each individual generator

unit – must also be submitted.

Tabulation 2 - Setting Data of the Generator Unit

Owner Plant Location Unit Type

The following data must be submitted in either text or diagram

form:

Data Submission
Description
Item Format

2.1 Protection Setting

2.1.1 Loss of Field text

2.1.2 Under-excitation text, diagram

2.1.3 Over-excitation text, diagram

 240

2.1.4 Overfluxing (V/Hz) text, diagram

2.1.5 Differential text

2.2 Control Data

2.2.1 Details of the excitation loop diagram

described in a block diagram, showing

the transfer functions of each

individual elements and measurement

units

2.3 Control Devices’ Settings

2.3.1 Over-excitation Limiter text, diagram

2.3.2 Overfluxing Limiter (V/Hz) text, diagram

2.3.3 Under-excitation Limiter text, diagram

2.3.4 Manual Restrictive Limiter (if text

fitted)

2.3.5 Load Drop Compensation/VAr Divider text,

function

2.3.6 [unclear] Generator in the form of

lumped element, showing the

components for inertia, damping, and

shaft stiffness
 241

Tabulation 3 - Response Parameters of the Generator Unit (page

1 of 3)

Owner Plant Location Unit Type

The following data must be submitted:

Data
Description Unit Value
Item

3.1 Output Capability

3.1.1 Normal Full Load MW

3.1.2 Normal Minimum Load MW

3.1.3 Minimum Load that can be Maintained MW

(at rated boiler pressure for the

thermal unit)

3.2 Output Capability in Emergency Conditions

3.2.1 Additional Output Power MW

3.2.2 MVAr Reduction for Adding to MW MVAr

Output

3.2.3 Notification Needs minutes

3.2.4 Minimum Time Period for Cancellation minutes

3.3 Notification for Synchronisation

3.3.1 … hours after shutdown time minutes

3.3.2 … hours after shutdown time minutes

3.3.3 … hours after shutdown time minutes

 242

3.4 Earliest Time for Synchronisation

3.4.1 Monday xx

hours

3.4.2 Tuesday to Friday xx

hours

3.4.3 Saturday xx

hours

3.5 Earliest Unit Shutdown Time

3.5.1 Monday to Thursday xx

hours

3.5.2 Friday xx

hours

3.5.3 Saturday and Sunday xx

hours

3.6 Flexibility

3.6.1 Minimum Shutdown Time of Plant Unit minutes

3.6.2 Shutdown Limit (Maximum Number per no./day

day)

Tabulation 3 - Response Parameters of the Generator Unit (page

2 of 3)

Owner Plant Location Unit Type

The following data must be submitted:

 243

Data
Description Unit Value
Item

3.7 Speed of Load Change

3.7.1 …hours after shutdown time

Synchronise to …MW MW/min

…MW to …MW MW/min

…MW to normal full load MW/min

3.7.2 …hours after shutdown time

Synchronise to …MW MW/min

…MW to …MW MW/min

…MW to normal full load MW/min

3.7.3 …hours after shutdown time

Synchronise to …MW MW/min

…MW to …MW MW/min

…MW to normal full load MW/min

3.7.4 Speed of Load Reduction (till MW/min

Shutdown)

3.8 Set-up Parameters

3.8.1 Level of Circulation Reserve MW

3.8.2 Response Time to Full Load minutes

3.9 Accuracy in Fulfilling Dispatcher Target

3.9.1 Error Deviation Standard for a 30- MW

minute period
 244

The following data must be submitted, either in text or

diagram form:

Data Submission
Description
Item Format

3.10 Flexibility

3.10.1 Minimum Operation Period after graphical

Shutdown Time data

3.11 Load Parameter

3.11.1 Synchronising Block Load after …Hours graphical

of Offload data

Tabulation 3 - Response Parameters of the Generator Unit (page

3 of 3)

Owner Plant Location Unit Type

The following Power plant data must be submitted:

Data
Description Unit Value
Item

3.12 Synchronisation Interval

3.12.1 Unit 1 to Unit 2 minutes

3.12.2 Unit 2 to Unit 3 minutes

3.12.3 Unit 3 to Unit 4 minutes

3.12.4 Unit 4 to Unit 5 minutes

 245

3.13 Interval to Shutdown

3.13.1 Unit 1 to Unit 2 minutes

3.13.2 Unit 2 to Unit 3 minutes

3.13.3 Unit 3 to Unit 4 minutes

3.13.4 Unit 4 to Unit 5 minutes

3.14 Flexibility

3.14.1 Minimum Operation Period after graphical

Shutdown Time data

Tabulation 4 - Installation Data of Network User (page 1 of 2)

Network User Connection Point Location

The following Power plant data must be submitted:

Data
Description Unit Value
Item

4.1 Voltage Rating

4.1.1 Nominal Voltage kV

4.1.2 Highest Voltage kV

4.2 Insulation Coordination

4.2.1 Rated Lightning Impulse Withstand kV

Voltage

4.2.2 Rated Short Duration Power Frequency kV

Withstand Voltage
 246

4.3 Rated Short Time Withstand current kA

4.4 Rated Current

4.4.1 Circuit Maximum Current amps

4.5 Grounding

4.5.1 Earth Grid Rated Thermal Current

4.6 Insulation Pollution Performance

4.6.1 Minimum Total Creepage millimeter

4.6.2 Pollution Level as per IEC 815

4.7 Short-circuit Infeed to the System

4.7.1 Maximum 3-phase short-circuit kA

symmetrical infeed, including infeeds

from embedded power plants directly

connected to the User’s system

4.7.2 Total infeed at the instance of fault kA

– taking into consideration induction

motors contribution

4.7.3 Minimum zero sequence impedance of PU

User’s system at connection point

(base: 100 MVA)

4.7.4 Minimum zero sequence impedance of PU

User’s system at connection point

(base: 100 MVA)

 247

Tabulation 4 Installation Data of Network User (page 2 of 2)

Network User Connection Point Location

The following Power plant data must be submitted:

Data
Description Unit Value
Item

4.8 Load Conducting Capabilities

4.8.1 Wherein the Load or Group-load can be

supplied through several connection

points:

4.8.2 Normal proportion of supply from MW

connection point

4.8.3 Normal proportion of supply from MW

connection point

4.9 Embedded Power Plants Connection Network Ke (Base:

100 MVA)

4.9.1 Resistance per

unit

4.9.2 Reactance per

unit

4.9.3 Susceptance per

unit
 248

The following Power plant data must be submitted:

Data Submission
Description
Item Format

4.10 Grounding

4.10.1 Grounding Method text

4.11 Remote Control and Data Transmission text

4.12 Network User Installation Configuration

4.12.1 Operational Diagram showing both single line

existing electrical circuit and diagram

suggested main facilities in the

Network User Installation, including

busbar regulation, switching

facilities, and operational voltage

4.13 Network User Installation Impedance

4.13.1 For each component of the table

configuration of Network User’s

installation: details of serial and

parallel impedance of the positive,

negative and zero sequences, including

mutual coupling between neighbouring

elements (Base: 100 MVA)

 249

4.14 Load Transfer Capability

4.14.1 Transfer regulation for both planned text

and emergency conditions

Tabulation 5 - Installation Setting Data of Network User (page

1 of 2)

Network User Connection Point Location

The following Power plant data must be submitted:

Data
Description Unit Value
Item

5.1 Protection Data

5.1.1 The reach of all protection schemes table %

to the transmission, busbar, and

cable

5.1.2 Number of protective schemes at each text

item

5.1.3 Total number of fault-clearing for table milli-

both short and long distance seconds

disturbances

5.1.4 Detail of reclosure order text

5.2 Tap-change Regulation Data

Delay-time setting for all tap- table second

changer trafo
 250

5.3 Reactive Compensation Regulator

5.3.1 Rating of reactive power of all table MVAr

reactors

5.3.2 Rating of reactive power of all bank- table MVAr

capacitors

5.3.3 Detail of the automatic regulator of text

each reactor and bank-capacitor

Tabulation 6-Load Characteristic

Network User Connection Point Location

The following data should be submitted in form of table,

graphic and/or task:

Data Period Format Unit

Item Description Time Transmit

6.1 Data for all

Load types

6.1.1 Maximum active In the next table MW

power 7 years

6.1.2 Maximum In the next table MVAr

reactive power 7 years

6.1.3 Load types yearly text

(controlled
 251

rectifiers,

big motor,

etc)

6.2 Data for

Fluctuate
Demand

6.2.1 Active power yearly

variation
cycle in one
period

6.2.2 Variation yearly

reactive power
cycle in one
period

6.2.3 Maximum active yearly

power change
rate

6.2.4 Maximum yearly

reactive power
change rate

6.2.5 Shortest In the next table second

interval on 7 years, it
active and is observed
reactive power yearly
fluctuation
repetition
 252

6.3 Hugest change

step

6.3.1 For active yearly table MW/second

power

6.3.2 For reactive yearly table MVAr/second

power

Additional Rules

This addition rules arrange the exception of Network

User Installations (Grid) as connected in Sumatera

Electrical Power System on the basis of Power

Purchase Agreement (PPA) and Energy Sales Contract

(ESC) signed prior to the prevailing of Grid Code.

AC 1.0 In this matter the provision and the extent so

required under PPA and ESC which is not in

accordance with the requirements set forth in

Connection and Operation Rules would be discussed in

separable part by Generation PLN/State Electric

Power Company related to Load Regulating Center in

order to achieve operational agreement.

AC 1.1 Generation PLN/relevant Electric power Company file

supporting evidences showing inability of its

generator units following the requirements of

operation set out in Sumatera Network Network in 2

(two0 months as of the effectiveness of this Rules.

AC 1.2 Load Regulating Centre evaluates evidences as

 253

submitted by Generation PLN/State Electric Power

Company and if it is deemed necessary they would

discuss it with Generation PLN/State Electric Power

Company in order to obtain operational reference.

Such operational reference on the basis of

evaluation and/or discussion is settled within 2

(two) months as from the Load Regulating Center

receives the aforementioned evidences, signed by

Generation PLN/relevant Electric Power Company and

Load Regulating Center.

AC 2.0 As from the effectiveness of this Network Rule until

the achievement of new operational agreement, then

subsequently the provision and the extent set forth

in PPA and ESC which have been required as

operational reference.
 254

Appendix A

Schedule Summary

A. Schedule of Load Prediction, Long Term

Maintenance and Operation

B. Network Management

C. Monthly Operation Plan (For the subsequent

months)

D. Weekly Operation Plan (For the subsequent

weeks)

E. Daily Dispatch Plan (For the subsequent

days)

F. Measurement and Settlement

 255

Appendix A-Schedule Summary

This appendix summarizes the entire schedules of

operational activities and network plan set forth in

this Network Rule. The abovementioned activities are

organized in 7 categories. Any parts set forth in

relevant Network Rule for each activity are indicated in

bracket, while if there is incompliance between this

summary and schedule determined under Network Rule, then

the schedule set out in Network Rule would be used.

A. Schedule of Load Prediction, Long Term Maintenance and

Operation

1. Grid Operational Schedule in the subsequent 1 year

1st October : Load Regulating Center issues Long

Term Operation Plan Draft (SDC

2.2).

15th December : Load Regulating Center issues Long

terms Operation Recent Plan(SDC 2.0

and SDC 2.5)

1st May : Load Regulating Center issues Long

Terms Operation Plan of Middle Year

Revision draft (SDC 2.2).

15th June : Load Regulating Center issues Long

Term Operation Plan of Middle Years

Recent Revision (SDC 2.5).

2. Maintenance Schedule in the following 1 year

 256

1st September : Generation PLN/Electrical Power

Company submits Maintenance Plan

Draft in the following 1 year in

respect of its generator unit (SDC

2.3) to the Load Regulating Center

15th December : Load Regulating Center issues the

Recent Network Maintenance Plan in

the following 1 year (SDC 2.3).

1st May : Electrical Power Company submits

semiannual maintenance plan

revision in the following 1 year in

respect of its generating unit (SDC

2.3)

1st June : Load Regualting Center issues

Semiannual Recent Revision, Network

Maintenance Plan in the following 1

year (SDC 2.3)

3. Load Prediction in the following 1 year

1st September : Area submits load prediction in

each main powerhouse in one year in

the future (SDC 2.1) to the Load

Regulating Center

15th September : Load Regulating Center settles Load

Prediction in 1 year in the future

(SDCA 1.3.0).

4. Annual Report of Network Protection Working

 257

Performance (in the previous year)

31st July : Load Regulating Center issues

reports (OC 12.3)

B. Network Management

Annual Network Operation Summary (for the previous year)

31st March : Network Management Committee (if it has

been organized) publishes Annual Network

Operation Summary Report (GMC 6.1).

C. Monthly Operation Plan (For the subsequent months)

In the consecutive 5 months : Generation PLN/Electric Power

Company submits information

(data) of preparedness and

maintenance on its units (SDC

3.1)

In the consecutive 10 months : Load Regulating Center issues

power requirement (SDC 3.1)

In the consecutive 15 months : Generation PLN/Electric Power

Company submits information

regarding energy Generation

variable cost (SDC 3.1)

In the consecutive 20 months : Load Regulating Center issues

Monthly Operation Plan (SDC

3.1)

In the consecutive 25 months : Network User submits the

response in respect of Monthly

Operation Plan (SDC 3.1)

 258

In the consecutive 28 months : Load Regulating Center revises

Monthly Operation Plan, if it

is deemed necessary (SDC 3.5).

D. Weekly Operation Plan (For the subsequent weeks)

Tuesday at 10.00 : Generation PLN/Electric Power Company

submits revision of unit preparedness

status (SDC 4.5)

Wednesday at 15.00 : Load Regulating Center issues Weekly

Operation Plan (SDC 4.5)

Thursday at 10.00 : Network User submits the response in

respect of Weekly Operation Plan (SDC

4.5)

Thursday at 15.00 : Load Regulating Center issues Recent

Weekly Operation Plan (SDC 4.5)

E. Daily Dispatch Plan (For the subsequent days)

At 10.00 : Generation PLN/Electric Power Company submits

the change of unit preparedness or

characteristic of unit operation (SDC 5.1 and

SDC 5.6)

At 15.00 : Load Regulating Center issues Daily Dispatch

Plan for the subsequent days (SDC 5.6).

 259

F. Measurement and Settlement

On the first day of each month : Meter read and Preparation

of Minutes by P3B Sumatera

and signed by Electric

Power Company (SC 2.1) and

preparation of Minutes by

P3b Sumatera and signed by

the Area (SC 2.3).

On the 9th working day : Upon the return of Minutes

which have been signed to

P3B Sumatera. Subsequently,

P3B Sumatera issues

Statement of Energy

Transaction to Electrical

Power Company if there is

no issue in respect of

measurement data (SC 2.1).

On the 15th working day : After the signed Minutes is

returned to P3B Sumatera.

Subsequently, P3B issues

Statement of Energy

Transaction to the Region

if there is no issue in

respect of measurement data

(SC 2.3).
 260

Terminology and Definition

(Glossary)

This glossary defines terminology as required in this Network

Rule. The consistent use in respect of such definition would

decrease any possibility of miscomprehension for the

provisions set forth in Network Rule. In the event that a

terminology or word is declared in particular ways in one Part

of the Network Rule, then the prioritized statement set out in

the aforementioned Network Rule would be compared with the

description in this Glossary.

The following words and statements required in the Network

Rule shall have the following meaning, unless the issues

require such other definition otherwise:

Device/Equipment it is tool/device/equipment

connected to, or constituting

part of, and/or transmission

network user and as required

to produce, to arrange or

measure the electric.

ANSI American National Standard

Institute (Institutsi Standar

Nasional Amerika)

Area Control Center (ACC) Regional Load Control: to

control and arrange part of

150 kV and 60 kV in Sumatera

 261

Grid.

Excitation Flow Flow which is flowing through

reel field in a generator

Black Start Start of one generating unit

made without power supply from

outside

Code Sumatera Grid Code

Network Code several regulation and

technical standard as well as

operation in order to ensure

reliable, save and efficient

Sumatera System Operation.

Automatic Generation Control(AGC)Automatice Generation

Control, it is computerization

facility arranging

automatically electric power

which is out from Generator as

a response on system frequency

change. This matter may cause

the optimal of generation cost

in its entirety and transmit

of signal to change set point

governor from generator unit

Load Electric power consumption in

each connection point, or the

amount of energy consumption

 262

as reserved by the network.

Top Load the highest load which is

supplied by Network or certain

user

Daily Top Load Daily highest load

Synchronization Load Temporary output level on one

generator unit in which it

could be synchronized.

Cold Reserve Generator unit capacity which

could be started and connected

to the Network in 4 hours

Long Term Reserve Generator unit that could be

started and connected within

more than 4 hours but less

than 2 days

Operation reserve The capacity is available

within operation period scale,

which in its realization, it

has been operated to produce

electrical power so scheduled

as reserve capacity.

Rotation Reserve (OC 2.1) Generation Capacity that is

not loaded and ready to serve

the increase of load. It is

indicated in percentage (%)

for system load or in MW. On

 263

the basis of Load Control

Centre, generator output that

could be connected with the

system in 10 minutes and load

that could be released in 10

minutes could be also deemed

as rotation/hot reserve

component.

Active Power Generation, distribution or

use of electric power as a

result of multiplication

between voltage and

alternating current component

that is commonly declared in

kilowatt (kW) or megawatt

(MW). It is part of apparent

power of VA or kVA that could

be transformed to be sparkle,

physical movement or hot.

Reactive Power it is part of electrical power

generating and maintaining

electric field/magnetic of

alternating current device.

Reactive power should be

supplied to magnetic device

such as motor and voltage

 264

regulator and should be

supplied to compensate the

losses of reactive on

transmitting facility. It is

mentioned in kiloVars (kVAr)

or megaVars (MVAr).

Apparent Power It is as a result of

multiplication on voltage and

flow in the series of electric

mentioned in kilo voltampere

(kVA) or mega voltampere

(MVA), containing both active

and reactive power.

Declaration Statement of Preparedness

Plan, points of operation

characteristic or such other

factors made by Generator

PLN/Electric Power Company in

respect of its generator units

pursuant to Operation and

Dispatch Plan Rule (SDC) as

set forth in Appendix 3.

Dispatch Instruction submitted to

Generation PLN/Electrical

Power Company in order to load

the units into certain levels

 265

whose entire number is in

accordance with the

requirement/load, through

reliable and economic

procedures.

Daily Dispatch Daily load for power plant

expected in connection with

the Operation Plan Rule and

Dispatch (SDC 5.0).

Harmonic Distortion Distortion caused by the non-

linear characteristic of

certain electricity power

equipment, such as rectifier,

inverter, motor engine with

varying speed. The harmonic

current generated in a Grid,

together with the frequency

response characteristic, may

cause harmonic voltage

distortion. The harmonic

voltage distortion is stated

in % over voltage in 50Hz

nominal frequency.

Active Energy Active power distribution

speed in a time period,

usually measured in watt-hour

 266

(Wh) or kilowatt-hour (kWh).

Load Factor Ratio of average output or

load to maximum output or load

in a time period.

Flicker Minor change on voltage

occurring rapidly and

continuously, which may be

detected by human eyes when

occur in fluorescent light.

Outage Unplanned event resulting in

abnormal condition in a Grid.

Working Day Everyday in a week, except

Saturday, Sunday, or Holiday,

when the government offices

are not off duty.

Heat Rate Thermal energy used by a

generating unit in producing a

unit of electric power, stated

in GJ/MWh or kCal/kWh

Hydro Hydraulic power used to

produce electric power.

IEC The International

Electrotechnical Commission

IEEE The Institute of Electrical

and Electronic Engineers

Incremental Transmission Loss Change in transmission loss

 267

resulting from the generation

change of certain unit.

Long-term Operation Schedule Statement showing the

preparatory plan of the

generating units, and the

method of scheduling to meet

the load forecast within 1

year to come (SDC 2.0).

Maintenance Schedule A schedule showing outage plan

for maintenance

implementation.

Network, Grid Sumatra Grid used to

distribute power consisting of

conductor in a voltage of 66

kV, 150 kV and 275 kV, along

with Main Powerhouse,

Transformer and any other

components.

SCC Sumatra Control Center

Capacity Output power which may be

achieved by a generating unit,

Transformer, Conductor or any

other equipment, stated in MW

or MVA.

Droop Characteristic Generating governor parameter

defined as frequency change

 268

percentage producing output

power change at 100% of the

rated output. For example, the

generation of 1000 MW with a

droop characteristic of 5%

will result in the increased

output of 10 MW for each

decreased frequency of 0.25

Hz, from 50 Hz.

Economic Operation Characteristic The Data of operation

providing information on the

economic operation of the

generating unit.

Characteristic of Operation It means Parameter defining a

capability of generator unit

in responding dispatch

instruction

Reliability It means capability in

supplying power without

disconnecting in any and all

conditions

Requirement/Load Amount of active and reactive

power which has been supplied

or it is expected that is it

would be supplied by entire

 269

customers through Grid or part

of System declared in megawatt

and megaVAr within certain

time periods

Load Rate Rate of Improvement of load on

generator unit connected to

the system in operator

controlled condition and

normal operation, it is

declared in MW/Minutes.

Voltage Blink Decrease of RMS (root mean

square) voltage in fraction of

millisecond until several

seconds

Urgent Circumstance Serious condition influencing

reliability of System and

comfort of customer

Planned output System facility output as

proposed by P3B Sumatera or

generating unit proposed by

Generator PLN/Electric Power

Company within the period as

approved by Load Controlling

Center

Black Start Capability It is capability of one

 270

generating center to conduct

black start operation

Contingency It is an incident due to

failure on one or more

components such as Generator,

Transformer

Preparedness/Procurement Capable/readiness time

measurement on one generator,

transformer unit or such other

facilities in service

operation whether it is

operated. Such measurement

would be declared in

percentage (%) of its

availability in evaluated

periods.

Urgent Condition Situation where integrity,

security or stability in its

entirety or in its part is in

threatened condition.

High Consumer (=TT Consumer) It is consumer connected

directly to high voltage

system

Working Safety Coordinator Any individual as

appointed/assigned by P3B
 271

Sumatera or System User in

order to coordinate any

working safety issues in

connection point, including

preparedness, application,

approval and revision in

respect of local safety

procedure.

Annual System Operation Report Operational Plan report in

previous years, and analysis

of Grid Capability in serving

projection of load and

generation rate for the 5

subsequent years. This annual

report shall be prepared by

P3B Sumatera.

Annual System Operation System Operation Summary as

Summary Report prepared and issued by System

Management Committee, (if

Committee has been

established).

Lithography Handwriting

Merit Order Generator unit list with

subsequent marginal operation

cost, including: start up and

 272

shut down cost, minimum time

of start up and out time, fuel

obstacles, as well as such

other operation obstacles.

MNEM (Mnemonic) means group

abbreviations of ‘ALARM” for

displayed messages consisted

of synchronized format,

information format and

terminated format.

P3B Sumatera PLN of Distribution and Load

Controlling Center of Sumatera

constituting PLN unit as the

owner of System and managing

party of Electric power System

in Sumatera Island

Manual load shedding Load shedding carried out by

shedding PMT serving the load.

Automatic Load shedding with Load shedding conducted by the

low frequency operation with low frequency

Load shedding Load decrease operated

deliberately (either

automatically or manually)

with disconnection on certain

 273

load due to abnormal incident,

in order to maintain the

integrity of System and to

prevent higher extinction

System user It is institution

using/requiring the system

(Generating company, Area, big

consumer)

Generation Production or facilities as

required to produce electric

Reactive Power Generation Reactive power capacity which

could be produced to be

maintained.

Minimum Generation Minimum output of one

generation unit which could be

maintained.

Disconnection Disconnection electrically on

System user equipment from the

System

Automatic Voltage Regulator Regulator of automatic and

continue excitation on one

Generator unit to arrange its

terminal voltage.

Landing Provision of one electrical

connection between one or more

 274

conductor and land as required

in order to safe personnel,

public and equipment safety

Voltage decrease It is a procedure in order to

decrease load by decreasing

voltage.

Meter equipment Measuring device

Measurement equipment/metering All equipment connecting with

system metering system including:

flow transformer, voltage

transformer, measuring device.

Landing equipment It is equipment designed for

land

Weekly period From Friday until the next

Thursday.

Circumstance It is unplanned incident in or

in connection with System

which has or may have caused

violation of Operation Code or

an incident on a person

Agreement of Electric Power Agreement declaring concept,

Purchase condition and price for

Generation PLN/Electric Power

Company to sell their

electrical power to the

 275

purchaser.

Statement of It is a statement in respect

Preparedness/Procurement of procurement of Generator

units as expected by

Generation PLN/Electrical

Power Company, in connection

with Operation and Dispatch

Plan Rule, Appendix 3.

Generation PLN/Electrical Generation PLN Unit/Company

Power Company obtaining one or more

generating unit distributing

power to the System

PLC Power Line System,

communication media through

high voltage air system

PLTA (hydroelectric power Generator center requiring

plan) hydroelectric power.

PMT Power breaker in order to

close and open series of

electric either in unloaded or

loaded condition with certain

capability to break short

connection flow. In English it

is formerly known as circuit

breaker (CB).
 276

Local Working Safety Procedure It is working safety procedure

which is applied by P3B

Sumatera or System User,

including activities performed

in respective connection

point.

Load projection Load prediction as expected

that it would occur in system.

PT. PLN (Company) in Sumatera Business units of PLN which

Area are on the duty to operate

distribution system in working

area including Sumatera Island

Load Controlling Centre (SCC) Load controlling center of P3B

Sumatera conducting schedule

and dispatch of generator

units and supervision and

switching Grid

Low Frequency Rele It is Rele that could detect

system frequency operating if

frequency decreases below its

setting price

Weekly Operation Plan Statement showing outage plan

of generator unit, generator

center and system in weekly

period
 277

Load plan Load projection and subscribe-

load which is expected that it

would be required by the

customer

Weekly maintenance plan Schedule showing outage plan

of generator unit, generator

center and system within

weekly period.

Annual System development plan 10 years plan for development

and power of system and

additional of Generator in

order to fulfill demand

projection

Losses Electric power losing in

Transformer point and

transformer conductor/cable in

the system.

Certificate of Connection Written confirmation as issued

point by P3B Sumatera to System User

that one connection point has

been approved by P3B Sumatera

and has been ready to energize

(voltage aid)

Synchronization Equal process on frequency,

voltage, fasa of one generator

 278

unit and system in such a way

that it fulfills requirement

of connection to be conducted.

System Combination between System and

all equipment of System user

connected to the System

SCADA system Supervisory Control and Data

Acquisition (SCADA) System

shall constitute long distance

controller and measurement

used in electric power. Such

SCADA collect operational data

such as: Frequency, voltage,

power flow, PMT position in

the system and to process and

to display it in Load

Controlling Centre and

Unit/Sub-unit of Load Control

Start It is process of generator

unit from shut down to

synchronized status to the

system

Unreserved energy study It is method predicting any

possibility of failure of load

service for expansion plan on

 279

certain power source for load

prediction. The required

criteria for such study shall

be percentage (%) of energy

prediction (MWh) which fails

to be served or to be

fulfilled.

High Voltage (TT) Voltage above 35 kV until 150

kV.

TET High Extra Voltage of 500 kV

in Sumatera system

Connection Point Connection Point between

System and installation of

system user

Generator Transformer Transformer required to

converse generator voltage to

the required level on

connection point to Grid

Generator unit Initial motor combination and

generator (and such other

equipments) generating

alternating current electrical

power.

Minimum output time Minimum time of generator unit

out of the system after shut

 280

down.

Startup minimum time Minimum time as required for

generator unit to be able to

connect to the System (Grid)

Time Time as recorded in measuring

time, whose accurateness is

related directly to the

frequency of Grid.
 281

PT. PLN (STATE ELECTRICAL POWER COMPANY) (COMPANY)

DECREE OF BOARD OF DIRECTOR OF PT PLN (COMPANY)

Number: 149.K/DIR/2006

REGARDING

FORMATION OF GRID CODE ARRANGING TEAM ON SUMATERA ELECTRICAL

POWER SYSTEM

BOARD OF DIRECTORS OF PT PLN (COMPANY)

Considering : a. that in order to improve company

performance such as through the

improvement of efficiency, quality and

reliability on electrical power

procurement in the activity of

transmission and operation effort in

Electrical Power System (STL) in Sumatera,

then it shall be deemed necessary to form

Grid Code Arranging Team of Sumatera

Electric Power System;

b. that the establishment of Arranging Team

of Grid Code of Sumatera Electric Power

System as referred to in letter a as

mentioned hereinabove, it shall be

necessary to be stipulated by virtue of

Decree of Board of Directors of PT PLN

(Company).
 282

In viewing of : 1. Law of the Republic of Indonesia Number 15

Year 1985 regarding electrical power;

2. Law of the Republic of Indonesia Number 19

Year 2003 regarding State Owned

Enterprise;

3. Regulation of Government of the Republic

of Indonesia Number 10 Year 1989 regarding

Procurement and Utilization of Electrical

Power as amended by Regulation of

Government of the Republic of Indonesia

Number 3 Year 2005 and Regulation of

Government of the Republic of Indonesia

Number 26 Year 2006.

4. Regulation of Government of the Republic

of Indonesia Number 23 Year 1994 regarding

the Transfer of Form of Public Company of

State Electric Company to be Company (the

Company).

5. Regulation of Government of the Republic

of Indonesia Number 45 Year 2005 regarding

Establishment, Management, Supervision and

Liquidation of State Owned Enterprise.

6. Articles of Association of PT. PLN

(Company).

7. Decree of Minister of State Owned

 283

Enterprise Number KEP-180/M-MBU/2003

regarding Termination and Appointment of

Members of Board of Directors of Company

of PT Perusahaan Listrik Negara;

8. Decree of Board of Director of PT PLN

(Company) Number 001.K/030/DIR/1994

regarding the Effectiveness of Regulation

in connection with Transfer of Form of

public company;

9. Decree of Board of Director of PT PLN

(Company) Number 062.K/010/DIR/2003

regarding Organization and Working

Procedure of PT Perusahaan Listrik Negara

(Company) as amended by virtue of Decree

of Board of Director of PT PLN (Company)

Number 092.K/010/DIR/2004 and Decree of

Board of Director of PT PLN (Company)

Number 141.K/DIR/2005;

HEREBY DECIDES

To Stipulate : DECREE OF BOARD OF DIRECTOR OF PT PLN

(COMPANY) REGARDING FORMATION OF GRID CODE

ARRANGING TEAM ON SUMATERA ELECTRICAL POWER

SYSTEM

FIRST : To form Grid Code Arranging Team on Sumatera

 284

Electrical Power System hereinafter shall be

referred to as STL Sumatera Grid Code Team.

SECOND : The Structure of Membership of Sumatera STL Grid

Code Team shall comprise:

I.DIRECTING TEAM : DIRECTOR OF TRANSMISSION AND

DISTRIBUTION

II.PATRON TEAM : - DEPUTY DIRECTOR OF

TRANSMISSION DEVELOPMENT

- DEPUTY DIRECTOR OF

DISTRIBUTION DEVELOPMENT

- DEPUTY DIRECTOR OF

GENERATION DEVELOPMENT

- DEPUTY DIRECTOR OF SYSTEM

PLAN

- DEPUTY DIRECTOR OF

GENERATION COMPETITION

MANAGEMENT

III.RESOURCE PERSON: -General Manager of PLN of

Sumatera P3B

-General Manager of PLN of

Sumbagut Generation

-General Manager of PLN of

Sumbagsel Generation

-General Manager of PLN of NAD

(Nanggroe Aceh Darussalam)

 285

Area

-General Manager of PLN of

North Sumatera Area

-General Manager of PLN of

West Sumatera Area

-General Manager of PLN of

Riau Area

-General Manager of PLN of

S2JB Area

-General Manager of PLN of

Lampung Area

-Chairman of PLN of North

Sumatera & Aceh Pikitring

-Chairman of PLN of Sumbagsel,

West Sumatera and Riau

Pikitring

IV. EXECUTIVE TEAM:

1. Manager of Transmission Operation Development

of PT PLN (Company) Head Office: Chairman

2. Manager of System Operation of PLN of P3B

Sumatera: Vice Chairman

3. Deputy Manager of System Plan of PLN of P3B

Sumatera: Secretary

4. WORKING TEAM I: Sub Field of Electric Power

Installation Development

-Manager of Transmission Development

 286

Management Out of Java of PT PLN (Company)

Head Office: Chairman

-Manager of Transmission of PLN of P3B

Sumatera: Secretary

-KSOP of PLN of Sumbagut Pikitring: Member

-KSOP of PLN of Sumbagsel, Sumbar and Riau

Pikitring: Member

-Transmission Expert of PLN Head office in

DDTRS: Member

-Scada & Tel Expert of PLN Head Office in

DDTRS: Member

-Main Powerhouse Expert of PLN Head Office in

DDTRS: Member

-Deputy Manager of Development O& M

Transmission of PLN of P3B Sumatera: Member

5. WORKING TEAM II: Sub Field of Operation Plan

& Implementation

-Planning Manager of PLN of P3B Sumatera:

Chairman

-Deputy Manager of Operation Plan of PLN of

P3b Sumatera: Secretary

-Technical Manager of PLN of NAD Area: Member

- Technical Manager of PLN of North Sumatera

Area: Member

- Technical Manager of PLN of West Sumatera

 287

Area: Member

- Technical Manager of PLN of S2JB Area:

Member

- Technical Manager of PLN of Riau Area:

Member

-Technical Manager of PLN of Lampung Area:

Member

-Manager of Production Field of PLN of Kilsu:

Member

-Manager of Production Field of PLN of

Kilsel: Member

-Manager of UPB of Sumbagut: Member

-Manager of UPB of Riau Source: Member

-Manager of UPB of Palembang: Member

6. WORKING TEAM III: Sub Field of Measurement of

Settlement

-Assistant of DD PKP of PT PLN (Company) Head

Office: Chairman

-Deputy Manager of Transaction of PLN of P3B

Sumatera: Secretary

-Commercial Manager of PLN of NAD Area:

Member

-Commercial Manager of PLN of North Sumatera

Area: Member

-Commercial Manager of PLN of West Sumatera

Area: Member
 288

- Commercial Manager of PLN of Lampung Area:

Member

-Planning Manager of PLN of Kitsu: Member

-Planning Mangaer of PLN of Kitsel: Member

-Manager of Financial and Commercial of PLN

of P3B Sumatera: Member

THIRD : The followings are the duties of STL Sumatera Grid

Code Team:

1. To arrange and recommend provisions set forth in

grid code consisting of;

a. Electric Power Installation

b. Operation Plan & Implementation

c. Measurement and Settlement

d. Data Requirement

2. To conduct comparison study of Grid Code

Application in Java, Bali STL

3. To submit report periodically for the activities

of STL Sumatera Grid Code Team to Director of

Transmission and Distribution.

FOURTH : The membership of STL Sumatera Grid Code Team shall

not release their respective member from daily

official duties.

FIFTH : STL Sumatera Grid Code Team in performing their

duties as referred to in Dictum Three shall be held

 289

liable to BOARD OF DIRECTOR OF PT PLN (COMPANY).

SIXTH : Any and all expenses or costs arising as a result

of the implementation of duties of STL Sumatera

Grid Code Team shall be borne by budget of PT PLN

(Company).

SEVENTH : Service Period of STL Sumatera Grid Code Team as

referred to in FIRST Dictum shall be 6 (six) months

as of the month of this Decree is stipulated and

declared to be liquidated after the team presents

STL Sumatera Grid Code and it is approved by

Director of Transmission and Distribution.

This Decree shall take effect as of the date of commencement.

Stipulated in Jakarta

On the date of 10th October 2006

PRESIDENT DIRECTOR

[Signed]

EDDIE WIDIONO S.