You are on page 1of 39

Rural Areas Electricity Company

Standard Operating Procedure


Of
Duqm Distribution Control Center
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Contents
Preface ................................................................................................................................................................................ 3
Objective ............................................................................................................................................................................. 4
STANDARD OPERATING PROCEDURE APPLICATION AREA ................................................................................................ 5
DEFINITIONS OF TERMS ...................................................................................................................................................... 6
RELATED SOP , REGULATION , POLICES .............................................................................................................................. 7
INVOLVED PERSONS ........................................................................................................................................................... 8
PLANNED SWITCHING PROGRAM ..................................................................................................................................... 10
PLANNED SWITCHING PROGRAM - PREPARATION STAGE ........................................................................................... 10
PLANNED SWITCHING PROGRAM WORKFLOW – EXECUTION STAGE .......................................................................... 13
PLANNED SWITCHING PROGRAM – DOCUMENTATION STAGE.................................................................................... 17
Un-PLANNED SWITCHING PROGRAM ............................................................................................................................... 19
Un-PLANNED SWITCHING PROGRAM - PREPARATION STAGE ..................................................................................... 19
Un-PLANNED SWITCHING PROGRAM – EXECUTION STAGE ......................................................................................... 20
Un-PLANNED SWITCHING PROGRAM – DOCUMENTATION STAGE .............................................................................. 25
EMERGENCY SWITCHING PROGRAM ................................................................................................................................ 27
EMERGENCY SWITCHING PROGRAM – INCIDENT REPORT STAGE ............................................................................... 27
EMERGENCY SWITCHING PROGRAM – EXECUTION STAGE .......................................................................................... 28
EMERGENCY SWITCHING PROGRAM – DOCUMENTATION STAGE ............................................................................... 31
11 Kv NOD update ............................................................................................................................................................ 33
11 Kv NOD update – DOCUMENTATION STAGE ........................................................................................................... 33
33 Kv NOD update ............................................................................................................................................................ 36
33 Kv NOD update – DOCUMENTATION UPDATESTAGE .............................................................................................. 36

Page | 2
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Preface

The Company accepts and recognizes its legal and moral responsibilities for ensuring the safe
design, construction, operation and maintenance of equipment and the provision of safe systems
of work which protect the health and safety of employees, contractors and the public. These
responsibilities rank equally with all other business objectives of the Company.

Tanweer operational staff and who is undertaking work on behalf of Tanweer on its
distribution system shall provide detailed switching program sequence to proceed with
planned / unplanned / Emergency switching on the HV system. This procedure defines how
work on HV distribution network will be executed using Switching Program. Furthermore,
Tanweer operational staff and who is working on behalf of tanweer on HV distribution system
are required to undertake unplanned and emergency switching, when events require
response to restore supply or isolate plant and circuit to isolate fault or danger.This
procedure defines how unplanned / emergency switching is to be carried out on Tanweer
distribution system.

In additional, any changes to be done on existing 11kV and 33 kV network, the person
responsible MUST update network operating diagram accordingly, therefore This procedure
defines how the update is to be carried out.

Page | 3
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Objective

The objectives of this SOP are:

• To explain how to meet the obligations of getting approval on switching program to


undertake work on Tanweer distribution system.
• To set guidelines and timetable to undertake Switching Program.
• To specify the information to be provided amongst the staff of Tanweer and who is
working on behalf of Tanweer to ensure safe switching and comply with the ESR.
• To define roles and responsibilities of approving and conducting the Switching
Program.
• To explain how to meet the obligations before undertaking switching on the HV
networks for unplanned/emergency events;
• To explain the procedure when there is urgent need to act in an emergency situation
when people, plant or circuits are in immediate danger.
• To explain the procedure to update the 11 kV and 33 kV Network Operating Diagram
to ensure the network information change is updated.
• To define roles and responsibilities on reporting and document outage on tanweer
distribution system.

Page | 4
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

STANDARD OPERATING PROCEDURE APPLICATION AREA

This SOP applies to:

• Distribution Control Center.


• Network Operations All Zones
• Any part involves within switching program activity.

Page | 5
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

DEFINITIONS OF TERMS

ESR ELECTRICAL SAFETY RULES


CME CIRCUIT MAIN EARTH
DCC DISTRIBUTION CONTROL CENTRE
AEP AUTHORIZED ELECTRICAL PERSON
SAEP SENIOR AUTHORIZED ELECTRICAL PERSON
DCP DISTRIBUTION CONTROL PERSON
PTW PERMIT TO WORK
LOA LIMITATION OF ACCESS
SFT SANCTION FOR TEST
HV HIGH VOLTAGE
LV LOW VOLTAGE
SCADA SUPERVISORY CONTROL AND DATA ACQUISITION
GIS Geographical Information System
CA Control Analyst
NOD Network Operating Diagram
ZL Zone Lead

Page | 6
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

RELATED SOP , REGULATION , POLICES and codes

1. Electrical Safety Rules


2. RAEC operation code of practice
3. Outage management procedure
4. System Incident reporting
5. System emergency contingency plan
6. Significant incident

Page | 7
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

INVOLVED PERSONS

Abbreviatio
n Responsible Person Responsibility in the process
used in
SOP
One who is responsible for planning
functions required at Zone such as
Authorized Electrical preparing the switching program, and
SAEP
Person responsible for carrying out on-site
activities. This reference covers SAEP,
SAEP 1 and SAEP 2.

One who is responsible for reviewing and


ZL/ head of assigning the prepared switching
ZONE LEAD
operation
program.

One who is responsible for review,


approval and
routing switching program to ZONE
Distribution Control LEAD/ head of operation in the zone and
DCP Person
communicating to the relevant parties for
at the DCC
further feedback. He is responsible for
instructing, recording and switching
operations on SCADA and by SAEP.

CA Control Analyst at the • One who is responsible for


DCC monitoring the
activities within the DCC to ensure that
changes
to the 11 kV and 33 kV network are
updated
within the records systems. Generating
reports and required analysis
• One who is responsible for
updating the SCADA
system
HSCADA Head of SCADA

Page | 8
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

• One who is responsible for


updating the GIS
HGIS Head of Geographical
system
information system

• One who is responsible to manage


all distribution control center activities.

HDCC Head of Distribution


control center

Page | 9
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

PLANNED SWITCHING PROGRAM


PLANNED SWITCHING PROGRAM - PREPARATION STAGE

Tanweer needs to have organized sequence procedures in place in advance of undertaking


switching on the HV network. Preparing Switching Program in a timely
manner is mandatory to secure safe operation and comply with Electrical Safety Rule.

The workflow below explains the sequence of PLANNED Switching Program in preparation
stage.

The workflow defines roles for each part involving in switching program cycle. The switching
program must be prepared and approved 3 days before execution.

In exceptional circumstances, where due to unforeseen network or customer requirements,


the SAEP may request permission to complete the process within 3 days of the planned
work but this is only possible with the prior agreement and authorization of the Head of
Control.

Page | 10
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

PLANNED SWITCHING PROGRAM WORKFLOW – PREPARATION STAGE

DCP SAEP Zone Lead Call


center
Start
Switching program not
approved, advise SAEP
to review and resubmit.

Not approve
Create
Switching
Review and approve program and
switching program send to DCP
through oracle
including all
Approve required
document for
approval
Save copy of the
approved switching
program in the shared Send SMS
file between DCC + to
operation Zones + customers
QHSE. Send SMS to
call center.

SAEP receive
approved
switching
program and
proceed the
process as
below

Page | 11
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Required
Step description owner
document
For planned work, SAEP will Create
Switching Program within Oracle
1.prepared
Switching Program sequence shall
be prepared by SAEP describing the Switching
objective of the switching including program
details for each step such as sheet
Prepare
opening and closing of circuit
1 Switching breakers, isolation, application of 2. NOD SAEP
Program CME’s, application of safety lock and
caution . The SAEP will provide
single line diagrams (NOD’s)
showing the network before the
planned work and the proposed
network after the planned work being
completed.
DCP reviews / approve / or reject the
submitted switching program based
on ESR compliance. DCP then will
Review / issue reference number and forward
approval of approved switching program to DCP/
2 1. Approved
SAEP.
switching Switching ZL
A copy of the approved
program program
Switching Program will be saved
in the shared folder by the DCP/ sheet
upload on oracle. 2. NOD
Approved
Receive
Switching
approved
3 SAEP receives approved switching program SAEP
switching program and plan for execution. sheet
program
2. NOD

Page | 12
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

PLANNED SWITCHING PROGRAM

PLANNED SWITCHING PROGRAM WORKFLOW – EXECUTION STAGE

No switching operations to START without instruction to proceed BY DCP on the day


of the work.

All switching sequence shall be carrying out as described in approved switching document.

The time and date when each switching sequence is carrying out shall be recorded on the
SAEP copy of the Switching Program. This shall be recorded before the next sequence item
is carrying out.

As a preliminary to the START of switching, the SAEP responsible for carrying


out the switching shall identify himself to the DCP involved. Both will record the names of
the other person.

The SAEP carrying out operations on the system shall only carry out operations with
instruction of involved DCP, and NOT another SAEP.

Where more than 1 SAEP is required to carry out switching within the Switching
Program, each SAEP involved in switching shall be in control of a copy of the
Switching Program. In this case the DCP will instruct each SAEP to undertake the
switching they will be required to carry out separately under the management of DCP.

Page | 13
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

PLANNED SWITCHING PROGRAM WORKFLOW – EXECUTION STAGE

DCP SAEP Call center

Confirm and check with Ready to begin


SAEP the approved switching program
switching program
reference matching
DCC reference.

Agree to proceed with Carry out isolation


SAEP. issue switching switching instructions
instruction to SAEP as and record time of each
per sequence on
sequence on switching
approved switching program
program.

Isolation
Isolation

Report sequence
Record complete time completion to DCP and
in switching program time of each completed
sequence.

Confirm to issue safety Verify with DCP


permit authorization card,
issue safety permit

confirm safety permit Cancel safety permit


cancellation

Start restoration
instruct to start switching instruction and
Restoration

restoration switching to record time of each item


SAEP as per sequence
Restoration

as on switching program
on approved switching
program.

Record complete time in Report item complete to


switching program, send DCP and time of each
sms to call center completed sequence,
proceed to process as proceed to process as
below. SMS to customer
below

Page | 14
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Step Description Owner

1 Prepare to SAEP will need to make final preparations to start


start the Switching Program. All HSE Rules and the
switching requirements of approved
program Tanweer ESR must be strictly followed;
SAEP is responsible for the safety of Tanweer SAEP
staff, contactors and the public. SAEP shall
confirm the network NOD to be used is correct and
that open points are in line with the NOD.
2 SAEP and The SAEP and the DCP shall confirm Switching
DCP to Program reference number is correct, and all
agree SAEP involving in switching has a copy of the
SAEP
START the same Switching Program. The SAEP and DCP
Switching shall confirm the updated latest network operating DCP
Program diagram.
3 Sequence DCP will instruct SAEP to perform the sequence
of of switching as described on Switching Program.
Switching DCP and SAEP shall record the time of each
Program sequence. SAEP shall consult DCC before shifting
load from one feeder to another.
4 Follow DCP SAEP follows the instructions of DCP to perform
instructions the switching sequence and record the times of
each sequence. Where further sequence of the
Switching Program is required by the SAEP before
the issue of safety document or another SAEP is
required to carry out switching as part of sequence
, the DCP and SAEP will repeat step 3 above.
Before issuing any safety documents (PTW / SFT / SAEP
LOA), the SAEP shall inform DCP that the DCP
sequence instructed being completed and shall
confirm the times of each sequence. The DCP
shall record on the DCC copy of
the Switching Program the times of each sequence
including isolation, CME and application of safety
locks and caution.
5 Issue safety The SAEP shall identify the details of the safety
documents document and the authorization of the permit
executer. The DCP shall confirms all appropriate
isolation and earthing is in place and the permit
executer has valid authorization. No permit shall SAEP
be issued if the permit executer does not have the DCP
required authorization. The DCP shall agree and
record the time of the issue of the safety document
Page | 15
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

on the DCC copy of the Switching Program, and


the SAEP shall record the time on his copy of the
Switching Program.
6 Cancellation Once work completed, the permit executer shall
of safety inform the SAEP and sign of the safety document SAEP
document no further work required. The SAEP shall confirm
by SAEP all work completed and sing off the safety
document recording the cancelation time on the
document and in the Switching Program.
7 cancellation The SAEP shall report cancellation of the safety
of safety document and the time canceled to the DCP. The SAEP
document DCP shall confirm cancellation and record the time
DCP
by DCP in DCC Switching Program.
8 switching The SAEP and the DCP shall discuss and confirm
program the restoration switching, the DCP will instruct the SAEP
completion restoration sequence and both the DCP and SAEP
DCP
will record the time of each sequence.

Page | 16
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

PLANNED SWITCHING PROGRAM

PLANNED SWITCHING PROGRAM – DOCUMENTATION STAGE

The below workflow describes the way forward to document copies of executed
switching program for the sake of required update and auditing of the completed work.

DCP SAEP

Save switching program document Scan switching program with all


safety document and save in shared
file.

Close safety permit, submit Issue close work order through


complete switching program to oracle.
control analyst.

Page | 17
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Step Description Document Owner


1 DCC DCP shall save a copy of the 1. Switching
Documentation completed DCC Switching Program program
and copies of the NOD's used during document
the work. Daily Outage 2. Daily
sheet and DCC Audit Report to be outage DCP
completed. sheet
3. DCC
audit
report
2 Site SAEP shall scan completed switching 1. Switching
documentation program documents, all safety programs
documents issued and all NOD’s in 2. NOD SAEP
shared folder for audit purpose by the 3. Safety
DCC. SAEP will ensure the NOD on permits
the shared folder is updated.
3 Closing Work SAEP will initiate closing of the work nil SAEP
Order order in Oracle. The DCP will close the DCP
work order and the Control Analyst to CA
be notified.

Page | 18
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Un-PLANNED SWITCHING PROGRAM


Un-PLANNED SWITCHING PROGRAM - PREPARATION STAGE

Tanweer needs to have organized sequence procedures in place in advance of carried


out switching on the HV network. Preparing Switching Program in a timely
manner is mandatory to secure safe operation and comply with Electrical Safety Rule
DURING UNPLANNED SWITCHING PROGRAM. The DCC ASSUMED TO HAVE
access to the SCADA system at Duqm, Musandam and Masirah currently which
provides alarms, indication and the current state of plant at 33 kV and 11 kV
substations. The network without SCADA system, report shall be received through site
SAEP. The DCC must secure updated data/ NOD of the plant and circuits of the 33
kV and 11 kV level. When any plant or circuit is at abnormal condition, this shall be
recording and handling by the DCP on:

1. planned Switching Program


2. DCC Outage Sheet
3. The Handover Sheet
4. The SCADA Diagram

5. The Log

Page | 19
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Un-PLANNED SWITCHING PROGRAM

Un-PLANNED SWITCHING PROGRAM – EXECUTION STAGE

No switching operations to START without instruction to proceed BY DCP on


the day of the work.
All switching sequence shall be carrying out as described in approved switching
document.
The time and date when each switching sequence is carrying out shall be recorded on
the SAEP copy of the Switching Program. This shall be recorded before the next
sequence item is carrying out.
As a preliminary to the START of switching, the SAEP responsible for undertaking the
switching shall identify himself to the DCP involved. Both will record the names of the
other person.
The SAEP undertaking operations on the system shall only carry out operations with
instruction of involved DCP, and NOT another SAEP.
Where more than 1 SAEP is required to carry out switching within the Switching
Program, each SAEP involved in switching shall be in control of a copy of the
Switching Program. In this case the DCP will instruct each SAEP to undertake the
switching they will be required to carry out separately under the management of DCP

Page | 20
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Un-PLANNED SWITCHING PROGRAM WORKFLOW – EXECUTION STAGE


Call center /
DCP SAEP SCADA zone / bulk
customer
ALARM
start
Circuit breaker trip or
Log event and network damage Alarm / Notification
record time ( or from call
outage sheet ) circuit center /
breaker emergency
Inform SAEP to trip incharge
investigate, send
SMS to SMS to
management and Acknowledge customer if
call center investigate and report estimation
finding to DCP time > 3
Log finding / time hours
on outage sheet

Discuss / agree Discuss / agree initial


initial action action

Log instruction / Record instruction on


times on outage field outage sheet,
sheet repeat instructions to
DCP

Isolation
Isolation

Carryout isolation, issue


safety permit and record
repairing actions on
Report complete sequence
action / time on
outage sheet Record time for each
action on field outage
sheet

Report action to DCP

Discuss / agree Discuss / agree


Restoration
Restoration

restoration step restoration steps

Log instruction /
times on outage
sheet

Page | 21
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Record instruction on
field outage sheet,
repeat instructions to
DCP

Carryout restoration
Record complete sequence
action / time on
outage sheet, Record time for each
confirm supply action on field outage
restored, sms to sheet
Tanweer Sms to
management and Report action to DCP , customers
call center, confirm supply restored,
proceed to process proceed to process
below below

Page | 22
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Step Description Owner

1 Incident Incident reporting, either an alarm on the SCADA


system or reported from SAEP, Call Centre, Zone
emergency engineer or bulk customer, will require
the DCP to be notified. The DCP will log the event
and determine appropriate action. When HV circuit SAEP
breaker has tripped at a Primary Substation, the
DCP should identify the substation name the DCP
feeder name and any indications on the SCADA Call
system. These should be logged on the DCC Center
Outage Sheet and Control Log with the time of the
circuit breaker operation. The DCP will send SMS
to TANWEER management and the call center to
inform of the outage and lost load.
2 Incident DCP shall contact the SAEP to discuss the
Investigation incident and instruct to investigate the incident. All
HSE Rules and the requirements of approved
TANWEER ESR must be strictly followed; SAEP is SAEP
responsible for the safety of Tanweer staff, DCP
contactors and the public. SAEP shall confirm the
network NOD to be used is updated.
3 Incident Following investigation, the DCP will receive
Investigation information from SAEP which will confirm the
situation, the normal or abnormal state of plant or
circuit. The DCP will log all relevant information SAEP
and times. The DCP and SAEP will discuss DCP
options where action needs to be taken to restore
supplies or protect people, plant or circuits from
danger. The SAEP and the DCP shall agree un
planned switching program is required.
4 Preparing After deciding the appropriate action, the
switching DCP will write switching instructions in the DCC
program Outage Sheet, and switching sheet. The DCP will
SAEP
give the instructions to the SAEP with switching
sequence. The SAEP will write the sequence in his DCP
Field Outage Sheet and repeat them back to the
DCP. Both the DCP and the SAEP will record the
agreed switching sequence.

Page | 23
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

5 Carrying out SAEP follows the instructions of DCP to perform


switching the switching sequence and record the times of
sequence each sequence.
Before issuing any safety documents (PTW / SFT /
LOA), the SAEP shall inform DCP that the SAEP
sequence instructed being completed and shall
DCP
confirm the times of each sequence. The DCP
shall record on the DCC copy of
the Switching Program the times of each
sequence including isolation, CME and application
of safety locks and caution.
6 Carrying out The SAEP shall identify the details of the safety
switching document and the authorization of the permit
SAEP
sequence executer. The DCP shall confirms all appropriate
isolation and earthing is in place and the permit
executer has valid authorization. No permit shall
be issued if the permit executer does not have the
required authorization. The DCP shall agree and
record the time of the issue of the safety document
on the DCC copy of the Switching Program, and
the SAEP shall record the time on his copy of the
Switching Program.
7 cancellation of Once work completed, the permit executer shall
safety inform the SAEP and sign of the safety document
SAEP
document by no further work required. The SAEP shall confirm
DCP all work completed and sing off the safety DCP
document recording the cancelation time on the
document and in the Switching
8 cancellation of The SAEP shall report cancellation of the safety
safety document and the time canceled to the DCP. The
SAEP
document by DCP shall confirm cancellation and record the time
DCP in DCC Switching Program DCP
9 Ending The SAEP and the DCP shall discuss and confirm SAEP
switching the restoration switching, the DCP will instruct the
DCP
program restoration sequence and both the DCP and SAEP
will record the time of each sequence.
SAEP will create work order on oracle next day.

Page | 24
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Un-PLANNED SWITCHING PROGRAM

Un-PLANNED SWITCHING PROGRAM – DOCUMENTATION STAGE

The below workflow describes the way forward to document copies of executed switching
program for the sake of required update and auditing of the completed work

DCP SAEP SCADA CALL CENTER /


ZONE / BULK
CUSTOMER
Send SMS to
Tanweer
management / Scan complete Inform supply
call center outage sheet , restored
safety
document used
Save copy of during
DCC outage operation and
sheet and NOD save in share
used in share folder between
file, and DCC , operation
complete daily zones , QHSE
outage report

Update NOD

Page | 25
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Step Description Document Owner


1 DCC DCP send SMS to Tanweer 4. Switching
Documentation Management and call center to inform program
supply restored. document
DCP shall save a copy of the 5. Daily
completed DCC Switching Program outage DCP
and copies of the NOD's used during sheet
the work. Daily Outage 6. DCC
sheet and DCC Audit Report to be audit
completed. report
2 Site SAEP shall scan completed switching 4. Switching
documentation program documents, all safety programs
documents issued and all NOD’s in 5. NOD SAEP
shared folder for audit purpose by the 6. Safety
DCC. SAEP will ensure the NOD on permits
the shared folder is updated.
3 Closing Work SAEP will initiate closing of the work nil SAEP
Order order in Oracle. The DCP will close the DCP
work order and the Control Analyst to CA
be notified.

Page | 26
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

EMERGENCY SWITCHING PROGRAM


EMERGENCY SWITCHING PROGRAM – INCIDENT REPORT STAGE

Tanweer needs to have organized sequence procedures in place in advance of carried out
switching on the HV network. Preparing Switching Program in a timely
manner is mandatory to secure safe operation and comply with Electrical Safety Rule
DURING EMERGENCY SWITCHING PROGRAM. The DCC ASSUMED TO HAVE access
to the SCADA system at Duqm, Musandam and Masirah currently which
provides alarms, indication and the current state of plant at 33 kV and 11 kV substations.
The network without SCADA system, incident report shall be received through site SAEP.
The DCC has updated data of the plant and circuits of the 33 kV and 11 kV level.
Where any item of plant or circuit is at an abnormal condition, this shall be recording and
handling by the DCP on:

6. planned Switching Program


7. DCC Outage Sheet
8. The Handover Sheet
9. The SCADA Diagram

10. The Log

Page | 27
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

EMERGENCY SWITCHING PROGRAM

EMERGENCY SWITCHING PROGRAM – EXECUTION STAGE

No switching operations to START without instruction to proceed BY DCP on the day


of the work.

All switching sequence shall be carrying out as described in approved switching document.

The time and date when each switching sequence is carrying out shall be recorded on the
SAEP copy of the Switching Program. This shall be recorded before the next sequence item
is carrying out.

As a preliminary to the START of switching, the SAEP responsible for carrying


out the switching shall identify himself to the DCP involved. Both will record the names of
the other person.

The SAEP carrying out operations on the system shall only carry out operations with
instruction of involved DCP, and NOT another SAEP.

Where more than 1 SAEP is required to carry out switching within the Switching
Program, each SAEP involved in switching shall be in control of a copy of the
Switching Program. In this case the DCP will instruct each SAEP to undertake the
switching they will be required to carry out separately under the management of DCP.

Page | 28
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

EMERGENCY SWITCHING PROGRAM WORKFLOW – EXECUTION STAGE

DCP SAEP Call center

SAEP identify
emergency case
required urgent action

Isolation
Isolation

Identify / Confirm
isolation point /
breaker

Confirm circuit breaker Yes


and open Is it possible to open
the circuit breaker by
DCP ??
No

Open circuit breaker


remotely

Record complete Confirm SWITCHING


actions / times on complete and inform
outage sheet DCP, record action on
outage sheet

Discuss and agree Discuss and agree


restoration step,
Restoration
Restoration

restoration step,
proceed to process as proceed to process as
below. below.

Page | 29
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Step Description Owner


Emergency incident An emergency incident is when action is SAEP
required to isolate plant and circuits to
avoid immediate danger. When SAEP
identifying such emergency, should identify
the isolation point circuit breaker to isolate
the danger / or fault. DCP and SAEP shall
confirm If the circuit breaker could control
through SCADA or not !!
Isolation , open circuit Yes No DCP/SAEP
breaker
If the answer is yes, If the answer is no,
DCP open the circuit SAEP shall open
breaker. The DCP the circuit breaker
should identify the remotely and prove
appropriate circuit dead. SAEP should
breaker on the not put
SCADA system and himself in danger in
open the circuit taking this action.
breaker, SAEP shall SAEP should
confirm circuit record and report to
breaker opened and the DCP circuit
prove dead. breaker opened.
Activity recording Following operation of the circuit breaker. DCP/SAEP
The action and time should be recorded on
the DCC Outage Sheet.
Next Steps The DCP and SAEP should discuss the DCP/SAEP
actions required after isolating the fault.
This will depend on the circumstances and
may involve raising to a manager or may
require attendance of emergency services
if there are persons
injured. There may also need to be further
unplanned switching if supplies are
affected. If this is the case, then it should
be carried out under the unplanned
switching procedure.

Page | 30
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

EMERGENCY SWITCHING PROGRAM

EMERGENCY SWITCHING PROGRAM – DOCUMENTATION STAGE

The below workflow describes the way forward to document copies of executed switching
program for the sake of required update and auditing of the completed work

DCP SAEP Call center

Send SMS to Tanweer Record, APPLY outage


management and call management
center procedure
Scan complete outage
sheet , PTW used
during operation and
Save copy of DCC save in share folder
outage sheet and NOD between DCC ,
used in share file, and operation zones ,
complete daily outage QHSE
report

Update NOD

Page | 31
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Step Description Document Owner


1 DCC DCP send SMS to Tanweer 7. Switching
Documentation Management and call center to inform program
supply restored. document
DCP shall save a copy of the 8. Daily
completed DCC Switching Program outage DCP
and copies of the NOD's used during sheet
the work. Daily Outage 9. DCC
sheet and DCC Audit Report to be audit
completed. report
2 Site SAEP shall scan completed switching 7. Switching
documentation program documents, all safety programs
documents issued and all NOD’s in 8. NOD SAEP
shared folder for audit purpose by the 9. Safety
DCC. SAEP will ensure the NOD on permits
the shared folder is updated.
3 Closing Work SAEP will initiate closing of the work nil SAEP
Order order in Oracle. The DCP will close the DCP
work order and the Control Analyst to CA
be notified.

Page | 32
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

11 Kv NOD update
11 Kv NOD update – DOCUMENTATION STAGE

Any changes to the 11kV network, will have been carried out under one of the

following procedures;

* Planned Switching Program TANWEER/SOP/DCC/01


* Un Planned Switching TANWEER/SOP/DCC/01
* Emergency Switching TANWEER/SOP/DCC/01

At the end of each switching program, any change of the existing 11 Kv Network will be
reflected immediately to the existing NOD and update the changes. The Control Analyst
scope to ensure 11 Kv NOD update daily and to identify where the update on the 11 kV
NOD required. The scope of control analyst is to update head of SCADA and head of GIS
the change on 11 Kv NOD to be reflected on SCADA & GIS. The flowchart below describes
the process and roles.

Page | 33
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Control analyst SAEP head of control Head of GIS


and SCADA

Update NOD Update NOD in


after each share file.
switching
program and
when required.

Audit and verify


NOD updated in
share folder

If there is need
to update Update SCADA
SCADA inform system
head of control
and SCADA

IF THERE IS
NEED TO Update GIS
UPDATE GIS system
INFORM HEAD
OF GIS

Audit and verify


GIS and SCADA
being updated

Create weekly
report for head
of control and
SCADA

Page | 34
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Step Description Owner


1 Review / audit All work on the 11kV network will require CA
PTW and categorized as planned,
unplanned or emergency switching. By
the end of each switching program cycle
the document along with
Field / DCC outage sheet document must
save in the shared drive. The CA reviews
the daily switching documents in the
shared folder to determine if there
change on 11 Kv network. The scope of
control analyst is to update head of
SCADA and head of GIS the change on
33 Kv NOD to be reflected on SCADA &
GIS.
2 Update 11kV NOD SAEP will update the 11 kV NOD in the CA/SAEP
shared folder. CA will ensure the update
is completed and confirm the correct of
update.
3 SCADA and GIS CA will inform HSCADA and HGIS to CA/HSCADA/HGIS
Update 11Kv update the system accordingly. HSCADA
and HGIS will update the SCADA system
and the GIS diagrams as
required. Both HSCADA & HGIS MUST
confirm the update has been
completed correctly. CA shall escalate
the non-update of NOD to manager
withing 2 weeks.
4 CA Reporting CA generate weekly audit report for the DCP/SAEP/ZONE
HDCC. The HDCC informs ZONE LEAD / HEAD
LEAD/operation head for each update. OPERATION

Page | 35
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

33 Kv NOD update
33 Kv NOD update – DOCUMENTATION UPDATESTAGE

Any changes to the 33 Kv network, will have been carried out under one of the

following procedures;

* Planned Switching Program TANWEER/SOP/DCC/01


* Un Planned Switching TANWEER/SOP/DCC/01
* Emergency Switching TANWEER/SOP/DCC/01

At the end of each switching program, any change of the existing 33 Kv Network will be
reflected immediately to the existing NOD and update the changes. The Control Analyst
scope to ensure 33 Kv NOD update daily and to identify where the update on the 33 kV
NOD required. The scope of control analyst is to update head of SCADA and head of GIS
the change on 33 Kv NOD to be reflected on SCADA & GIS. The flowchart below describes
the process and roles.

Page | 36
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Control analyst SAEP head of control Head of GIS


and SCADA

Update NOD Update NOD in


after each share file.
switching
program and
when required.

Audit and verify


NOD updated in
share folder

If there is need
to update Update SCADA
SCADA inform system
head of control
and SCADA

IF THERE IS
NEED TO Update GIS
UPDATE GIS system
INFORM HEAD
OF GIS

Audit and verify


GIS and SCADA
being updated

Create weekly
report for head
of control and
SCADA

Page | 37
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Step Description Owner


1 Review / audit All work on the 33kV network will require CA
PTW and categorized as planned,
unplanned or emergency switching. By
the end of each switching program cycle
the document along with
Field / DCC outage sheet document must
save in the shared drive. The CA reviews
the daily switching documents in the
shared folder to determine if there
change on 33 Kv network. The scope of
control analyst is to update head of
SCADA and head of GIS the change on
33 Kv NOD to be reflected on SCADA &
GIS.
2 Update 33kV NOD SAEP will update the 33 kV NOD in the CA/SAEP
shared folder. CA will ensure the update
is completed and confirm the correct of
update.
3 SCADA and GIS CA will inform HSCADA and HGIS to CA/HSCADA/HGIS
Update 33Kv update the system accordingly. HSCADA
and HGIS will update the SCADA system
and the GIS diagrams as
required. Both HSCADA & HGIS MUST
confirm the update has been
completed correctly. CA shall escalate
the non-update of NOD to manager
withing 2 weeks.
4 CA Reporting CA generate weekly audit report for the DCP/SAEP/ZONE
HDCC. The HDCC informs ZONE LEAD / HEAD
LEAD/operation head for each update. OPERATION

Page | 38
Standard Operating Procedure planned / Doc Number TANWEER/SOP/DCC/01
Unplanned / Emergency Switching/ Effective Date DATE OF SIGNATURE
update NOD Version Number V0.1

Page | 39

You might also like