Professional Documents
Culture Documents
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
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
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
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
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.
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
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
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.
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
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
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.
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
Isolation
Isolation
Report sequence
Record complete time completion to DCP and
in switching program time of each completed
sequence.
Start restoration
instruct to start switching instruction and
Restoration
as on switching program
on approved switching
program.
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
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
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
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
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
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
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
Isolation
Isolation
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
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
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
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
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
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
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:
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
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.
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
SAEP identify
emergency case
required urgent action
Isolation
Isolation
Identify / Confirm
isolation point /
breaker
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
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
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
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
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;
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
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
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
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;
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
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
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
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