Loop Automation - Voltimum · 2015-01-28 · Loop Automation is a suite of FDIR self-healing...

28
Energy Business - MVS - Automated Overhead Revision: R7 Date: 27/06/2013 Marcelo Carvalho Automated Overhead Product Manager Loop Automation

Transcript of Loop Automation - Voltimum · 2015-01-28 · Loop Automation is a suite of FDIR self-healing...

Energy Business - MVS - Automated Overhead

Revision: R7

Date: 27/06/2013

Marcelo Carvalho

Automated Overhead Product Manager

Loop Automation

Introduction

Electricity is becoming increasingly important in our everyday lives. This demand puts immense pressure on

electricity providers to improve the reliability of supply to their customers by reducing the number of supply

interruptions and minimizing their duration.

Fault Detection, Isolation and Service Restoration (FDIR) self-healing algorithms embedded in pole-

mounted reclosers and sectionaliser controllers are highly effective distributed (or decentralized) automation

systems that identify faults on an overhead line, isolate them and restore supply to unfaulted sections of the

grid without any intervention from an operator, delivering the required reliability to utilities.

Loop Automation is a suite of FDIR self-healing algorithms for overhead distribution networks. It was

developed by Schneider Electric for its offer of pole-mounted automatic circuit reclosers (ACR’s) and

sectionalisers (SEC’s) equipped with a controller from the ADVC Controller Range.

ADVC controllers running Loop Automation operate the grid without human operator intervention using

embedded voltage detection, timers, protection flags and peer-to-peer communications.

Loop Automation

N-Series

ACR

U-Series

ACR W-Series

ACR

RL-Series

LBS/SEC

ADVC Controller

Loop Automation Scheme Tool

WSOS5

Configuration and Monitoring

Software

• Improved network availability and reliability;

• Decreased number (measured by the System Average Interruption Frequency Index - SAIFI) and

duration (System Average Interruption Duration Index - SAIDI) of outages by quickly detecting and

isolating a fault, then restoring power to unfaulted sections before the outage is added to KPI records;

• Reduced size of zones affected by faults (thus maximising energy delivery to customers);

• Power is restored quickly without any operator intervention;

• Switchgear controllers automatically reconfigure their protection settings upon fault isolation and

power restoration;

Loop Automation - Benefits

• Existing recloser or sectionaliser installations may be upgrades to run Loop Automation schemes, simply

requiring a controller firmware upgrade and configuration;

• Classic Loop Automation enables grid automation without using communications;

• Intelligent Loop Automation takes advantage of peer-to-peer communications for added safety and

improved operation. It ensure that the fault is not re-energized after its disconnection (a highly

undesirable event).

• Easy to configure and supervise using WSOS5 Loop Automation Scheme tool;

• Easy to commission, deploy and maintain;

• Easy to integrate with SCADA/DMS using industry-standard protocols;

• R&D support readily available;

• World-class product and application support by a major global company - Schneider Electric;

• Its original version, Classic Loop Automation, was consolidated and perfected over 15 years of

application, proving itself as an effective overhead distribution automation solution. It was largely deployed

globally, with multiple applications in the USA, Australia, Brazil and Hong Kong.

Loop Automation - Advantages

Loop Automation Description

Sources

Feeder

Midpoint

Feeder

Tie

Closed Tripped

Switchgear State

Loop Automation - Device Types & Topology

Reclosers and sectionalisers in an Intelligent Loop Automation self-healing scheme perform one of three

different roles:

• Feeder : Device closest to the a power supply;

• Tie: The open point device where two overhead lines meet (also known as the normally open point);

• Midpoint: Device positioned between a Feeder and a Tie device.

8

F

M

T

Feeder

Midpoint

Tie

ADVC

Controller

Overhead

Switchgear

T

F

M M

M

F

CB CB

Co

ntr

ol

Local Control Unit

SCADA Comms

DNP3

IEC60870-5-101/104

Modbus

Remote

Engineering/Operation Control Center

Op

era

tio

n

SCADA/DMS

Peer-to-Peer Comms

TCP/IP Radio

Ethernet

Fibre Optics

M

Local

Engineering/Operation

CB Substation Circuit Breaker

N-Series

ACR

U-Series

ACR

W-Series

ACR

RL-Series

LBS

Overhead Self-Healing Loop Automation System Architecture

MV Transformer

Substation Substation

Classic Loop Automation Rules

The basic rules* of Loop Automation (the Classic Loop Automation Rules) are:

• (1) Feeder devices trip when their source supply is lost;

• (2) Midpoint devices activate their Alternative (or Reverse) Protection Group when they lose

source supply and, if the midpoint is an automatic recloser, it will also change to single shot mode

(auto-reclose off). After supply is restored from another source, midpoints will have auto-reclose

turned back on automatically;

• (3) Tie devices close when they detect that supply from its load or source side is lost.

These simple rules disconnect, isolate and reconfigure the grid for all possible faults.

* See Appendix X in the Loop Automation User Manual for the complete set of rules.

Intelligent Loop Automation Rules

Intelligent Loop Automation adds another level of intelligence to Loop Automation. It complements the

Classic Loop Automation basic operation rules with the following (the Intelligent Loop Automation Rules):

• (4) A device (either a Feeder or a Midpoint) that goes to lockout (the locked out device) sends a trip

request to its downstream device;

• (5) A Feeder also sends a trip request to its downstream device if it trips to lockout after loosing its

source supply (Classic Loop Automation Rule 1);

• (6) If Tie control mode is Message, the locked out device sends a close request to the Tie in the

scheme upon confirmation of a successful operation of its downstream device;

• (6a) If this confirmation doesn’t come, the locked out device will not send a close request to the

Tie;

• (7) If Tie control mode is Timer, a Tie will operate as per its basic Classic Loop Automation Rule 3 -

regardless of receiving a close request or not. This mode maintains the availability of the

scheme and enables an automatic attempt to restore supply regardless of the availability of the peer-

to-peer communications.

• (8) If Tie control mode is Message, a Tie will operate only if it receives a Loop Automation close

request.

* See Intelligent Loop Automation User Manual for the complete set of rules.

WSOS5 Loop Automation Scheme Tool

Loop Automation Scheme Tool

The Loop Automation Scheme Tool enables easy creation, configuration, validation and monitoring of

individual Loop Automation schemes.

Loop Automation Case Studies

CASE 1 Permanent Fault Between Substation CB & Feeder Device

Substation CB’s

(or other switchgear)

10km 15km

10km

7.5km

Midpoint 4

Midpoint 3

2D

Feeder 2

2B

10km

2A

1A

Midpoint 2

7.5km

1D

1B

7.5km

5km

2C The substation CB picks up, trips

from protection & goes to lockout.

The Feeder device trips and goes to

lockout after its timer expires.

Midpoint 1

Loop Automation Activation Delay

timers start due to a loss of supply.

Midpoint devices change protection group in anticipation

to the power flow direction change and go to Single Shot

(no auto-reclose) mode after their timers expire.

The Tie device also changes protection group depending

on which side the power was lost (source or load), goes to

Single Shot (no auto-reclose) mode and closes

automatically after its timer expires.

Feeder 1

Tie

• Fault isolated

• Power restored to unfaulted sections in less than 1 minute

• No operator intervention

Closed Tripped

Switchgear

Live Dead

Line

1C B+SS B

B B+SS

Permanent Fault Between Substation CB & Feeder Device Intelligent Loop Automation with Timer-Controlled Tie

10km 15km

10km

7.5km

Midpoint 4

Midpoint 3

2D

Feeder 2

2B

10km

2A

1A

Midpoint 1

Midpoint 2

7.5km

1D

1B

7.5km

Feeder 1

1C

5km

2C Modbus Close Request

The substation CB picks up, trips

from protection & goes to lockout.

The Feeder device trips and goes to lockout after its

timer expires. It will then send a close request to the

tie device using Modbus P2P communications.

Midpoint devices change protection group in anticipation

to the power flow direction change and go to Single Shot

(no auto-reclose) mode after their timers expire.

The Tie device also changes protection group depending

on which side the power was lost (source or load), goes to

Single Shot (no auto-reclose) mode and closes upon

receiving a close request and having its timer expired.

Closed Tripped

Switchgear

Live Dead

Line

Tie

Substation CB’s

(or other switchgear)

• Fault isolated

• Power restored to unfaulted sections in less than 1 minute

• No operator intervention

B+SS B

B+SS B

Permanent Fault Between Substation CB & Feeder Device Classic & Intelligent Loop Automation with Message-Controlled Tie

Loop Automation Activation Delay

timers start due to a loss of supply.

CASE 2 Permanent Fault Between Feeder & Midpoint Devices

10km 15km

10km

7.5km

Midpoint 4

Midpoint 3

2D

Feeder 2

2B

10km

2A

1A

Tie

Midpoint 2

7.5km

1D

1B

7.5km 2C

1C

5km

Loop Automation Activation Delay

timers start due to a loss of supply.

The downstream Midpoint device changes protection group in

anticipation to the power flow direction change and goes to Single Shot

(no auto-reclose) mode after its timer expires or upon receiving a Loop

Automation trip request, which will also cause the device to open. The Tie device also changes protection group depending

on which side the power was lost (source or load), goes to

Single Shot (no auto-reclose) mode and closes after its

timer expires.

The Feeder device picks up, executes a trip/reclose

sequence & goes to lockout. It will then send a trip

request to its downstream device using Modbus P2P

communications.

Closed Tripped

Switchgear

Live Dead

Line

Modbus Trip Request

Feeder 1

Other Midpoint devices also change protection group and go

to Single Shot (no auto-reclose) mode after their timers expire.

Midpoint 1 B+SS B

B B+SS

Substation CB’s

(or other switchgear)

• Fault isolated

• Power restored to unfaulted sections in less than 1 minute

• No operator intervention

Permanent Fault Between Feeder & Midpoint Devices Intelligent Loop Automation with Timer-Controlled Tie

10km 15km

10km

7.5km

Midpoint 4

Midpoint 3

2D

Feeder 2

2B

10km

2A

1A

Midpoint 2

7.5km

1D

1B

7.5km

Feeder 1

2C

1C

5km

B

The downstream Midpoint device changes protection group in

anticipation to the power flow direction change and goes to Single

Shot (no auto-reclose) mode after its timer expires or upon receiving a

Loop Automation trip request, which will also cause the device to trip.

The Feeder device Picks up, executes a trip/reclose

sequence & goes to lockout. It will then send a trip

request to its downstream device and a close request to

the Tie device using Modbus P2P communications.

Closed Tripped

Switchgear

Live Dead

Line

Modbus Trip Request

Other Midpoint devices also change protection group

and go to Single Shot (no auto-reclose) mode after their

timers expire.

Tie

Modbus Close Request

Midpoint 1

B+SS

B B+SS

Substation CB’s

(or other switchgear)

• Fault isolated

• Power restored to unfaulted sections in less than 1 minute

• No operator intervention

Permanent Fault Between Feeder & Midpoint Devices Intelligent Loop Automation with Message-Controlled Tie

The Tie device also changes protection group depending

on which side the power was lost (source or load), goes to

Single Shot (no auto-reclose) mode and closes upon

receiving a close request and having its timer expired.

Loop Automation Activation Delay

timers start due to a loss of supply.

CASE 3 Permanent Fault Between Midpoint Devices

Substation CB’s

10km 15km

10km

7.5km

Midpoint 4

Midpoint 3

2D

Feeder 2

2B

10km

2A

1A

Midpoint 1

Midpoint 2

7.5km

1D

1B

7.5km

Feeder 1

2C

1C

Loop Automation Activation Delay

timers start due to a loss of supply.

The downstream Midpoint device changes protection group in

anticipation to the power flow direction change and goes to Single Shot

(no auto-reclose) mode after its timer expires or upon receiving a Loop

Automation trip request, which will also cause the device to trip.

The Tie device also changes protection group depending

on which side the power was lost (source or load), goes to

Single Shot (no auto-reclose) mode and closes when its

timer expires.

The Midpoint device picks up, executes a trip/reclose

sequence & goes to lockout. It will then send a trip

request to its downstream device using Modbus P2P

communications.

• Fault isolated

• Power restored to unfaulted sections in less than 1 minute

• No operator intervention

Closed Tripped

Switchgear

Live Dead

Line

Modbus Trip Request

Tie

5km

B B+SS

Permanent Fault Between Midpoint Devices Intelligent Loop Automation with Timer-Controlled Tie

Substation CB’s

10km 15km

10km

7.5km

Midpoint 4

Midpoint 3

2D

Feeder 2

2B

10km

2A

1A

Tie

7.5km

1D

1B

7.5km

Feeder 1

2C

1C

5km

The Tie device also changes protection group depending

on which side the power was lost (source or load), goes to

Single Shot (no auto-reclose) mode and closes upon

receiving a close request and having its timer expired.

• Fault isolated

• Power restored to unfaulted sections in less than 1 minute

• No operator intervention

Closed Tripped

Switchgear

Live Dead

Line

Modbus Close Request

Modbus Trip Request

Midpoint 2

Midpoint 1 B B+SS

Loop Automation Activation Delay

timers start due to a loss of supply.

Permanent Fault Between Midpoint Devices Intelligent Loop Automation with Message-Controlled Tie

The downstream Midpoint device changes protection group in

anticipation to the power flow direction change and goes to Single Shot

(no auto-reclose) mode after its timer expires or upon receiving a Loop

Automation trip request, which will also cause the device to open.

The Midpoint device picks up, executes a trip/reclose sequence

& goes to lockout. It will then send a trip request to its

downstream device and a close request to the Tie device using

Modbus P2P communications.

CASE 4 Permanent Fault Between Midpoint and Tie Devices

Substation CB’s

10km 15km

10km

7.5km

Midpoint 4

Midpoint 3

2D

Feeder 2

2B

10km

2A

1A

Midpoint 1

Midpoint 2

7.5km

1B

7.5km

Feeder 1

2C

1C

5km

1D

Loop Automation Activation Delay

timer starts due to a loss of supply.

The Tie device, having received a

close inhibit request, will remain open

and won’t close on the fault.

The Midpoint device Picks up, executes a

trip/reclose sequence & goes to lockout. It will

then send a close inhibit request to the Tie device

using Modbus P2P communications.

• Fault isolated

• Power restored to unfaulted sections in less than 1 minute

• No operator intervention

Closed Tripped

Switchgear

Live Dead

Line

Tie

Permanent Fault Between Midpoint and Tie Devices Intelligent Loop Automation with Timer-Controlled & Message-Controlled Tie

Modbus Close Inhibit Request

CASE 5 Intelligent Loop Automation with Overload Control

Load<Overhead

Substation CB’s

10km 15km

10km

7.5km

Midpoint 4

Midpoint 3

2D

Feeder 2

2B

10km

2A

1A

Midpoint 2

7.5km

1D

1B

7.5km

Feeder 1

2C

1C

5km

B

The downstream device changes protection group in

anticipation of the change in the direction of the power flow,

goes to Single Shot (no auto-reclose) mode and trips. It

then sends its pre-fault load measurement to the tie.

The Feeder device picks up, executes a trip/reclose

sequence & goes to lockout. It will then send a trip

request to its downstream device using Modbus P2P

communications.

• Fault isolated

• Power restored to unfaulted sections in less than 1 minute

• No operator intervention

Closed Tripped

Switchgear

Live Dead

Line

Modbus Trip Request

Other Midpoint devices change protection group and go

to Single Shot (no auto-reclose) mode.

Tie

Modbus Close Request

Midpoint 1

B+SS

B B+SS

Load

The Tie device requests the overhead of the alternate feeder and

compares it to the reported load. If the overhead is larger than

the load, the Tie changes protection group depending on which

side the power was lost (source or load), goes to Single Shot (no

auto-reclose) mode and closes.

Loop Automation Activation Delay

timers start due to a loss of supply.

Permanent Fault Between Feeder & Midpoint Devices Intelligent Loop Automation with Overload Control (Case Load<Overhead)

Overhead Request

Overhead

CASE 6 Intelligent Loop Automation with Overload Control

Load>Overhead

Substation CB’s

10km 15km

10km

7.5km

Midpoint 4

Midpoint 3

2D

Feeder 2

2B

10km

2A

1A

Midpoint 2

7.5km

1D

1B

7.5km

Feeder 1

2C

1C

5km

B

The downstream device changes protection group in

anticipation of the change in the direction of the power flow,

goes to Single Shot (no auto-reclose) mode and trips. It

then sends its pre-trip load measurement to the tie.

Picks up, executes trip/reclose sequence & goes to

lockout. It will then send a trip request to its

downstream device using Modbus P2P

communications.

• Fault isolated

• Power restored to unfaulted sections in less than 1 minute

• No operator intervention

Closed Tripped

Switchgear

Live Dead

Line

Modbus Trip Request

Tie

Midpoint 1

B+SS

The Tie device requests the overhead of the alternate feeder and

compares it to the reported load. If the load is larger than the

overhead, the close operation is inhibited and the Tie reports an

overload to the device that sent the latest load report.

Loop Automation Activation Delay

timers start due to a loss of supply.

Overload Report

Modbus Trip Request

Load

Permanent Fault Between Feeder & Midpoint Devices Intelligent Loop Automation with Overload Control (Case Load>Overhead)

Other midpoint devices change protection group and go

to Single Shot (no auto-reclose) mode.

Overhead

Overhead Request

Load

Modbus Close Request

B+SS B

After receiving an overload report from the Tie, the Midpoint device

sends a trip request to its downstream device in order to reduce

the load that can be connected to the alternate feeder.

After receiving a trip request, the Midpoint device trips and

reports its load to the tie.

The Tie once again compares the load to the alternate

feeder overhead. If the load is now below the overhead,

the Tie closes.