Professional Documents
Culture Documents
09 - Chapter 4 - 3 PDF
09 - Chapter 4 - 3 PDF
CHAPTER 4
DISTRIBUTION SYSTEM RELIABILITY
EVALUATION SERVICES
4.1
INTRODUCTION
Reliability assessment is the most important factor in designing and
In the
106
107
4.2.1
SAIFI
(4.1)
108
SAIFI
Ni
(4.2)
NT
SAIDI
(4.3)
the time taken to reach the outage spot is comparatively larger than the actual
time of repair. In such cases, SAIDI can be reduced by using optimal crew
dispatch techniques like having a decentralized scheme to crew movement
wherein crew are available at multiple locations throughout the system and
the ones nearest the fault fix the problem. Use of automation is another
109
SAIDI
ri N i
NT
(4.4)
CAIDI
(4.5)
110
CAIDI
ri N i
Ni
SAIDI
SAIFI
(4.6)
If service is
CTAIDI
(4.7)
111
seen for the reporting period. The CAIDI uses total number of customer
interruptions in its denominator while the CTAIDI has total number of
customers interrupted.
Equation (4.8).
CTAIDI
ri N i
(4.8)
CN
CAIFI
Ni
CN
(4.9)
112
ASAI
N T 8760
ri N i
N T 8760
(4.10)
Average System Interruption Frequency Index
Unlike SAIFI, ASIFI is an index that uses the load interrupted
rather than the number of customers interrupted. Thus, it is a measure of the
expected number of times load is interrupted during the specified interval of
time. Thus ASIFI for a system is be computed as given in Equation (4.11).
ASIFI
Li
LT
(4.11)
where, Li is the load interrupted due to each outage while LT is the total load
connected to the system under consideration. ASIFI becomes equal to SAIFI
when the load distributed to each customer is equal.
Average System Interruption Duration Index
Similar to ASIFI, ASIDI is load based and computes the average
duration for which load is interrupted when a sustained outage occurs. Thus
ASIDI is computed as given in Equation (4.12).
ASIDI
ri Li
LT
(4.12)
113
and energy oriented indices is the average load at each load point busbar. The
average load La is given in Equations (4.13) and (4.14).
La = Lp f
where
(4.13)
= load factor
La
Ed
t
(4.14)
where,
L a(i) U i
(4.15)
La(i) and Ui respectively are the average connected load and the
114
AENS
L a(i) U i
Ni
(4.16)
where, La(i) and Ui respectively are the average connected load and the
average annual outage time at load point i and Ni is the number of customers
at load point i.
The system wide indices are used to describe the average
performance of the system. For customers requiring high levels of reliability,
using the system wide indices to generalize the quality of service may not be
appropriate. In such cases the use of customer level indices are used to
compute the reliability of the service. Generally, three indices used for the
same are:
Customer interruption frequency which is the frequency of
interruptions seen by the customer during the year
Customer outage duration which is the average time the
customer spends in the interrupted state
Customer service availability is the fraction of the year the
customer has power supply.
Apart from the indices defined so far certain utilities also define
metrics for prioritizing customers based on importance. These indices can be
used not only to assess the past performance of a distribution system but also
to predict the future system performance.
115
4.3
utilities often use large databases where outage histories are maintained often
termed as Outage Management Systems (OMS). These databases include
details of the location, date / time of the failure event, the component involved
and the number of customers interrupted due to each outage. Also recorded
are the entities like the time taken to restore service to the affected customers,
116
the time to repair / replace the failed component and more importantly the
cause of the interruption. Events where service was restored in stages due to
switching actions or reconfiguration of the system are also recorded. Put
together, the outage database provides information on each and every event
that happens on a distribution system. The history of outages in power system
is needed for calculating the distribution system reliability indices.
The
Substation
BRK
L1
M1
C1
F1
900 Customers
1800 KVA
S1 (NC)
M2
L2
L3
C2
F2
550 Customers
1100 KVA
S2 (NC)
NC - Normally Closed
BRK - Breaker
M3
L4
C3
L5
C4
F3
450 Customers
825 KVA
125 Customers
300 KVA
117
Failure Rate ( )
Frequency/yr
0.10
0.25
0.30
0.20
0.40
0.10
0.10
0.00
MTTR
(hours)
4
4
4
3
3
1
2
0
FOR
hrs/yr
0.40
0.12
0.15
0.60
0.00
0.05
0.05
0.00
118
119
120
JAXBContext context =
JAXBContext.newInstance(DistributionSystemReliability.class);
Marshaller marshaller = context.createMarshaller();
marshaller.setProperty(Marshaller.JAXB_FORMATTED_OUTPUT, true);
OutputStream os=new FileOutputStream("dsr.xml");
marshaller.marshal(new DistributionSystemReliability(900, 1800, new
LoadPointData("C1", "M1", 0.10, 4, 0.40)), os);
121
122
4.4
model are Distribution System Reliability (DSR) Service Provider and the
Service Requester. The main aim is to represent the estimation of distribution
system reliability indices as a service and to exchange the required data using
XML over SOAP. The SOAP communication model for distribution system
reliability analysis is shown in Figure 4.2.
Binding
(SAIFI service)
(SAIDI service)
(CAIDI service)
(CAIFI service)
(CTAIDI service)
(ASAI service)
(ASIFI service)
(ASIDI service)
Binding
Figure 4.2
123
the
implementation details and only expose their interfaces. In this manner, the
power system client need not be aware of any underlying technology or the
programming paradigm which the service is using.
between services allows for a quicker response to changes than the existing
conventional applications for power system operations. This results in a
much faster adoption to the need of power system industries.
4.4.1
124
125
the information needed to use, deploy, manage and control the reliability
services.
models associated with a service to define the service interface. The purpose
of service descriptor is to facilitate interaction and visibility, particularly
126
when the providers and participants are in different ownership domains. The
RSDs describe how the service provider and client communicate with each
other. It also provides the information about the data type, binding and
address information for invoking the services from the service provider. The
SAIFI service is described as follows:
<definitions name=ReliabilityService
targetNamespace="urn:Reliability">
<types>
<schema targetNamespace="urn:Reliability">
<doubleType name="estimateSAIFI">
</doubleType>
<element name="estimateSAIFIResponse" type ="string"/>
</types>
<message name="SAIFI_estimateSAIFI">
<portType name="saifi">
<operation name="estimateSAIFI">
<input message="tns: SAIFI_estimateSAIFI"/>
<output message="tns:
saifi_estimateSAIFIResponse"/></operation>
</portType>
<binding name="saifiBinding" type="tns: saifi">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document"/><operation name="estimateSAIFI">
</binding>
<service name="ReliabilityService">
<port name="saifiPort" binding="tns: saifiBinding">
<soap:address location=" http://loacalhost:8080/reliability"/>
</service>
</definitions>
127
communication model, all the reliability service objects are translated and
mapped into XML for interoperability in a heterogeneous environment. The
mapping file describes how the Java objects like package, type, port, method,
and endpoint are mapped into XML and vice versa. While invoking the
reliability service, the method call and its parameters are mapped into XML
and sent through SOAP communication protocol. When received at the client
or server end, the request / response parameters must be mapped from XML
to their proper types or objects to make interoperability inherently.
4.4.4
communication model, the SOAP request sent by the client is received by the
service provider as a SOAP MessageContext. A handler is introduced to
extract the request payload from the MessageContext and to parse it to extract
the actual data, which is required for reliability estimation services. A handler
chain is used to control the sequence of operations to obtain the desired
results. Separate handlers are introduced to carry out the intended task in
sequence to obtain the desired reliability index. In order to estimate the
128
<handler>
<handler-name>Estimation of CAIDI</handler-name>
<handler-class>reliability.CaidiImpl</handler-class>
</handler>
</handler-chain>
</handler-chains>
129
The handler chain has been associated with the CAIDI estimation
service using @HandlerChain annotation with the file element initialized
with
handler-chain.xml.
The
CAIDI
estimation
service
calls
client
has
to
establish
the
SOAP
connection
using
The SOAP
130
String destination =
"http:/192.168.1.1:1078/powersystem/ReliabilityService";
SOAPConnectionFactory soapConnFactory =
SOAPConnectionFactory.newInstance();
SOAPConnection connection = soapConnFactory.createConnection();
SOAPMessage reply = connection.call(message, destination);
131
The SOAP response for SAIFI and SAIDI services obtained using the
proposed model is shown below:
<env:envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns0="urn:reliability"
xmlns:xsd="http://www.w3.org/2001/xmlschema"
xmlns:xsi="http://www.w3.org/2001/xmlschema-instance">
<env:body>
<ns:computeresponse>
<result>
<distribution_system_evaluation>
<dsrindices>
<saifi>1.04999</saifi>
<saidi>2.02257</saidi>
..
</dsrindices>
</distribution _system _evaluation>
</result>
</ns:computeresponse>
</env:body>
</env:envelope>
In the proposed SOAP communication model, the various
reliability services can be invoked by the clients without any limitations. It
has been proven that the proposed model is capable of representing the power
system problems in heterogeneous environments.
distribution system reliability evaluation are attached in the SOAP body. The
provider sends an entire document rather than sending a set of parameters to
the clients. SOAP message handlers are used to intercept both SOAP request
and response messages and for sequencing the operations. The proposed
SOAP communication model for reliability analysis makes the distribution
132
system reliability service provider and its clients to exist in a loosely coupled
environment.
4.5
It is
133
have been developed using Internet Protocol (IP) for the Wide Area Network
(WAN) connected between the control centres and substations. This system
provides information on power failures to customers through the Internet, in
addition to the operators of the electric power sector. Moreover, the system is
able to supervise the status and failure of both the power transmission systems
and the power distribution systems simultaneously.
power failures using the operation status and activated status of the switch and the
relay. The power systems information delivering system has the following
features:
Power failure monitoring using Web browser
Reproducing at any time the power systems status in the past
The integration of the information on power systems
configuration and status for the power transmission and the
power distribution network
The integration of power systems information and geographical
map information
The provision of statistical or historical information for offline
use, such as calculated blackout time or number of customers
affected
Kivikko et al (2003) presented a Web application for viewing
customer-specific interruption data.
134
architecture that describes the system that is Web enabled and designed for
medium voltage / low voltage substation monitoring and maintenance. The
developed system utilizes Web, GSM and GPRS technologies, which are
becoming lesser and lesser expensive and makes it possible to:
inform the right persons when there is an alarm in a substation
via e-mail
inform through SMS
display on the Web through a PC with a Web browser
provide real time information from the substation and also
provide historical information
Even though Web enabled power system applications provide faster
and timely information and collaborate efficiently with other network
135
technologies, they are still facing challenges due to heterogeneous nature and
the way they are communicating with each other.
Kannammal et al (2006) have proposed a secure model based on
the concept of shared objects and mobile agents to secure the business
database present in the e-business environment.
implemented that would control the direct access to the business database
while maintaining synchronized data transfer.
136
the messaging server to have an access to any type of data sources and
capable of providing these data if its Web services are invoked.
The Messaging server provides two Web services read() and write()
that can be called by the client to write or read current values. Also client can
subscribe to some data in order to be notified if any of the attributes of this
data changed. If data changes are made, a notification is created and stored in
a buffer and the client will be intimated using notify message that new
values are available for the data to which it has subscribed. The authors have
demonstrated this SIMS messaging based on Web services to exchange data
between a hydraulic power plant and a telecontrol center.
The SIMS messaging was first used in SCADA application to
telecontrol 15,000 MW hydro power plants from four dispatching centres
(Laurent Bacon and Cedric Bellec 2006).
architecture was defined to ensure the robustness of the control systems. First
level concerns about the power unit control, the second level called as plant
local control deals with power distribution among all power units and the
third level called as dispatching center deals with control, modification and
supervision of generation schedules. SIMS is used as the communication
protocol between a dispatching center and hundreds of local control plants.
Open connectivity unified architectures are evolving based on service
oriented architecture to have effective message based communication.
Standard specifications are emerging to define a base set of generic services
to browse and query namespaces, read / write data and publish / subscribe
events and data changes.
Jeongje Park et al (2010) have developed Web based on-line real
time reliability integrated information system for monitoring reliability of
electrical energy supply including wind turbine generator. In order to supply
137
information about the quality, reliability and security of the electric service,
several techniques and methodologies have been adapted that include
traditional operation planning, real time control functions and a redesign of
control system hardware and software architectures. As the utilization of
renewable resources has been receiving considerable attention in recent years,
the information system requirement is increased. The reliability information
system is more important for implementing the smart grid. The proposed
integrated information system not only supplies the information about the
reliability indices of the power system but also the estimation of CO2
emission.
The system developed by them is used to evaluate probabilistic
production energy with reduction in production cost and to obtain CO2
emission by inserting renewable energy to the power systems. Probabilistic
reliability indices have been used extensively for generation expansion
planning. The basic reliability indices, namely the loss of load expectation
(LOLE), the expected energy not supplied (EENS) and the energy index of
reliability (EIR) can be calculated using effective load duration curve. From
these reliability indices, probabilistic production energy, production cost,
capacity factor and CO2 emission can be obtained. The proposed on-line
reliability information system is successfully established and applied to Jeju
Island Power System in South Korea. The functioning of this system can be
viewed in the Website, http://worris.gsnu.ac.kr/PraWin. The users of this
system are the system operators, decision makes and information seekers and
they will access the system with browser via the Web. Jaeseok Choi et al
(2010) have extended the above work for grid constrained probabilistic
reliability evaluation of power systems including wind turbine generators.
They have developed a multi-state model for composite power system
reliability evaluation based on the composite power system effective load
138
139
operational data as well as outage history database is high, as any client with
browser access and specialized knowledge can exploit these vulnerabilities.
At the same time, the occurrence of the critical events should be notified to
the system operators in a synchronized manner without any information loss
or omission in order to take timely decisions.
A Web service model has been proposed for event notification
system to improve scalability and a concept of remotely accessible sharable
bean component is introduced to improve the security of Web applications.
This sharable bean component named as shared object is used not only to
improve the security, but also to enable synchronized and reliable
140
Remote
Outage
History
Table
Web
Service
Sharable Bean
Component
Web
Service
Power
System
Clients
Trigger
Figure 4.3
momentary respectively.
141
Date
Time of
fault
23 March
12:02:20
12:20:30
F1
900
1800
15 April
16:13:56
16:14:26
F1
550
1100
5 May
00:23:10
01:34:29
F1
450
825
12 June
23:17:00
23:47:14
F2
400
800
6 July
09:30:10
09:31:10
F2
1850
3700
20 August
15:45:39
20:12:50
F1
450
825
31 August
08:20:00
10:20:00
F2
900
1800
3 September
17:10:00
17:20:00
F2
950
1900
2 October
10:15:00
10:55:00
F2
1850
3700
31 October
01:47:25
03:35:15
F2
900
2600
23 November 15:00:05
15:20:00
F1
550
1100
13 December
09:06:15
F2
1850
3700
09:05:10
Time of
No. of
Load Interruption
Feeder
restoration
Customers kVA
type
142
B1
DS 1
SCADA
System
(custom)
Outage
History
Table
Trigger
Create
Store
Browser
JAX-RPC
based
Web service
Invoke
Web service
E-mail
FAX/
Printer
SMS
Java Bean
Sharable
Component
Power system
Client side
Web service
143
144
through
the
message_send
trigger.
The
service, it means that the previous information is consumed, and then the
forwarding service updates the outage information attributes of the sharable
bean by invoking the remote method storeData(). Also, the flag attribute of
the bean is set to true to indicate that new information is available for the
notification service to consume.
synchronized and reliable data transfer between the database server and the
145
clients. The power system clients have to contact the notification service
continuously by sending request messages for any information update. The
clients need not contact the database server for the information. Also, the
location of sharable bean and the database server are hidden from the clients.
By this approach, the outage history database is made secure by avoiding
direct access to the database server. Since the forwarding and notification
services are deployed as Web services, they are inherently scalable and will
respond to a large number of clients who are sending request messages for
updated information.
As the system is designed to notify the fault events during power
systems operations, it is not sufficient to have only scalable and synchronized
services but also reliable services are required to notify the system events to
the power system operators at appropriate time to enable them to take
effective decisions. The reporting facility is extended to various devices to
enhance the reliable communication.
146
4.6
CONCLUSION
The predictive reliability assessment of radial distribution feeder
system using Failure Modes and Effects Analysis has been presented and
analyzed in the distributed environment.
plugged into this model and the services are made available anytime and
anywhere for the power system planning and operations.
A secure and scalable Web application framework has been
developed using SOAP communication for continuous monitoring of power
distribution systems and maintenance of outage history information which is
required for planning while further expansion. The model is designed to
report the status of the power distribution system corresponding to outage and
restoration state in a synchronized way. This model enhances the security of
operational data of different power sectors in the deregulated environment and
protects the history of outage information as the clients are not aware of the
location of the operational database. The SOAP communication model uses
147
sharable bean components and Web services to update the power system
operators automatically with outage or restoration information due to data
changes with respect to the operational status of the power systems. The
service that resides in the database server is informed about the new
information by triggering a function. The reporting facility is extended to
various devices such as PC, Fax and other electronic gadgets to enhance the
reliable communication to avoid abnormalities. The developed notification
model is scalable as the forwarding and notification services are designed as
Web services and the critical events are notified to the operators as well as to
the decision makers instantly in a synchronized way, which enables them to
take appropriate actions in time to improve the quality of service and
maintenance.