<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Smart Grids Blog</title>
	<atom:link href="http://www.smartgridsblog.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.smartgridsblog.com</link>
	<description>News  &#38; development for smart grid</description>
	<lastBuildDate>Sat, 16 Jan 2010 05:54:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Distribution Operation Modeling and Analysis (DOMA)</title>
		<link>http://www.smartgridsblog.com/distribution/distribution-operation-modeling-and-analysis-doma-2/</link>
		<comments>http://www.smartgridsblog.com/distribution/distribution-operation-modeling-and-analysis-doma-2/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 05:50:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Distribution]]></category>
		<category><![CDATA[DOMA]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/distribution/distribution-operation-modeling-and-analysis-doma-2/</guid>
		<description><![CDATA[







DOMA Narrative
This application is based on a real-time
    unbalanced distribution power flow for dynamically changing
    distribution operating conditions. It analyzes the results of the
    power flow simulations and provides the operator with the summary
    of this analysis. It further provides other applications with
 <a href="http://www.smartgridsblog.com/distribution/distribution-operation-modeling-and-analysis-doma-2/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[<!--CusAds1--><p>DOMA Narrative</h2>
<p class="MsoNormal">This application is based on a real-time<br />
    unbalanced distribution power flow for dynamically changing<br />
    distribution operating conditions. It analyzes the results of the<br />
    power flow simulations and provides the operator with the summary<br />
    of this analysis. It further provides other applications with<br />
    pseudo-measurements for each distribution system element from<br />
    within substations down to load centers in the secondaries. The<br />
    model is kept up-to-date by real-time updates of topology,<br />
    facilities parameters, load, and relevant components of the<br />
    transmission system. </p>
<p class="MsoNormal">The Distribution Operation Modeling and Analysis<br />
supports three modes of operation:</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
1.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>&nbsp;Real-time mode, which reflects present conditions in the power<br />
system.</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
2.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>&nbsp;Look-ahead mode, which reflects conditions expected in the<br />
near future (from one hour to one week ahead)</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
3.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>&nbsp;Study mode, which provides the capability of performing the<br />
“what if” studies.</p>
<p class="MsoNormal">
<img border="0" src="http://intelligrid.ipower.com/IntelliGrid_Architecture/Use_Cases/images/ADA_Information_Flows.jpg" width="800" height="602">

<!-- Quick Adsense Wordpress Plugin: http://techmilieu.com/quick-adsense -->
<div style="float:left;margin:10px 10px 10px 0;">
<script type="text/javascript"><!--
google_ad_client = "pub-4979295129832072";
/* 336x280图片, 创建于 10-1-14 */
google_ad_slot = "5113627842";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
</div>

</p>
<p class="MsoNormal">The key sub-functions performed by the<br />
application are as follows:</p>
<h3>Modeling Transmission/Sub-Transmission System Immediately Adjacent<br />
to Distribution Circuits</h3>
<p class="MsoNormal">This sub-function provides topology and<br />
electrical characteristics of those substation transformers and<br />
transmission/sub-transmission portions of the system, where loading<br />
and voltage levels significantly depend on the operating conditions of<br />
the particular portion of the distribution system.&nbsp; The model also<br />
includes substation transformers and transmission/sub-transmission<br />
lines with load and voltage limits that should be respected by the<br />
application.&nbsp;&nbsp; </p>
<h3>Modeling Distribution Circuit Connectivity</h3>
<p class="MsoBodyText">This sub-function provides a topological model<br />
of distribution circuits, starting from the distribution side of the<br />
substation transformer and ending at the equivalent load center on the<br />
secondary of each distribution transformer. A topological consistency<br />
check is performed every time connectivity changes. The model input<br />
comes from SCADA/EMS, Distribution SCADA, from field crews, from DISCO<br />
operator, from AM/FM/GIS, WMS, and OMS databases, and engineers.&nbsp; </p>
<h3 style="text-indent: 0in; page-break-after: avoid; margin-left: 0in">
Data Management Issues between AM/FM/GIS and ADA Distribution<br />
Connectivity Database</h3>
<p class="MsoBodyText">Standard interfaces between different AM/FM/GIS<br />
databases, data converters, and ADA database are not developed yet for<br />
practical use. The AM/FM/GIS databases were not designed for real-time<br />
operational use. They lack many objects and attributes needed for ADA.<br />
The population of the databases is not supported by an interactive<br />
consistency check. The existing extractors of data and the converters<br />
into ADA databases do not determine all data errors. The ADA<br />
applications must conduct additional data consistency checking and<br />
data corrections before recommendations and controls are issued.<br />
Typically utility do not have established procedures for regular<br />
update of the AM/FM/GIS databases by the operation and maintenance<br />
personnel. Therefore many changes implemented in the field remain<br />
unnoticed by the databases. Synchronization of the field state with<br />
the ADA database is a challenge in modern utilities. </p>
<h3 style="text-indent: 0in; margin-left: 0in">Data Management Issues<br />
between CIS and AM/FM/GIS and ADA Distribution Connectivity Database</h3>
<p class="MsoBodyText">For the ADA applications, the AM/FM/GIS data<br />
must be associated with the corresponding customer information data<br />
from the CIS database. This data include billing data and description<br />
of the customer specifics, such as rate schedule, customer code, meter<br />
number, address, etc. The critical information is the billing data.<br />
This data is updated based on metering cycles (typically one month)<br />
and is not well synchronized. In order to synchronize billing data an<br />
automated meter reading system should be implemented. In order to<br />
update the ADA databases more frequently, which would increase the<br />
resolution of ADA functions to individual distribution transformers<br />
and even customers, a high capacity communication system should be<br />
introduced to gather the data from hundreds of thousands of meters at<br />
the same time. Some of the modern procedures enabled by AMR conflict<br />
with the needs of ADA model.An example is the consolidated bills,<br />
where the individual load data of distribution transformers located in<br />
different sites of the consolidated company becomes unavailable for<br />
the external to CIS world.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
<h3>Modeling Distribution Nodal Loads</h3>
<p class="MsoNormal">This sub-function provides characteristics of<br />
real and reactive load connected to secondary side of distribution<br />
transformer or to primary distribution circuit in case of primary<br />
meter customers. These characteristics are sufficient to estimate kW<br />
and kvars at a distribution node at any given time and day and include<br />
the load shapes and load-to-voltage sensitivities (for real and<br />
reactive power) of various load categories. In real-time mode, the<br />
nodal loads are balanced with real-time measurements obtained from<br />
corresponding primary circuits. A validity check is applied to<br />
real-time measurements.&nbsp; The load model input comes from Distribution<br />
SCADA, from CIS supported by AMR and linked with AM/FM/GIS, and<br />
weather forecast systems.</p>
<h3>Modeling Distribution Circuit Facilities</h3>
<p class="MsoNormal">This sub-function models the following<br />
distribution circuit facilities:</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
1.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>Overhead and underground line segments</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
2.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>Switching devices</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
3.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>&nbsp;Substation and distribution transformers, including step-down<br />
transformers</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
4.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>&nbsp;Station and feeder capacitors and their controllers</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
5.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>&nbsp;Feeder series reactors</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
6.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>&nbsp;Voltage regulators (single- and three-phase) and their<br />
controllers</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
7.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>&nbsp;LTC’s and their controllers</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
8.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>&nbsp;Distribution generators and synchronous motors</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
9.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7.0pt; font-family: Times New Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
</span>Load equivalents for higher frequency models</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">All facilities should be modeled with sufficient<br />
details to support the required accuracy of Distribution Operation<br />
Modeling and Analysis application. </p>
<h3>Distribution Power Flow</h3>
<p class="MsoNormal">The sub-function models the power flow including<br />
the impact of automatically controlled devices (i.e., LTCs, capacitor<br />
controllers, voltage regulators), and solves both radial and meshed<br />
networks, including those with multiple supply busses (i.e. having<br />
Distributed Energy Resources (DER) interconnected to the power<br />
system).&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
<h3>Evaluation of Transfer Capacity</h3>
<p class="MsoNormal">This sub-function estimates the available<br />
bi-directional transfer capacity for each designated tie switch. The<br />
determined transfer capacity is such that the loading of a tie switch<br />
does not lead to any voltage or current violations along the<br />
interconnected feeders.</p>
<h3>Power Quality Analysis</h3>
<p class="MsoNormal">This sub-function performs the power quality<br />
analysis by:</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
1.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><br />
Comparing (actual) measured and calculated voltages against the limits</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
2.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><br />
Determining the portion of time the voltage or imbalance are outside<br />
the limits</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
3.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><br />
Determining the amount of energy consumed during various voltage<br />
deviations and imbalance</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
4.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><br />
Recording the time when voltage violations occur</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
5.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><br />
Performing modeling of higher harmonics propagation and resonant<br />
conditions based on information available from the sources of harmonic<br />
distortion</p>
<p class="MsoNormal" style="text-indent: -.25in; margin-left: .75in">
6.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><br />
Performing modeling of rapid voltage changes based on information<br />
available from the sources of voltage distortion</p>
<p class="MsoNormal">The sub-function provides the ability to estimate<br />
the expected voltage quality parameters during the planned changes in<br />
connectivity and reactive power compensation.&nbsp; </p>
<h3>Loss Analysis</h3>
<p class="MsoNormal">This sub-function bases its analysis on technical<br />
losses (e.g., conductor I<sup>2</sup>R losses, transformer load and<br />
no-load losses, and dielectric losses) calculated for different<br />
elements of the distribution system (e.g., per feeder or substation<br />
transformer). For the defined area, these losses are accumulated for a<br />
given time interval (month, quarter, year, etc.). They are further<br />
compared with the difference between the energy input (based on<br />
measurements) into the defined area and the total of relevant billed<br />
kWh (obtained from the database), normalized to the same time<br />
interval. The result of the comparison is an estimate of commercial<br />
losses (e.g., metering errors and theft).</p>
<h3>Fault Analysis</h3>
<p class="MsoNormal">This sub-function calculates three-phase,<br />
line-to-line-to-ground and line-to-ground fault currents for each<br />
protection zone associated with feeder circuit breakers and field<br />
reclosers. The minimum fault current is compared with protection<br />
settings while the maximum fault current is compared with interrupting<br />
ratings of breakers and reclosers. If the requirements are not met, a<br />
message is generated for the operator.</p>
<h3>Evaluation of Operating Conditions</h3>
<p class="MsoNormal">This sub-function determines the difference<br />
between the existing substation bus voltage and the substation bus<br />
voltages limits.&nbsp; </p>
<p class="MsoNormal">The sub-function also estimates the available<br />
dispatchable real and reactive load obtainable via volt/var control.&nbsp;&nbsp;<br />
The operator or other applications can use this information for<br />
selective load reduction. The sub-function provides aggregated<br />
operational parameters for the transmission buses to be used in<br />
transmission operation models.</p>
<h2>DOMA Steps</h2>
<p>The DOMA Steps include:</p>
<ul>
<li>DOMA Data Conversion</li>
<li>DOMA without Events</li>
<li>DOMA with Events Causing<br />
          It to Run</li>
<li>DOMA Runs Based on a Schedule</li>
<li>DOMA Used in Study<br />
          Mode or Look-Ahead Mode</li>
</ul>
<h3>DOMA Data Conversion</h3>
<p>
<img border="1" src="http://intelligrid.ipower.com/IntelliGrid_Architecture/Use_Cases/images/ADA_Data_Conversion_small.jpg" xthumbnail-orig-image="images/ADA_Data_Conversion.jpg" width="700" height="497"></p>
<p>&nbsp;</p>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/distribution/distribution-operation-modeling-and-analysis-doma-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Distribution Operations &#8211; Overview of Advanced Distribution Automation</title>
		<link>http://www.smartgridsblog.com/distribution/distribution-operations-overview-of-advanced-distribution-automation/</link>
		<comments>http://www.smartgridsblog.com/distribution/distribution-operations-overview-of-advanced-distribution-automation/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 03:51:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Distribution]]></category>
		<category><![CDATA[Distribution Automation]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/?p=1176</guid>
		<description><![CDATA[Introduction to Advanced Distribution Automation (ADA)
Objective: The objective of Advanced
Distribution Automation Function is to enhance the reliability of
power system service, power quality, and power system efficiency,
by automating the following three processes of distribution
operation control: data preparation in near-real-time; optimal
decision-making; and the control of distribution operations in
coordination with transmission and generation systems operations.
Scope: The ADA Function <a href="http://www.smartgridsblog.com/distribution/distribution-operations-overview-of-advanced-distribution-automation/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[
<!-- Quick Adsense Wordpress Plugin: http://techmilieu.com/quick-adsense -->
<div style="float:right;margin:10px 0 10px 10px;">
<script type="text/javascript"><!--
google_ad_client = "pub-4979295129832072";
/* 336x280, 创建于 10-1-4 */
google_ad_slot = "6171198131";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
</div>
<h1>Introduction to Advanced Distribution Automation (ADA)</h1>
<p class="MsoNormal"><strong>Objective: </strong>The objective of Advanced<br />
Distribution Automation Function is to enhance the reliability of<br />
power system service, power quality, and power system efficiency,<br />
by automating the following three processes of distribution<br />
operation control: data preparation in near-real-time; optimal<br />
decision-making; and the control of distribution operations in<br />
coordination with transmission and generation systems operations.</p>
<p class="MsoNormal"><strong>Scope:</strong> The ADA Function performs a) data<br />
gathering, along with data consistency checking and correcting; b)<br />
integrity checking of the distribution power system model; c) periodic<br />
and event-driven system modeling and analysis; d) current and<br />
predictive alarming; e) contingency analysis; f) coordinated volt/var<br />
optimization: g) fault location, isolation, and service restoration;<br />
h) multi-level feeder reconfiguration; i) pre-arming of RAS and<br />
coordination of emergency actions in distribution; j) pre-arming of<br />
restoration schemes and coordination of restorative actions in<br />
distribution, and k) logging and reporting. These processes are<br />
performed through direct interfaces with different databases and<br />
systems, (EMS, OMS, CIS, MOS, SCADA, AM/FM/GIS, AMS and WMS),<br />
comprehensive near real-time simulations of operating conditions, near<br />
real-time predictive optimization, and actual real-time control of<br />
distribution operations.</p>
<p class="MsoNormal"><strong>Rationale:</strong> By meeting its objectives in<br />
near-real time, the Function makes a significant contribution to<br />
improving the power system operations through automation, which cannot<br />
be achieved using existing operational methods.  </p>
<p class="MsoNormal"><strong>Status</strong>: The methodology and specification<br />
of the Function for current power system conditions have been<br />
developed, and prototype (pilot) and system-wide project in several<br />
North-American utilities have been implemented by Utility Consulting<br />
International and its client utilities prior to IntelliGrid Architecture project.  </p>
<p><img src="http://intelligrid.ipower.com/IntelliGrid_Architecture/Use_Cases/DO_ADA_Overview_files/image002.gif" border="0" alt="" width="721" height="427" />

</p>
<p>Figure 1: Coordination of ADA applications is accomplished through<br />
internal interfaces within the ADA function and through the feedback<br />
from the power system</p>
<p><img src="http://intelligrid.ipower.com/IntelliGrid_Architecture/Use_Cases/DO_ADA_Overview_files/image004.jpg" border="0" alt="" width="760" height="539" /></p>
<p>Figure 2: Real-Time Distribution Operations showing Interactions<br />
and Information Flows</p>
<p><img src="http://intelligrid.ipower.com/IntelliGrid_Architecture/Use_Cases/DO_ADA_Overview_files/image006.gif" border="0" alt="" width="677" height="493" /></p>
<p>Figure 3: What Do We Need to Know to Optimally Control<br />
Distribution?</p>
<p><img src="http://intelligrid.ipower.com/IntelliGrid_Architecture/Use_Cases/DO_ADA_Overview_files/image008.gif" border="0" alt="" width="723" height="549" /></p>
<p>Figure 4: Information Flows within Advanced Distribution Automation<br />
(ADA)</p>
<h2>Source:EPRI</h2>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/distribution/distribution-operations-overview-of-advanced-distribution-automation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wide-Area Monitoring And Control – Automated Control Functions</title>
		<link>http://www.smartgridsblog.com/transmission/wide-area-monitoring-and-control-%e2%80%93-automated-control-functions/</link>
		<comments>http://www.smartgridsblog.com/transmission/wide-area-monitoring-and-control-%e2%80%93-automated-control-functions/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 03:22:36 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Monitoring&Control]]></category>
		<category><![CDATA[Transmission]]></category>
		<category><![CDATA[Interlocking]]></category>
		<category><![CDATA[Load Balancing]]></category>
		<category><![CDATA[Sequenced Controls]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/?p=1171</guid>
		<description><![CDATA[







Contents

Narrative
Normal Sequence Steps
Steps – Alternative / Exception Sequences

Narrative
Transmission Automated Control (Baseline) describes a set of functions that are typically automated within a substation, but are not directly associated with protection, fault handling, or equipment maintenance.  In general, they serve to optimize the operation of the power system and ensure its safe operation by preventing manually <a href="http://www.smartgridsblog.com/transmission/wide-area-monitoring-and-control-%e2%80%93-automated-control-functions/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[<!--CusAds1--><h2>Contents</h2>
<ul>
<li>Narrative</li>
<li>Normal Sequence Steps</li>
<li>Steps – Alternative / Exception Sequences</li>
</ul>
<h2>Narrative</h2>
<p>Transmission Automated Control (Baseline) describes a set of functions that are typically automated within a substation, but are not directly associated with protection, fault handling, or equipment maintenance.  In general, they serve to optimize the operation of the power system and ensure its safe operation by preventing manually generated faults.  These functions include:</p>
<ul>
<li>Changing transformer taps to regulate system voltage</li>
<li>Switching capacitor banks or shunts in and out of the system to control voltage and reactive load</li>
<li>Interlocking of controls to prevent unsafe operation</li>
<li>Sequencing controls to ensure safe operation</li>
<li>Load balancing of feeders and transmission lines to reduce system wear and resistive losses</li>
<li>Restoring service quickly in the event of a fault, with or without operator confirmation</li>
</ul>
<p>The functions described in this use case were traditionally performed by individual devices acting alone.  When implemented this way, they did not have any effect on the communications system.  However, in the last five to seven years, these functions have been distributed across the substation.  That is, the software logic controlling the function now often resides on a different device than the one which provides the inputs or outputs to the process.</p>
<p>This change has taken place because the use of substation LANs has made it economical to place Intelligent Electronic Devices (IEDs) close to the equipment they are monitoring and controlling.  Logic has therefore either been centralized, with a single Substation Computer using the IEDs as remote controllers, or it has been distributed among the IEDs themselves.  In either case, the communications system has now become part of the automation functions.</p>
<h3>Voltage Regulation using Tap Changers</h3>
<p>In voltage regulation, the automation system ensures a constant voltage on the substation bus by adjusting the tap of one or more transformers.  A monitoring IED provides a voltage value to the Substation Computer, which has been programmed with threshold and hysteresis logic. The IED is usually monitoring the bus side of a transformer.  In more complex situations, IEDs may monitor multiple voltages throughout the station and pass them all to the Substation Computer as input to the logic. When the logic indicates that the bus voltage must be adjusted, the Substation Computer issues a control operation to the IED connected to the transformer tap.  This will change the monitored voltage, which will be fed back through the logic.</p>
<p>The voltage control logic typically has a pre-programmed qualification delay in the tens of seconds – adjusting the tap causes wear on the equipment, so adjustments should not be made lightly.  Therefore, an appropriate update time for the monitored voltage is on the order of one-half second to one second.  Because of the wear on the transformer and tap, and the impact on the rest of the system if adjusted wildly, tap raise/lower operations are typically performed with select-before-operate logic.  Redundancy and reliability of the communications path is important.</p>
<h3>Volt/VAR Regulation using Capacitor or Shunt Control</h3>
<p>In capacitor bank control, the automation system optimizes the voltage and inductive load on a line or bus by connecting or disconnecting one or more capacitor banks.  It prevents the imaginary part of the load from becoming too large, reducing voltage and the efficiency of the system.  The banks may be widely located across the power system, or within the substation.  There are many different logic algorithms for performing capacitor bank control.  The simplest is calendar or time of day control, in which the load on the power system is not even monitored.  The logic simply assumes that the inductive load will be higher at certain times of the day or year.  In areas where inductive load is largely caused by air conditioning, logic may switch based on ambient temperature.  Some algorithms monitor voltage only and switch when it passes certain thresholds.  More sophisticated algorithms monitor both current and voltage and switch based on either the calculated power factor or directly on the calculated inductive load (VARs).  There are typically hysteresis settings on such logic to prevent frequent switching.  Shunt control occurs under similar conditions, but with the addition or removal of inductive loads.</p>
<p>In distributed Volt/VAR control, one IED controls one capacitor bank on a given line, and each IED makes switching decisions individually.  In centralized Volt/VAR control, each IED reports monitored values back to a Substation Computer.  The Substation Computer may make switching decisions based on averages or groupings of voltages.  When it decides a switch is necessary, it sends a control message to the appropriate IED, which may or may not be the device reporting the controlled measurements.</p>
<p>The hysteresis in some Volt/VAR algorithms may often be in hours, so communication delays in tens of seconds are easily acceptable.  It is fairly common to broadcast capacitor bank control messages, without any select-before-operate logic, since the effect of any given control is usually small.  When capacitor banks are located remotely, pagers have sometimes been used as a communications media – one number to switch the bank in, one to disconnect it.</p>
<h3>Interlocking</h3>
<p>Interlocking prevents unsafe operation of the various switches and breakers within a substation.  When an Operator or software application attempts to operate a control, the automation system evaluates the state of the entire system and may reject the control request based on pre-programmed logic.  This logic corresponds directly to the topology and interconnection of the substation.  Simpler substations may have little or no interlocking.  The most complex logic is associated with complex transformer and bus redundancy systems. </p>
<p>For instance, an operator will close an earthing switch on a section of the bus to ground it prior to permitting maintenance on the equipment.  However, the operator may not be aware that the bus section is still live due to an interconnection with another bus section or a feeder fed by another bus section.  The automation system must prevent a fault by rejecting the Operator’s request.</p>
<p>Interlocking is most reliably and efficiently performed by the device that must perform the requested operation.  In the past, it may have been performed by the substation GUI or SCADA master station, when those were the only locations that could perform switching.  It is still often performed by a Substation Computer or Data Concentrator which serves as a clearinghouse for all control operations to the substation.  This centralized logic mechanism is still used, especially because deregulation has increased the number of master stations that require access to the substation.</p>
<p>However, more and more frequently, interlocking is performed by logic on the IEDs themselves, operating on data distributed by peer-to-peer communications between the devices.  This peer-to-peer communications has been made possible by the introduction of the substation LAN.  Performing interlocking at the IED permits the same logic and performance to be in effect regardless of whether the control request originates at a remote site, at a substation GUI, at the control panel of the IED, or even a manual panel switch.</p>
<p>In an ideal system, the state information required to perform interlocking would be updated simultaneously throughout the system.  Any delay provides a window in which a control could be mis-operated.  However, in practice, it is sufficient to update the state of the system in less than a second or two.  This interval represents the typical time between the moment an Operator checks the state of the system on a GUI or display panel, and the moment the Operator makes the control request.  As more automation applications are deployed in the substation, human reaction time will become less of a factor, and the demands on interlocking will increase.  Today, a challenging interlocking requirement for an advanced substation is less than 200 milliseconds between updates.</p>
<p>The control itself is typically issued with select-before-operate logic.  The distribution of state information for interlocking may be broadcast or multicast.  Redundancy and reliability is extremely important.</p>
<h3>Sequenced Controls</h3>
<p>While interlocking is intended to prevent Operator-initiated faults by rejecting invalid controls, sequenced controls automate some portion of the Operator’s tasks to eliminate the possibility of an invalid control ever being issued.</p>
<p>For example, consider a substation with two transformers and a normally open switch between the two bus sections connected to each transformer.  There are two different philosophies that an Operator may employ to take one of the transformers out of service.  In “make before break”, the Operator should (1) connect the two buses, (2) disconnect the transformer from the bus, and (3) disconnect the transformer from the upstream transmission line.  This method ensures there will be no outage of service.  In “break before make”, however, the Operator should (A) disconnect the transformer, then (B) quickly connect the bus and then (C) disconnect the transmission line.  This results in an outage, but prevents side effects resulting from mis-matched transformers sharing the same bus.</p>
<p>In a sequenced control, the Operator simply requests the isolation of the transformer, and the automation system performs the controls in the sequence required by the utility.  The Operator is not permitted to perform any other sequence.  In the “break before make” case above, it also ensures that the resulting outage is as small as possible, because the automation system can perform the sequence faster than a human.</p>
<p>The speed of a sequenced control is related to the components involved in the sequence.  For instance, the logic may need to wait for motorized switches to connect or disconnect before proceeding with the next control in the sequence.  In a “break before make” sequence as described above, however, the length of the outage must be minimized and a value of less than half a second is typically desired.  All sequenced controls are typically service-affecting and are therefore executed with select-before-operate logic.</p>
<h3>Load Balancing</h3>
<p>Load balancing is typically a distribution operation, performed between two transformers within a substation, but may also be performed in transmission systems between substations.  In the distribution case, two feeders serviced by separate transformers are connected at their remote ends by a normally open switch.  A pole-top IED controls the switch.  Other IEDs monitor load on the line.  The IEDs report the state and load of the system to a Substation Computer.  The Substation Computer detects the condition when one transformer is heavily loaded and the other has excess capacity, and sends a message to the pole-top IED to close the switch.  Now, instead of one line loaded at 90% and the other at 25%, both may be loaded at 50%.  Since resistive losses vary with the square of the current, this action improves the efficiency of the power system and reduces wear on equipment.  In transmission systems, two substations having lines feeding the same third substation may share load.  This type of logic is typically centralized, not distributed.</p>
<p>As with tap changing, load balancing is not an action that is typically performed lightly.   Qualification times for the logic may be measured in minutes or even hours.  Therefore, update times and control transmission times may be measured in seconds.  In distribution operations, this is fortunate because IEDs controlling the switches may be remote and only reached via slow links.  Some utilities may prefer that the process not be completely automated, and that the automation system request confirmation from the Operator before taking action.  Reliability of the data is important and redundant links may be used.</p>
<h3>Automated Service Restoration</h3>
<p>Automated Service Restoration is typically a distribution operation, but may be performed in transmission systems when “loops” are possible between substations.  In the distribution case, two feeders are connected at their remote ends by a normally open switch.  Several other switch / breaker combinations are located at other points along the feeders.  All the switches and breakers are monitored by IEDs.  When a fault occurs, the IEDs on the upstream side of the fault trips its breaker.  It notifies the Substation Computer of its action.  The IED on the downstream side of the fault notifies the Substation Computer of the loss of current and estimates the direction of the fault.  Based on that information and pre-configured logic, the Substation Computer recommends to the Operator that the breaker of the downstream IED should be opened and the normally open switch should be closed.  The Operator typically directs the Substation Computer to do so, and the Substation Computer forwards the decision to the IEDs.  When the IEDs perform the operations, power is restored to all portions of the feeders except the section in which the fault occurred.  The more break points there are in the feeders, the fewer customers will be affected by a given fault.</p>
<p>Time is of the essence in service restoration, but utilities typically require an Operator approve the decision of the system, so the human Operator is usually the slowest link in the system.  Communications times may be measured in seconds.  The breaker tripping is done by an individual IED without need for communications.</p>
<p>An alternative scenario occurs if the fault is not on the main feeder but on a lateral.  In this case, the fault causes the protection IED at the substation to trip and attempt reclosure.  While the current is zero between reclosure attempts, the IED nearest the fault opens its switch to clear the fault.  This is called “auto-sectionalization”.  Then, when the next reclosure occurs, service is restored to all subscribers except those on the lateral.  In this case, there is no effect on the communications system other than to monitor that the events occurred.</p>
<h2>Normal Sequence Steps</h2>
<p> </p>
<table border="1" cellspacing="0" cellpadding="0" width="100%">
<thead>
<tr>
<td>#</td>
<td>Event</td>
<td>Name of Process/Activity</td>
<td>Description of<br />
Process/Activity</td>
<td>Information Producer</td>
<td>Information<br />
Receiver</td>
<td>Name of Info Exchanged</td>
<td valign="top"> </td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top">1.1               </td>
<td valign="top">Voltage Change</td>
<td valign="top">Change in Voltage</td>
<td valign="top">VOLTAGE REGULATION.  IED identifies that the voltage has exceeded the deadband to be recognized as a change and notifies the Substation Computer Device. </p>
<p>May be performed by one or more IEDs depending on the logic being used.  Substation Computer Device maps the point number into its database, stores the value, and runs the voltage control logic.  Typically starts a qualification timer to avoid rapid and frequent tap changes.</td>
<td valign="top">IEDs</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Voltage</td>
<td valign="top"> </td>
</tr>
<tr>
<td valign="top">1.2               </td>
<td valign="top">Qualification Timeout</td>
<td valign="top">Tap Change</td>
<td valign="top">Substation Computer Device identifies that the voltage change(s) received from the IED(s) represent a significant change and require action.  Issues a command to the IED.</p>
<p>IED performs the tap change through local I/O.  Causes voltage change (1.1) and cycle repeats.</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">IED</td>
<td valign="top">Tap Change Control</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">2.1               </td>
<td valign="top">Load Change</td>
<td valign="top">Change in Load</td>
<td valign="top">VOLT/VAR REGULATION.  IED identifies that the voltage and/or current has exceeded the deadband to be recognized as a change and notifies the Substation Computer Device. </p>
<p>May be performed by one or more IEDs depending on the logic being used.  Substation Computer Device maps the point number into its database, stores the value, and runs the Volt/VAR control logic.  Starts a qualification timer if appropriate.</p>
<p>If extremely simple control logic is being used (e.g. calendar, time-of-day, this step may be omitted).</td>
<td valign="top">IED</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Voltage, Current</td>
<td valign="top"> </td>
</tr>
<tr>
<td valign="top">2.2               </td>
<td valign="top">Qualification Timeout</td>
<td valign="top">Adjust Reactive Load</td>
<td valign="top">Substation Computer Device decides that it is time to adjust the load and issues a control to the appropriate IED.  Applies qualification times and hysteresis algorithms to avoid many rapid adjustments.</p>
<p>May not be the same IED as last reported a Load Change.</p>
<p>Adjustment usually causes a Load Change (2.1) and cycle repeats.</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">IED</td>
<td valign="top">Control</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">3.1               </td>
<td valign="top">System State Change</td>
<td valign="top">Change of System State</td>
<td valign="top">INTERLOCKING.  IED detects a change in a switch or breaker that it is monitoring and transmits the state change to the device implementing the logic, either the Substation Computer Device or one or more peer IEDs.</p>
<p>Substation Computer Device or peer IED maps the point number into its database, stores the value, and thus updates its current “picture” of the system state.</td>
<td valign="top">IED</td>
<td valign="top">IED or Substation Computer Device</td>
<td valign="top">Switch State, Voltage, Current</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">3.2               </td>
<td valign="top">Switch Request</td>
<td valign="top">Request Switch</td>
<td valign="top">System Operator  requests that a particular switch or breaker be opened or closed.  Device receiving the command runs interlocking logic and either denies (3.3) or accepts (3.4) the request.</td>
<td valign="top">System Operator</td>
<td valign="top">IED or Substation Computer Device</td>
<td valign="top">Control Request</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env7_Intra-Control_Center.htm"></a></td>
</tr>
<tr>
<td valign="top">3.3               </td>
<td valign="top"> </td>
<td valign="top">Deny Request</td>
<td valign="top">Device performing the interlocking logic rejects the attempt as being unsafe.</td>
<td valign="top">IED or Substation Computer Device</td>
<td valign="top">System Operator</td>
<td valign="top">Control Status</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env7_Intra-Control_Center.htm"></a></td>
</tr>
<tr>
<td valign="top">4.1               </td>
<td valign="top">Sequenced Control Request</td>
<td valign="top">Request Sequenced Control</td>
<td valign="top">SEQUENCED CONTROL.  System Operator  requests a sequence to be performed.</td>
<td valign="top">System Operator</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Control Request</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env7_Intra-Control_Center.htm"></a></td>
</tr>
<tr>
<td valign="top">4.2               </td>
<td valign="top"> </td>
<td valign="top">Send Control</td>
<td valign="top">Substation Computer Device runs the sequence logic and issues the next control to an IED.</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">IED</td>
<td valign="top">Control</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">4.3               </td>
<td valign="top">Feedback</td>
<td valign="top">Send Feedback</td>
<td valign="top">IED provides feedback about whether the last control was successful.</p>
<p>Substation Computer Device maps the point number into its database, stores the value, and runs the sequence logic.  Typically logs the state change and its time.</p>
<p>If feedback was successful, Substation Computer Device initiates next control (4.2).  If not, if the feedback timed out, or if this was the last control, may terminate sequence (4.4).</td>
<td valign="top">IED</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Switch State</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">4.4               </td>
<td valign="top">Sequence Complete</td>
<td valign="top">Terminate Sequence</td>
<td valign="top">Substation Computer Device stops the sequence logic and indicates to System Operator  the status of the sequence.</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">System Operator</td>
<td valign="top">Control Status</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env7_Intra-Control_Center.htm"></a></td>
</tr>
<tr>
<td valign="top">5.1               </td>
<td valign="top">Load Change</td>
<td valign="top">Change in Load</td>
<td valign="top">LOAD BALANCING.  IED identifies that the current has exceeded the deadband to be recognized as a change and notifies the Substation Computer Device. </p>
<p>May be performed by one or more IEDs depending on the logic being used.  Substation Computer Device maps the point number into its database, stores the value, and runs the load balancing control logic.</td>
<td valign="top">IED(s)</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Current, Voltage</td>
<td valign="top"> </td>
</tr>
<tr>
<td valign="top">5.2               </td>
<td valign="top">Request to Connect Feeders / Lines</td>
<td valign="top">Request Connection to Feeders / Lines</td>
<td valign="top">Substation Computer Device determines that load has exceeded acceptable thresholds and that conditions are met to perform balancing. </p>
<p>Requests that System Operator  connect a particular two feeders or lines.</p>
<p>System Operator  either confirms the operation (5.3) or does nothing, and load continues to increase (5.1).</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">System Operator</td>
<td valign="top">Automated Control Request</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env7_Intra-Control_Center.htm"></a></td>
</tr>
<tr>
<td valign="top">5.3               </td>
<td valign="top"> </td>
<td valign="top">Confirm Request</td>
<td valign="top">System Operator  issues control accepting the request.</td>
<td valign="top">System Operator</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Confirm</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env7_Intra-Control_Center.htm"></a></td>
</tr>
<tr>
<td valign="top">5.4               </td>
<td valign="top"> </td>
<td valign="top">Balance Load</td>
<td valign="top">Substation Computer Device issues a control to connect the two feeders or lines.</p>
<p>Load will readjust and cycle repeats (5.1).</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">IED</td>
<td valign="top">Control</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">6.1               </td>
<td valign="top">Fault</td>
<td valign="top">Breaker Trip</td>
<td valign="top">AUTOMATIC SERVICE RESTORATION.  IED detects fault and trips breaker.  Notifies Substation Computer Device of the trip, and (through the point number) the direction and distance to the fault.</td>
<td valign="top">Upstream IED</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Trip</td>
<td valign="top"> </td>
</tr>
<tr>
<td valign="top">6.2               </td>
<td valign="top">Loss of Current</td>
<td valign="top">Report Loss of Current</td>
<td valign="top">IEDs detect loss of current.  Notify Substation Computer Device of the event and the suspected direction and distance of the fault.</td>
<td valign="top">Downstream IEDs</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">No Current Detected,</p>
<p>No Voltage Detected</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">6.3               </td>
<td valign="top"> </td>
<td valign="top">Request Restoration</td>
<td valign="top">Substation Computer Device runs auto-restoration logic and determines which switch should open.  Requests permission to open that switch and close the normally-open switch.</p>
<p>System Operator  will either confirm the request (6.4), or decide to perform some other operation through the Substation Computer Device.</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">System Operator</td>
<td valign="top">Automated Control Request</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env7_Intra-Control_Center.htm"></a></td>
</tr>
<tr>
<td valign="top">6.4               </td>
<td valign="top"> </td>
<td valign="top">Confirm Request</td>
<td valign="top">System Operator  tells the Substation Computer Device to execute the restoration.</td>
<td valign="top">System Operator</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Confirm</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env7_Intra-Control_Center.htm"></a></td>
</tr>
<tr>
<td valign="top">6.5               </td>
<td valign="top"> </td>
<td valign="top">Open Switch</td>
<td valign="top">Substation computer performs control to open the downstream switch nearest the fault.</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Downstream IED</td>
<td valign="top">Control</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">6.6               </td>
<td valign="top"> </td>
<td valign="top">Close Switch</td>
<td valign="top">Substation Computer Device performs control to close the normally-open switch.</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">IED controlling normally open switch</td>
<td valign="top">Control</td>
<td valign="top"> </td>
</tr>
<tr>
<td valign="top">6.7               </td>
<td valign="top"> </td>
<td valign="top">Send Feedback</td>
<td valign="top">IEDs update system state and load to Substation Computer Device.  Substation Computer Device maps data and stores in database.</td>
<td valign="top">IEDs</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Switch State, Current, Voltage</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
</tbody>
</table>
<hr size="1" /> </p>
<h2>Steps – Alternative / Exception Sequences</h2>
<p> </p>
<table border="1" cellspacing="0" cellpadding="0" width="100%">
<thead>
<tr>
<td>#</td>
<td>Event</td>
<td>Name of Process/Activity</td>
<td>Description of<br />
Process/Activity</td>
<td>Information Producer</td>
<td>Information<br />
Receiver</td>
<td>Name of Info Exchanged</td>
<td valign="top"> </td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top">3.1               </td>
<td valign="top"> </td>
<td valign="top">Execute Request</td>
<td valign="top">Device performing the interlocking logic tells the IED to operate the control request.  May be the same IED.</td>
<td valign="top">IED or Substation Computer Device</td>
<td valign="top">IED</td>
<td valign="top">Control</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">3.2               </td>
<td valign="top"> </td>
<td valign="top">Confirm Request</td>
<td valign="top">Device performing the interlocking logic informs the System Operator  that the request has been successfully performed.</td>
<td valign="top">IED or Substation Computer Device</td>
<td valign="top">System Operator</td>
<td valign="top">Control Status</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env7_Intra-Control_Center.htm"></a></td>
</tr>
<tr>
<td valign="top">X.1              </td>
<td valign="top">Fault</td>
<td valign="top">Trip Breaker</td>
<td valign="top">IED detects fault and trips breaker.  Notifies Substation Computer Device of the trip, and (through the point number) the direction and distance to the fault.  Starts reclosure timer.</td>
<td valign="top">Upstream IED</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Trip</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">X.2              </td>
<td valign="top"> </td>
<td valign="top">Report Lateral Switch Open</td>
<td valign="top">IED detects the fault and that current is zero. Waits a configured number of reclosure attempts, then opens the switch for the Lateral.  Notifies the Substation Computer Device.</td>
<td valign="top">Lateral IED</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Switch State</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
<tr>
<td valign="top">X.3              </td>
<td valign="top"> </td>
<td valign="top">Breaker Reclosed</td>
<td valign="top">Upstream IED successfully recloses the breaker and notifies the Substation Computer Device that service is restored.</td>
<td valign="top">Upstream IED</td>
<td valign="top">Substation Computer Device</td>
<td valign="top">Switch State</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"></a></td>
</tr>
</tbody>
</table>
<p>Source:EPRI</p>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/transmission/wide-area-monitoring-and-control-%e2%80%93-automated-control-functions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Substation Automation Data Acquisition and Control Functions</title>
		<link>http://www.smartgridsblog.com/substation/substation-automation-data-acquisition-and-control-functions/</link>
		<comments>http://www.smartgridsblog.com/substation/substation-automation-data-acquisition-and-control-functions/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 03:12:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Substation]]></category>
		<category><![CDATA[IED]]></category>
		<category><![CDATA[RTU]]></category>
		<category><![CDATA[SCADA]]></category>
		<category><![CDATA[Substation Automation]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/?p=1167</guid>
		<description><![CDATA[Table of Contents

Sampling, Sensing, and Control: e.g. PT and CT Sampling, Fault indicator sensing, LTC Raise/Lower controls, and Protection Trip Signal
Protection IED Interactions: e.g. interactions among protection IED to determine whether to trip, and which equipment to trip
Substation Master System: e.g. Substation system that manages the IEDs within the substation, ranging from simple data concentrators, <a href="http://www.smartgridsblog.com/substation/substation-automation-data-acquisition-and-control-functions/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[<!--CusAds1--><h2>Table of Contents</h2>
<ul>
<li>Sampling, Sensing, and Control: e.g. PT and CT Sampling, Fault indicator sensing, LTC Raise/Lower controls, and Protection Trip Signal</li>
<li>Protection IED Interactions: e.g. interactions among protection IED to determine whether to trip, and which equipment to trip</li>
<li>Substation Master System: e.g. Substation system that manages the IEDs within the substation, ranging from simple data concentrators, RTUs, to sophisticated master stations for managing substation automation functions</li>
<li>DER Management Systems Monitoring and Control of DER Devices: e.g. managing Distributed Energy Resources in a substation or at an industrial customer site</li>
<li>SCADA Systems within Control Centers for Monitoring and Control of Field Equipment: e.g. Control center SCADA system used to monitor substation data, and issue controls to substation equipment</li>
</ul>
<h2>Overview</h2>
<p><strong>Scope</strong>: The Data Acquisition and Control (DAC) functions of Substation Automation, used in transmission and distribution operations, comprise multiple types of mechanisms for data retrieval from field equipment and the issuing of control commands to power system equipment in the field, including among field devices, between field devices and systems located in substations, and between field devices and various systems (including, but not limited to, SCADA systems) located in DER and utility control centers and engineering/planning centers.</p>
<p><strong>Objectives:</strong> The DAC function provides real-time data, statistical data, and other calculated and informational data from the power system to systems and applications that use the data. The DAC function also supports the issuing of control commands to power system equipment and the setting of parameters in IEDs and other field systems.</p>
<p><strong>Rationale:</strong> Power system real-time data is source of most information required for power system operations. Control over the power system equipment can be achieved by issuing control commands and setting parameters.</p>
<p>The Data Acquisition and Control (DAC) function, used in transmission and distribution operations, comprises multiple types of mechanisms for data retrieval and issuing of control commands to power system equipment. These mechanisms are often used in conjunction with each other to provide the full range of DAC interactions. The DAC function, in turn, is used by other functions, such as Supervisory Control and Data Acquisition (SCADA) systems, Energy Management Systems (EMS), Protection Engineering systems, and Advanced Distribution Automation (ADA), as the means for their interactions with the power system equipment.</p>
<h2>Substation Environments</h2>
<p>The following drawing illustrates the two main IntelliGrid Environments in a Substation, the Environment between a substation and the control center, and the Environment within a control center. Click on each Environment to see a complete description of the Environment, the requirements that define the Environment, and the recommended standards, technologies, and best practices for that Environment.</p>
<map>
<area shape="rect" coords="507, 18, 682, 68" href="../Environments/Env7_Intra-Control_Center.htm" />
<area shape="rect" coords="509, 97, 682, 133" href="../Environments/Env5_Critical_Operations_DAC.htm" />
<area shape="rect" coords="503, 151, 679, 207" href="../Environments/Env3_Critical_Operations_Intra-Substation.htm" />
<area shape="rect" coords="480, 257, 689, 337" href="../Environments/Env1_Deterministic_Intra-Substation.htm" /></map>
<p>The following figure shows some of the key information flows of data acquired in substations and other field locations (click on picture to enlarge it).</p>
<p><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/images/DAC_UML.jpg" target="_blank"></a></p>
<h2>Sampling, Sensing, and Control of Power System Equipment</h2>
<h3>Narrative</h3>
<p><strong>Sampling and Sensing of Power System Equipment </strong>is performed by CTs, PTs, sensors, Intelligent Electronic Devices (IEDs), Remote Terminal Units (RTUs), or other microprocessor-based controllers. <strong>Control of Power System Equipment </strong>is performed by controllers, IEDs, or RTUs. These control commands are sometimes the result of applications within the IED or controller, and sometimes are passed through from external systems, such as a Substation Master System or a Control Center SCADA system.</p>
<p>The communications links are often very short (a few meters) but can also entail multi-mile links. The communications media typically are copper wires or optical fibers, but can include power line carrier, radio-based media, and possibly other media. Typically, the timing of the sampling, sensing, and control must meet very stringent requirements for rapid response (about 4 milliseconds), high availability, and high security.</p>
<p>They either use internal applications or are instructed by other entities to issue control signals to associated power system equipment. For example:</p>
<ul>
<li>Digital CTs sample the current on a substation bus</li>
<li>Sensors monitor the status of a circuit breaker</li>
<li>A Protection IED issues a trip signal to a circuit breaker</li>
<li>Load Tap Changer IED raises and lowers the transformer tap position according to pre-set algorithms, based on voltage levels sensed by Potential Transformers (PTs).</li>
<li>A circuit breaker IED issues an electro-mechanical or solid-state-based trip signal to a circuit breaker.</li>
<li>A DER IED controller senses status and measurements of a DER generator and its prime mover, and then issues start and stop signals.</li>
</ul>
<h3>Diagram</h3>
<p> </p>
<h3>Steps for Sampling, Sensing, and Control of Power System Equipment</h3>
<p>An IED receives sensor data from a Potential Transformer (PT), or a circuit breaker IED issues a trip signal to a circuit breaker device.</p>
<table border="1" cellspacing="0" cellpadding="0" width="100%">
<thead>
<tr>
<td width="41">#</td>
<td width="98">Event</td>
<td width="98">Name of Process/Activity</td>
<td width="260">Description of<br />
Process/Activity</td>
<td width="99">Information Producer</td>
<td width="99">Information<br />
Receiver</td>
<td width="90">Type of Info Exchanged</td>
<td width="127"> </td>
</tr>
</thead>
<tbody>
<tr>
<td width="41" valign="top">1.1</td>
<td width="98" valign="top">Continuous or very frequent data retrieval</td>
<td width="98" valign="top">Monitor sensors</td>
<td width="260" valign="top">IED performs analog-to-digital and/or digital-to-digital conversions from sensor inputs, retrieving data from its associated power system equipment and from PT and CT sensors.IED then performs basic engineering conversions on the raw data, processes the information, and determines if any subsequent actions are needed based on limit checking and other process results</td>
<td width="99" valign="top">Sensors</td>
<td width="99" valign="top">IED</td>
<td width="90" valign="top">Raw sensor data</td>
<td width="127" valign="top"><strong> </strong></td>
</tr>
<tr>
<td width="41" valign="top">1.2</td>
<td width="98" valign="top">Processed data indicates further local action needed</td>
<td width="98" valign="top">Send control commands</td>
<td width="260" valign="top">IED issues control commands to power system equipment, based on the results of processing the input data from the field</td>
<td width="99" valign="top">IED</td>
<td width="99" valign="top">Other IEDs or power system equipment, such as circuit breakers, voltage regulators, capacitor bank switches, LTCs, reclosers, etc</td>
<td width="90" valign="top">Signal data</td>
<td width="127" valign="top"><strong> </strong></td>
</tr>
</tbody>
</table>
<p> </p>
<h2>Protection IED Interactions</h2>
<h3>Narrative</h3>
<p><strong>Protection IED Interactions </strong>are undertaken to respond to a relatively local situation within a substation or on a feeder that requires the exchange of information among two or more IEDs, specifically to determine whether to issue a trip signal, and which equipment should be tripped.</p>
<p>The communications media are normally point-to-point cables, LANs (in automated substations), and point-to-multi-point radio channels (on feeders). Transmission protection actions require very high speed communication channels, with response timeframes of 1 to 4 milliseconds, while distribution protection actions involving automated switches could tolerate longer response times. For example:</p>
<ul>
<li>A protection IED issues a trip command over a Process Bus LAN to a circuit breaker IED within a substation, based on its detection of different power system measurements, such as low frequency, current overload, etc.</li>
<li>Multiple automated switch IEDs, using point-to-multi-point spread spectrum radio communications media, respond to a fault condition on a feeder segment by opening and closing switches to isolate the fault and restore power to unaffected feeder segments.</li>
</ul>
<h3>Diagram</h3>
<p> </p>
<h3>Steps for Protection IED Interactions</h3>
<p>A protection IED issues a trip command over a Deterministic Rapid Response LAN to a circuit breaker IED within a substation, based on its detection of different power system measurements, such as low frequency, current overload, etc.</p>
<table border="1" cellspacing="0" cellpadding="0" width="100%">
<thead>
<tr>
<td width="41">#</td>
<td width="98">Event</td>
<td width="98">Name of Process/Activity</td>
<td width="230">Description of<br />
Process/Activity</td>
<td width="99">Information Producer</td>
<td width="99">Information<br />
Receiver</td>
<td width="90">Type of Info Exchanged</td>
<td width="127"> </td>
</tr>
</thead>
<tbody>
<tr>
<td width="41" valign="top">2.1</td>
<td width="98" valign="top">Continuous monitoring</td>
<td width="98" valign="top">Sensor monitoring</td>
<td width="230" valign="top">Each IED in the group monitors local power system equipment</td>
<td width="99" valign="top">Power system equipment</td>
<td width="99" valign="top">IEDs</td>
<td width="90" valign="top">Sensor data</td>
<td width="127" valign="top"><strong> </strong></td>
</tr>
<tr>
<td width="41" valign="top">2.2</td>
<td width="98" valign="top">Fault in a feeder segment occurs</td>
<td width="98" valign="top">Fault detection</td>
<td width="230" valign="top">A fault occurs in a transmission segment. This fault is detected by one or more IEDs, including a protection IED in the substation.</td>
<td width="99" valign="top">Sensor or IED</td>
<td width="99" valign="top">IED</td>
<td width="90" valign="top">Fault sensor data</td>
<td width="127" valign="top"><strong> </strong></td>
</tr>
<tr>
<td width="41" valign="top">2.3</td>
<td width="98" valign="top">Protection IED issues trip command</td>
<td width="98" valign="top">Trip command</td>
<td width="230" valign="top">The protection IED issues a trip command to the breaker IED. Using the mechanisms described in section 2.2.1, the breaker IED issues a trip command to its breaker.</td>
<td width="99" valign="top">Protection IED</td>
<td width="99" valign="top">Equipment</td>
<td width="90" valign="top">Trip command</td>
<td width="127" valign="top"><strong></strong></td>
</tr>
<tr>
<td width="41" valign="top">2.4</td>
<td width="98" valign="top">Recloser trips</td>
<td width="98" valign="top">Monitor response to command</td>
<td width="230" valign="top">The breaker trips and this information is received by automated switch IEDs on the affected feeder.</td>
<td width="99" valign="top">Sensor or IED</td>
<td width="99" valign="top">IED</td>
<td width="90" valign="top">Control response sensor data</td>
<td width="127" valign="top"><strong></strong></td>
</tr>
<tr>
<td width="41" valign="top">2.5</td>
<td width="98" valign="top">IED internal analysis results – multiple iterations</td>
<td width="98" valign="top">Local IED response to fault</td>
<td width="230" valign="top">IEDs near faulted feeder segment communicate and determine which switches should be opened and which closed. This occurs a number of times, depending upon the results of the IED actions, the results of the breaker actions, and the parameter settings in the IEDs. Each IED performs its actions via the 2.2.1 process.</td>
<td width="99" valign="top">One IED</td>
<td width="99" valign="top">Other IEDs</td>
<td width="90" valign="top">Digital electric data</td>
<td width="127" valign="top"><strong></strong></td>
</tr>
</tbody>
</table>
<h3> </h3>
<h2>Substation Master Systems</h2>
<h3>Narrative</h3>
<p><strong>A Substation Master System</strong> is a system within a substation that can:</p>
<ul>
<li>Acquire data from the substation IEDs</li>
<li>Pass selected data to a control center</li>
<li>Receive control commands from the control center</li>
<li>Issue control commands to IEDs and controllers for them to take action</li>
</ul>
<p>Substation Master Systems can be relatively simple or can include sophisticated capabilities. They include data concentrators, Remote Terminal Units (RTUs), as well as more sophisticated Substation Control and Data Acquisition Systems. These are generalized systems, as opposed to IEDs or controllers, and usually monitor and/or control more than one power system device. Data concentrators and RTUs just pass data through them, acting primarily as communication nodes, although they may include a local database. Basic Substation Master Systems may include applications to perform some local interactions, or may help coordinate IED actions. Highly capable Substation Master Systems may include applications that can perform closed loop control (e.g. does not interact with the human operator before issuing a control command).</p>
<p>The communications media can be LANs, copper wire, optical cables, microwave radio, leased telephone lines, cellphones, and many other types. Data exchanges range from a few 10’s of milliseconds up to 1 second. Examples include:</p>
<ul>
<li>Data concentrator in a substation monitors data from IEDs that are located on feeders connected to the substation. It passes some of this data to a SCADA system and passes control commands from the SCADA to the IEDs. It may collect sequence of events data and some statistical information in a database.</li>
<li>Substation master coordinates the protection settings of substation IEDs based on requests from the SCADA system for different response patterns. For instance, different protection trigger levels are set for recloser responses if a storm is pending, or if reconfiguration of a feeder impacts the expected fault current level, or if DER generation levels could cause fuses to blow unnecessarily.</li>
<li>Substation master provides information to automated switch IEDs on a feeder as to the actual configuration of a neighboring feeder. This information will permit the automated switch IEDs to take more appropriate action if a fault occurs.</li>
<li>Substation master performs advanced substation automation functions, by responding to field conditions reported by IEDs and issuing control commands for volt/var optimization, fault location, isolation, and restoration, multi-feeder reconfiguration, etc.</li>
</ul>
<h3>Diagram</h3>
<p> </p>
<h3>Steps for Substation Master Systems</h3>
<p>Substation master systems coordinate the protection settings of substation IEDs based on requests from the SCADA system for different response patterns. For instance, different protection trigger levels are set for zone 3 protection or for recloser responses if a storm is pending, or if reconfiguration of a feeder impacts the expected fault current level, or if DER generation levels could cause fuses to blow unnecessarily.</p>
<table border="1" cellspacing="0" cellpadding="0" width="100%">
<thead>
<tr>
<td width="41">#</td>
<td width="98">Event</td>
<td width="98">Name of Process/Activity</td>
<td width="230">Description of<br />
Process/Activity</td>
<td width="99">Information Producer</td>
<td width="99">Information<br />
Receiver</td>
<td width="90">Type of Info Exchanged</td>
<td width="127"> </td>
</tr>
</thead>
<tbody>
<tr>
<td width="41" valign="top">3.1</td>
<td width="98" valign="top">On-going monitoring of data by substation master</td>
<td width="98" valign="top">Data monitoring</td>
<td width="230" valign="top">Substation master receives digital data from IEDs within a substation and along adjacent feeders. This data can be transmitted periodically or upon significant change of an analog value or upon status change</td>
<td width="99" valign="top">Multiple IEDs</td>
<td width="99" valign="top">Substation master</td>
<td width="90" valign="top">Digital electric data</td>
<td width="127" valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env3_Critical_Operations_Intra-Substation.htm"><strong></strong></a></td>
</tr>
<tr>
<td width="41" valign="top">3.2</td>
<td width="98" valign="top">Request by SCADA to change protection settings</td>
<td width="98" valign="top">Change settings</td>
<td width="230" valign="top">As requested by the control center SCADA system, the substation master determines the appropriate settings for protective relays and reclosers for a specific scenario (e.g. storm, changed feeder configuration)</td>
<td width="99" valign="top">Substation master</td>
<td width="99" valign="top">Protection and recloser IEDs</td>
<td width="90" valign="top">Settings</td>
<td width="127" valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env5_Critical_Operations_DAC.htm"><strong></strong></a></td>
</tr>
<tr>
<td width="41" valign="top">3.3</td>
<td width="98" valign="top">Power system event with IEDs responding</td>
<td width="98" valign="top">Sequence of events recording</td>
<td width="230" valign="top">A power system event occurs, to which the local IEDs respond. They then report their sequence of events to the substation master for inclusion with disturbance records.</td>
<td width="99" valign="top">IEDs</td>
<td width="99" valign="top">Substation master</td>
<td width="90" valign="top">IED SOE</td>
<td width="127" valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env5_Critical_Operations_DAC.htm"><strong></strong></a></td>
</tr>
<tr>
<td width="41" valign="top">3.4</td>
<td width="98" valign="top">Operator initiates trip of breaker</td>
<td width="98" valign="top">Select before operate (SBO) command</td>
<td width="230" valign="top">The substation master ensures that a control request from the control center is authorized, then passes the request to the circuit breaker IED for execution</td>
<td width="99" valign="top">Substation master</td>
<td width="99" valign="top">Circuit breaker IED</td>
<td width="90" valign="top">SBO control request</td>
<td width="127" valign="top"><strong></strong></td>
</tr>
</tbody>
</table>
<p> </p>
<h2>DER Management Systems Monitoring and Control of DER Devices</h2>
<h3>Narrative</h3>
<p><strong>DER management systems </strong>perform monitoring and control of a DER device, either at a customer site or within a substation or from a utility&#8217;s distribution control center (see Figure 1‑1). The DER management system could be a DER owner’s SCADA system, a customer’s Building Automation System (BAS), an energy aggregator’s system, or a distribution operations SCADA system. Communications media can include virtually any type, so long as response times of a few seconds can be accommodated. Examples include:</p>
<ul>
<li>Loss of power is detected at a customer site. The backup diesel generator starts up, the automatic transfer switch connecting the customer to the utility EPS opens, and the generator is connected to the customer’s local EPS (or just the critical equipment).</li>
<li>The owner of the DER device decides to reduce his load on the utility EPS by increasing generation. The DER operator implements this decision by setting new parameters in the DER management system. (These are manual actions by persons.) As an automated result, another generator is started by the DER management system, synchronized with the local EPS, and interconnected.</li>
<li>An energy aggregator sets groups of DER devices to cycle on and off over the next day, taking into account pollution limits, the real-time price of energy, and contractual arrangements with the owners of the DER devices.</li>
<li>While a DER device is interconnected with the utility EPS, a fault occurs on the feeder. The DER management system ensures that the DER device either trips off or the interconnection circuit breaker opens.</li>
<li>The DER management system collects sequence-of-events, performance data, and statistical information from DER devices in a substation.</li>
</ul>
<h3>Diagram</h3>
<p> </p>
<p>Figure DER Management Systems Monitoring and Control of DER Devices</p>
<h3>Steps for DER Management System Monitoring and Control of DER Devices</h3>
<p>The owner of the DER device decides to reduce his load on the utility EPS by increasing generation. The DER operator implements this decision by setting new parameters in the DER management system. (These are manual actions by persons.) As an automated result, another generator is started by the DER management system, synchronized with the local EPS, and interconnected.</p>
<table border="1" cellspacing="0" cellpadding="0" width="100%">
<thead>
<tr>
<td width="41">#</td>
<td width="98">Event</td>
<td width="98">Name of Process/Activity</td>
<td width="230">Description of<br />
Process/Activity</td>
<td width="99">Information Producer</td>
<td width="99">Information<br />
Receiver</td>
<td width="90">Type of Info Exchanged</td>
<td width="127"> </td>
</tr>
</thead>
<tbody>
<tr>
<td width="41" valign="top">4.1</td>
<td width="98" valign="top">DER owner decides to reduce load</td>
<td width="98" valign="top">Owner decision</td>
<td width="230" valign="top">DER owner contacts (calls, e-mails, alarms) DER Operator that additional energy from DER generation is needed.</td>
<td width="99" valign="top">DER owner</td>
<td width="99" valign="top">DER Operator</td>
<td width="90" valign="top">Call by person</td>
<td width="127" valign="top"> </td>
</tr>
<tr>
<td width="41" valign="top">4.2</td>
<td width="98" valign="top">DER operator enters new parameters</td>
<td width="98" valign="top">Establish parameters</td>
<td width="230" valign="top">DER Operator sets new parameters for DER generation output in the DER management system.</td>
<td width="99" valign="top">DER Operator</td>
<td width="99" valign="top">DER Management system</td>
<td width="90" valign="top">DER data entry</td>
<td width="127" valign="top"> </td>
</tr>
<tr>
<td width="41" valign="top">4.3</td>
<td width="98" valign="top">Start command</td>
<td width="98" valign="top">Start DER</td>
<td width="230" valign="top">DER management system issues start command to a DER unit.</td>
<td width="99" valign="top">DER management system</td>
<td width="99" valign="top">DER unit</td>
<td width="90" valign="top">DER start-up command</td>
<td width="127" valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env15_DER_Monitoring_and_Control.htm"></a></td>
</tr>
<tr>
<td width="41" valign="top">4.4</td>
<td width="98" valign="top">DER Unit started</td>
<td width="98" valign="top">Synchronization</td>
<td width="230" valign="top">DER Unit starts and synchronizes with the Local EPS, and reports success and current operating measurements to DER management system</td>
<td width="99" valign="top">DER unit</td>
<td width="99" valign="top">DER management system</td>
<td width="90" valign="top">DER reporting</td>
<td width="127" valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env15_DER_Monitoring_and_Control.htm"></a></td>
</tr>
<tr>
<td width="41" valign="top">4.5</td>
<td width="98" valign="top">On-going DER unit operations</td>
<td width="98" valign="top">Monitoring DER</td>
<td width="230" valign="top">DER unit reports current operating measurements to DER management system for operational information as well as historical and statistical information</td>
<td width="99" valign="top">DER unit</td>
<td width="99" valign="top">DER management system</td>
<td width="90" valign="top">DER historical and statistical records</td>
<td width="127" valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env15_DER_Monitoring_and_Control.htm"></a></td>
</tr>
<tr>
<td width="41" valign="top">4.6</td>
<td width="98" valign="top">Environmental limit reached</td>
<td width="98" valign="top">Environmental limit</td>
<td width="230" valign="top">DER management system calculates that a diesel generator has reached its daily (assigned) limit of emissions, and issues a stop command</td>
<td width="99" valign="top">DER management system</td>
<td width="99" valign="top">DER unit</td>
<td width="90" valign="top">DER stop command</td>
<td width="127" valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env15_DER_Monitoring_and_Control.htm"></a></td>
</tr>
<tr>
<td width="41" valign="top">4.7</td>
<td width="98" valign="top">DER unit stops</td>
<td width="98" valign="top">Stop DER</td>
<td width="230" valign="top">DER unit stops and shuts down. It reports back to the DER management system with its latest data</td>
<td width="99" valign="top">DER unit</td>
<td width="99" valign="top">DER management system</td>
<td width="90" valign="top">DER reporting</td>
<td width="127" valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env15_DER_Monitoring_and_Control.htm"></a></td>
</tr>
<tr>
<td width="41" valign="top">4.8</td>
<td width="98" valign="top">DER unit reports received</td>
<td width="98" valign="top">DER reports</td>
<td width="230" valign="top">DER management system provides DER unit data to DER operator via a User Interface</td>
<td width="99" valign="top">DER management system</td>
<td width="99" valign="top">DER operator</td>
<td width="90" valign="top">User display</td>
<td width="127" valign="top"> </td>
</tr>
</tbody>
</table>
<p> </p>
<h3>Control Center SCADA Systems Monitoring and Control of Field Equipment and IEDs</h3>
<h3>Narrative</h3>
<p><strong>SCADA systems </strong>perform remote monitoring and control of field equipment and IEDs. The term “SCADA” is used here to imply any centralized system which retrieves data from remote sites and may issue control commands when authorized. These SCADA systems are typically located in a utility control center, but may include an engineering “SCADA” system which retrieves protection data or disturbance data, or a maintenance “SCADA” system which monitors the health of both power system and communications equipment.</p>
<p>SCADA system monitoring can use communication channels directly to IEDs, via Remote Terminal Units (RTUs), through a data concentrator, through a substation master, or through a DER management system. The communications media can include virtually any type, so long as response times of 1 second can be accommodated. Although typically seen as used only for real-time distribution operations, the data acquired by the SCADA system can be used by many different systems, applications, and personnel in the control center. This Use Case is limited to the monitoring and control function by SCADA systems; other Use Cases (e.g. ADA Use Case) describe their interactions with the SCADA systems.</p>
<p>SCADA system monitoring and control examples include:</p>
<ul>
<li>Power system operations SCADA system receives real-time data from power system equipment via:</li>
</ul>
<p>–    RTUs</p>
<p>–    IEDs inside substations</p>
<p>–    IEDs along feeders</p>
<p>–    Substation masters</p>
<p>–    DER (or other generation) management systems</p>
<p>–    Other control centers</p>
<p>–    Manual entry</p>
<ul>
<li>Power system operations SCADA system issues control commands to power system equipment in real-time via:</li>
</ul>
<p>–    RTUs</p>
<p>–    IEDs inside substations</p>
<p>–    IEDs along feeders</p>
<p>–    Substation masters</p>
<p>–    DER (or other generation) management systems</p>
<p>–    Other control centers (if authorized)</p>
<ul>
<li>Power system operations SCADA system receives metering information</li>
<li>Data management “SCADA” system receives power equipment configuration data from devices. It may have its own communication channels to the remote sites, or it may acquire this data through the distribution operations SCADA system</li>
<li>Engineering “SCADA” system receives sequence of events data, oscillographic data (special handling required), historical data, and statistical data. It may have its own communication channels to the remote sites, or it may acquire this data through the distribution operations SCADA system</li>
<li>Maintenance “SCADA” system receives data related to the health of power system equipment and communications equipment. It may have its own communication channels to the remote sites, or it may acquire this data through the distribution operations SCADA system.</li>
<li>Planning “SCADA” system receives data that can be used for statistical analysis of power system measurements: maximums, minimums, averages, trends, profiles, power quality metrics, etc, needed for short and long term planning.</li>
</ul>
<h3>Diagram</h3>
<h3>Steps for Monitoring and Control by SCADA System</h3>
<p>Distribution operations SCADA system monitors and controls power system equipment via a multitude of mechanisms.</p>
<table border="1" cellspacing="0" cellpadding="0" width="100%">
<thead>
<tr>
<td>#</td>
<td>Event</td>
<td>Name of Process/Activity</td>
<td>Description of<br />
Process/Activity</td>
<td>Information Producer</td>
<td>Information<br />
Receiver</td>
<td>Type of Info Exchanged</td>
<td> </td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top">5.1</td>
<td valign="top">Establish an association between SCADA and RTU and/or IED</td>
<td valign="top">Establish association</td>
<td valign="top">Using an interactive process between an RTU or IED and a SCADA system, an association is established. This interactive process varies from protocol to protocol, but essentially entails setting up what data is available and what data is to be sent under what conditions. In some protocols, many of the steps are manual, while in others they are almost entirely automatic.</td>
<td valign="top">SCADA and RTU/IED</td>
<td valign="top">RTU/IED and SCADA</td>
<td valign="top">Association</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env5_Critical_Operations_DAC.htm"><strong></strong></a></td>
</tr>
<tr>
<td valign="top">5.2</td>
<td valign="top">Status change occurs in power equipment</td>
<td valign="top">Detect status change</td>
<td valign="top">A status change occurs in some power system equipment. This status change is “immediately” sent (usually within 1 second) to the SCADA system.  Depending upon the communication “services”, the status value can be sent periodically, or can use the “report-by-exception” service, which sends a status value only if it changes</td>
<td valign="top">IED which is sensing power system equipment</td>
<td valign="top">SCADA system</td>
<td valign="top">Status change</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env5_Critical_Operations_DAC.htm"><strong></strong></a></td>
</tr>
<tr>
<td valign="top">5.3</td>
<td valign="top">“Significant” change in a measurement value</td>
<td valign="top">Detect significant measurement change</td>
<td valign="top">A significant change occurs in a measured value. (Significant implies it exceeds some pre-established limit.) This changed value is sent according to pre-established protocol services: e.g. <em>report-by-exception</em> sends it immediately (within 1 to 2 seconds), while <em>periodically</em> sends it when the time period elapses.The protocol also determines what information is included, such as timestamp, quality code, etc.</td>
<td valign="top">RTU which is sensing power system equipment</td>
<td valign="top">SCADA system</td>
<td valign="top">Measurement change</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env5_Critical_Operations_DAC.htm"><strong></strong></a></td>
</tr>
<tr>
<td valign="top">5.4</td>
<td valign="top">SCADA issues control command</td>
<td valign="top">Issue control command</td>
<td valign="top">Either an operator or an application issues a control command through the SCADA system to an RTU or IED. These control commands are typically immediately implemented by sending a signal to the power system equipment</td>
<td valign="top">SCADA</td>
<td valign="top">RTU or IED which initiates signals to power system equipment</td>
<td valign="top">Control command</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env5_Critical_Operations_DAC.htm"><strong></strong></a></td>
</tr>
<tr>
<td valign="top">5.5</td>
<td valign="top">SCADA sends parameter settings</td>
<td valign="top">Set parameters</td>
<td valign="top">Either an operator or an application sends a parameter setting through the SCADA system to an RTU or IED. These parameter settings may be stored for later use or may be used immediately to initiate a signal to the power system equipment, such as a raise or lower control command</td>
<td valign="top">SCADA</td>
<td valign="top">RTU or IED</td>
<td valign="top">Parameter setting</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env5_Critical_Operations_DAC.htm"><strong></strong></a></td>
</tr>
<tr>
<td valign="top">5.6</td>
<td valign="top">SCADA requests specific data</td>
<td valign="top">Request data</td>
<td valign="top">Either an operator or an application requests specific data to be sent to the SCADA system from an RTU or IED.</td>
<td valign="top">SCADA</td>
<td valign="top">RTU or IED</td>
<td valign="top">Request</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env5_Critical_Operations_DAC.htm"><strong></strong></a></td>
</tr>
<tr>
<td valign="top">5.7</td>
<td valign="top">Sequence of Events log</td>
<td valign="top">Transmit sequence of events records</td>
<td valign="top">An RTU or IED has collected Sequence of Events log and initiates its transmittal to the SCADA system</td>
<td valign="top">RTU or IED</td>
<td valign="top">SCADA</td>
<td valign="top">SCADA SOE</td>
<td valign="top"><a href="http://intelligrid.ipower.com/IntelliGrid_Architecture/Environments/Env5_Critical_Operations_DAC.htm"><strong></strong></a></td>
</tr>
</tbody>
</table>
<p> Source: EPRI</p>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/substation/substation-automation-data-acquisition-and-control-functions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Power automation requires a complicated and sophisticated architecture</title>
		<link>http://www.smartgridsblog.com/substation/power-automation-requires-a-complicated-and-sophisticated-architecture/</link>
		<comments>http://www.smartgridsblog.com/substation/power-automation-requires-a-complicated-and-sophisticated-architecture/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 02:56:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Substation]]></category>
		<category><![CDATA[Fault Recording]]></category>
		<category><![CDATA[Gateways]]></category>
		<category><![CDATA[IEC 61850]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/?p=1164</guid>
		<description><![CDATA[


Power automation requires a complicated and sophisticated architecture. As a result, system integrators and software developers need optimal solutions that can withstand tough conditions. These solutions require powerful controllers with multiple serial ports for legacy device connection. They must also perform front-end tasks, such as data acquisition, numerical computing, data distribution, and remote device monitoring <a href="http://www.smartgridsblog.com/substation/power-automation-requires-a-complicated-and-sophisticated-architecture/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[<!--CusAds1--><table border="0" cellspacing="0" cellpadding="0" width="100%" align="center">
<tbody>
<tr>
<td colspan="2">Power automation requires a complicated and sophisticated architecture. As a result, system integrators and software developers need optimal solutions that can withstand tough conditions. These solutions require powerful controllers with multiple serial ports for legacy device connection. They must also perform front-end tasks, such as data acquisition, numerical computing, data distribution, and remote device monitoring and management. Network redundancy is also essential to ensure the continuous system operation of power automation applications. In addition, the effects of extreme temperature fluctuations must be overcome to maintain system stability.</td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr><a id="PowerPlant" name="PowerPlant"></a>Power Plant</tr>
<tr>
<td colspan="2" height="4"> </td>
</tr>
<tr>
<td colspan="2">The DA-681 and DA-662-I embedded computers are communication and protocol gateways that handle multiple devices running different protocols for front-end data computing and protocol conversion.</td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td align="right"><img src="http://www.moxa.com/Event/Sys/2009/IEC_61850-3/images/Application/PowerPlant-D.jpg" alt="" width="600" height="394" />

<!-- Quick Adsense Wordpress Plugin: http://techmilieu.com/quick-adsense -->
<div style="float:left;margin:10px 10px 10px 0;">
<script type="text/javascript"><!--
google_ad_client = "pub-4979295129832072";
/* 336x280图片, 创建于 10-1-14 */
google_ad_slot = "5113627842";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
</div>

</td>
<td width="130" align="left" valign="bottom"><a onmouseover="MM_swapImage('999','','http://www.moxa.com/Event/Sys/2009/IEC_61850-3/images/Application/TOP-icon-Off.jpg',1)" onmouseout="MM_swapImgRestore()" href="#PowerAutomation"><img id="Image21" src="http://www.moxa.com/Event/Sys/2009/IEC_61850-3/images/Application/TOP-icon-On.jpg" border="0" alt="" width="133" height="34" /></a></td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr><a id="Substation" name="Substation"></a>IEC 61850-3 Substation</tr>
<tr>
<td colspan="2" height="4"> </td>
</tr>
<tr>
<td colspan="2">The DA-681 is an embedded computer that serves as a communication processor and uses gateway protocol to handle multiple devices, which use different protocols for front-end data computing and protocol conversions. With IEC 61850-3 certification, the DA-681 is capable of providing protection against electrical surges, EMI, and other environmental threats. The DA-681 can also serve as a backend communication host and central controller for data analysis, processing, and transmission back to the control center.</td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td align="right"><img src="http://www.moxa.com/Event/Sys/2009/IEC_61850-3/images/Application/Substation-D.jpg" alt="" width="600" height="394" /></td>
<td width="130" align="left" valign="bottom"><a onmouseover="MM_swapImage('999','','images/Application/TOP-icon-Off.jpg',1)" onmouseout="MM_swapImgRestore()" href="#PowerAutomation"><img id="Image21" src="http://www.moxa.com/Event/Sys/2009/IEC_61850-3/images/Application/TOP-icon-On.jpg" border="0" alt="" width="133" height="34" /></a></td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr><a id="FaultRecording" name="FaultRecording"></a>Fault Recording</tr>
<tr>
<td colspan="2" height="4"> </td>
</tr>
<tr>
<td colspan="2">The DA-660 series communication embedded computers provide uninterrupted communication for data recovery. In the event of an accident, users can still retrieve their records, which are safely stored on the DA-660 computer. In addition, the DA-660 series also serves as a protocol converter.</td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td align="right"><img src="http://www.moxa.com/Event/Sys/2009/IEC_61850-3/images/Application/Fault-D.jpg" alt="" width="600" height="394" /></td>
<td align="left" valign="bottom"><a onmouseover="MM_swapImage('999','','http://www.moxa.com/Event/Sys/2009/IEC_61850-3/images/Application/TOP-icon-Off.jpg',1)" onmouseout="MM_swapImgRestore()" href="#PowerAutomation"><img id="Image21" src="http://www.moxa.com/Event/Sys/2009/IEC_61850-3/images/Application/TOP-icon-On.jpg" border="0" alt="" width="133" height="34" /></a></td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr><a id="AMR" name="AMR"></a>Automatic Meter Reading</tr>
<tr>
<td colspan="2" height="4"> </td>
</tr>
<tr>
<td colspan="2">The W325, IA240 series, and IA260 series embedded computers store metering data, convert it from proprietary protocols to the standard protocols used by the automation system, perform front-end computing, and then transmit the data to central servers wirelessly.</td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td align="right"><img src="http://www.moxa.com/Event/Sys/2009/IEC_61850-3/images/Application/AMR-D.jpg" alt="" width="600" height="369" /></td>
</tr>
</tbody>
</table>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/substation/power-automation-requires-a-complicated-and-sophisticated-architecture/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The evolution of substation communications</title>
		<link>http://www.smartgridsblog.com/substation/the-evolution-of-substation-communications-2/</link>
		<comments>http://www.smartgridsblog.com/substation/the-evolution-of-substation-communications-2/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 02:44:25 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Substation]]></category>
		<category><![CDATA[IEC 61850]]></category>
		<category><![CDATA[IED]]></category>
		<category><![CDATA[Substation Automation]]></category>
		<category><![CDATA[UCA 2.0]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/?p=1161</guid>
		<description><![CDATA[







Trends in electric utility automation, specifically substation automation, have converged upon a common communications architecture with the goal of having interoperability between a variety of intelligent electronic devices (IEDs) found in the substation. This initiative was begun back in the late 1980s driven by the major North American utilities under the technical auspices of EPRI <a href="http://www.smartgridsblog.com/substation/the-evolution-of-substation-communications-2/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[
<!-- Quick Adsense Wordpress Plugin: http://techmilieu.com/quick-adsense -->
<div style="float:right;margin:10px 0 10px 10px;">
<script type="text/javascript"><!--
google_ad_client = "pub-4979295129832072";
/* 336x280, 创建于 10-1-4 */
google_ad_slot = "6171198131";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
</div>
<p>Trends in electric utility automation, specifically substation automation, have converged upon a common communications architecture with the goal of having interoperability between a variety of intelligent electronic devices (IEDs) found in the substation. This initiative was begun back in the late 1980s driven by the major North American utilities under the technical auspices of EPRI (Electric Power Research Institute). The resulting standard that emerged is known as the Utility Communications Architecture 2.0 (UCA2.0) and is becoming an international standard as IEC61850. This architecture, which is now being adopted worldwide by utilities and IED vendors alike, has as its underlying network technology – Ethernet.</p>
<div><strong>The legacy substation</strong></p>
<p>Prior to this initiative, inter-IED communications (signalling and exchange of information) was typically achieved via a combination of rigid wiring between devices and low speed serial communications. Signalling was often accomplished by having outputs from one IED connected to the inputs of another. This system was by its very nature inflexible and limited in its scope of control. Most sophisticated inter-IED control schemes would require a large number of wiring interconnections between multiple IEDs and thus were not practical. Low-speed serial communications was often limited to master/slave half-duplex arrangements and thus true peer-to-peer communications between IEDs was not feasible.</p>
<div><img src="http://www.instrumentation.co.za/Articles/SA%20Instrumentation%20&amp;%20Control%20-%20Published%20by%20Technews/77c60a.png" alt="Typical legacy substation" />

</div>
<div>Typical legacy substation</div>
<p><strong>The substation LAN</strong></p>
<p>The emergence of the Ethernet-based substation LAN (local area network) has been steadily gaining momentum worldwide. The main benefits of the substation LAN are:</p>
<p><em>* High-speed, peer-to-peer communications between IEDs.</p>
<p>* Reduced inter-IED wiring.</p>
<p>* Coexisting multiple protocols (eg, DNP, Modbus, IEC61850) on the same physical network.</p>
<p>* Enables &#8216;Data over IP&#8217; for easy access to substation data.</em></p>
<div><img src="http://www.instrumentation.co.za/Articles/SA%20Instrumentation%20&amp;%20Control%20-%20Published%20by%20Technews/77c60b.png" alt="Substation LAN" /></div>
<div>Substation LAN</div>
<p>The family of substation hardened Ethernet switches from RuggedSwitch has been designed to implement the substation LAN and to meet the same EMI immunity, performance and reliability requirements and standards as mission-critical protective relaying devices.</p>
<p><strong>The IEC 61850 substation</strong></p>
<p>The IEC 61850 standard view of the substation has two application domains: Station Bus and Process Bus. Station Bus refers to an application domain where relays and RTUs attach to the LAN. Process Bus refers to the domain where devices such as CT/VT Merging Units (MU) provide sampled measured values of current and voltage via the LAN.</p>
<div><img src="http://www.instrumentation.co.za/Articles/SA%20Instrumentation%20&amp;%20Control%20-%20Published%20by%20Technews/77c60c.png" alt="IEC 61850 substation" /></div>
<div>IEC 61850 substation</div>
<p>Brendan Swart of H3iSquared says: &#8220;The RuggedSwitch family of substation hardened Ethernet switches has been created to meet the requirements of IEC 61850 and to implement Station Bus or Process Bus LANs. Specifically, these devices exceed the IEC 61850-3 EMI immunity requirements and the fibre optical network interfaces help provide zero packet loss performance under EMI stress. This is a must if the Station Bus LAN is to be used for tripping or blocking of breakers or if sampled measured values of current and voltage are to be distributed over the Process Bus LAN.</p>
<p>For more information contact H3iSquared, +27 (0)11 454 6025, <a href="mailto:brendan@h3isquared.com">brendan@h3isquared.com</a>, <a href="http://www.h3isquared.com/" target="blank">www.H3iSquared.com</a></div>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/substation/the-evolution-of-substation-communications-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kalki Sub-Station Gateways</title>
		<link>http://www.smartgridsblog.com/substation/kalki-sub-station-gateways/</link>
		<comments>http://www.smartgridsblog.com/substation/kalki-sub-station-gateways/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 02:34:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Substation]]></category>
		<category><![CDATA[Gateways]]></category>
		<category><![CDATA[IEC 60870-5-101]]></category>
		<category><![CDATA[IEC 60870-5-103]]></category>
		<category><![CDATA[IEC 60870-5-104]]></category>
		<category><![CDATA[IEC 61850]]></category>
		<category><![CDATA[Modbus]]></category>
		<category><![CDATA[RTU]]></category>
		<category><![CDATA[UCA 2.0]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/?p=1158</guid>
		<description><![CDATA[KSGL family of protocol hardware are field proven and secure solutions for protocol communication integration and translation requirements for the Power Generation, Transmission &#38; Distribution, Oil &#38; Gas, Industrial Automaton, Utilities, AMR, Remote Monitoring applications. Our products enable you to deploy standards based field-proven utility communication solutions with secure communication options quickly and cost-effectively.
Automation Systems <a href="http://www.smartgridsblog.com/substation/kalki-sub-station-gateways/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[<!--CusAds1--><p><span style="font-family: Arial; color: #333333;">KSGL family of protocol hardware are field proven and secure solutions for protocol communication integration and translation requirements for the Power Generation, Transmission &amp; Distribution, Oil &amp; Gas, Industrial Automaton, Utilities, AMR, Remote Monitoring applications. Our products enable you to deploy standards based field-proven utility communication solutions with secure communication options quickly and cost-effectively.</span></p>
<p>Automation Systems currently need to support new and high speed standards like IEC 61850, IEEE C37.118, DNP3, IEC 104, ICCP and integrate in a secure manner with central control centers, local control centers, remote monitoring stations, data concentration centers, local and national grids and at the same time be able to talk within the local sub-system on standards like IEC 60870-5-103, DNP3, Modbus, SPA, Courier, DLMS/IEC 62056, Ethernet IP, DH+, SEL Protocol, SRTP, GSM, CANOpen and various other proprietary and standard protocols. Kalki Protocol Converters and Gateways provide you with a unique and cost effective solution to achieve your sub-station modernization requirements and utility communication security requirements in a standards based manner.</p>
<p>The KSGL and KPG Platforms support the following functions:</p>
<ul>
<li>CANOpen IO Gateway &#8211; Connect to CANOpen IO&#8217;s and make them available on any standard protocol such as DNP3, IEC 60870-5-101/103/104, IEC 61850 (UCA 2.0), Courier, SPA, Modbus, ICCP and proprietary interfaces.</li>
<li>Protocol Converter &#8211; Convert standard or proprietary device protocols to control center protocols such as DNP3, IEC 60870-5-101/103/104, IEC 61850 (UCA 2.0), Courier, SPA, Modbus etc.,: one-to-one, one-to-many or many-to-many options supported</li>
<li>Data Concentrator &#8211; Collect data from all substation devices, using standard and proprietary protocol, and make it available to control centers and the local HMI, using LAN, WAN, serial connections and GSM/GPRS/PSTN modems on one or two standard protocols. KSGL support&#8217;s up-to 50000 points and the KPG family supports upwards of 250000 points.</li>
<li>Serial Port Pass-Through &#8211; Use the KSGL  to connect to any substation device for settings, remote maintenance, monitoring and control using the IED&#8217;s Proprietary Software. Have native support for Areva S1 and ABB CAP 501 and SMS.</li>
<li>GPRS/GSM/PSTN/RF &#8211; KSGL supports communication over GPRS, GSM, PSTN and Radio for Distribution Automation requirements, including interfacing RMU, Feeder RTU, Transformer Monitoring and similar applications.</li>
<li>Security Adapter &#8211; KSGL product act as a security adapter that support AES, 3DES and SSL Support. This enables two KSGL units to communicate in a secured manner over standard protocols over a public communication networks or similar technologies. KSGL/S can support FIPS 140-2 specifications.</li>
<li>Device Server &#8211; KSGL family of products can also be configured to act as a device server, thereby providing multiple serial ports over its Ethernet. This enables multi-mastering or redundancy configurations across a distributed network with less number of serial ports and also the possibility of connecting proprietary configuration software on these Device Server Ports.</li>
</ul>
<p><strong>Protocol Gateway Models</strong></p>
<table style="height: 111px;" border="1" cellspacing="0" cellpadding="0" width="95%">
<tbody>
<tr>
<td width="47%" height="15" align="center"><strong>Model Name</strong></td>
<td width="15%" height="15" align="center"><strong>Serial Ports</strong></td>
<td width="15%" height="15" align="center"><strong>Ethernet Ports</strong></td>
<td width="61%" height="15" align="center"><strong>Point Support*</strong></td>
</tr>
<tr>
<td width="47%" height="17" align="center">KSGL/S2/R1</td>
<td width="15%" height="17" align="center">2/4/6</td>
<td width="15%" height="17" align="center">1</td>
<td width="61%" height="17" align="center">500-1500</td>
</tr>
<tr>
<td width="47%" height="3" align="center">KSGL/S8/R2</td>
<td width="15%" height="3" align="center" valign="top">8</td>
<td width="15%" height="3" align="center">1</td>
<td width="61%" height="3" align="center">1500-10000</td>
</tr>
<tr>
<td width="47%" height="17" align="center">KSGL/S16/R2**</td>
<td width="15%" height="17" align="center">8/16</td>
<td width="15%" height="17" align="center">2</td>
<td width="61%" height="17" align="center">1500-20000</td>
</tr>
<tr>
<td width="47%" height="21" align="center">KSGL/S16/R4</td>
<td width="15%" height="21" align="center">8/16</td>
<td width="15%" height="21" align="center">4</td>
<td width="61%" height="21" align="center">1000-50000</td>
</tr>
<tr>
<td colspan="4" width="138%" height="21" align="center"><a href="http://www.kalkitech.com/protocolsupport.htm">Click here for more information on protocols supported</a><br />
* Point support will vary from protocol to protocol. The numbers given are indicative only.<br />
** Fiber Ethernet Ports are optionally available</td>
</tr>
</tbody>
</table>
<p>The gateway comes with a EasyConnect Configuration and Diagnostic&#8217;s software. The same can be downloaded from our download site for evaluation. These tools are easy to use and offer both local and remote access to the gateway configuration, security settings, log files, communication traces, and system statistics.</p>
<p>KSGL is an integration platform that can be deployed in your existing sub-stations to connect your existing sub-station IED&#8217;s and relays to newer sub-station control systems, for RMU automation and pole top communications, as data concentration equipment in distribution automation applications, as data concentrators in industrial automation applications, for pipe-line monitoring applications and so on. The KSGL/KPG supports protocols like IEC 61850, IEEE C37.118, IEC 60870-5-101, IEC 60870-5-104, DLMS, IEC 62056, IEC 60870-5-103, UCA 2.0, Modbus RTU, Modbus TCP/IP etc., and also can be configured to support proprietary interfaces like ABB SPA, Alstom Courier and other vendor specific protocols. The sub-station gateway supports expandable serial and Ethernet interfaces to support a multitude of devices to your latest control systems in substation. </p>
<p>If you would like to know more about this product or any other of Kalki&#8217;s products, solutions or services, please e-mail at <a href="mailto:sales@kalkitech.com?subject=Information request on Kalki Products and Solutions">sales@kalkitech.com</a> or submit our <a href="http://www.kalkitech.com/substationgatewayqtn.htm">Quotation Request Form</a></p>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/substation/kalki-sub-station-gateways/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Smart Grid Enabled Mobile Gateways</title>
		<link>http://www.smartgridsblog.com/it_security_communication_network/smart-grid-enabled-mobile-gateways/</link>
		<comments>http://www.smartgridsblog.com/it_security_communication_network/smart-grid-enabled-mobile-gateways/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 02:31:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IT&Security&Communication&Network]]></category>
		<category><![CDATA[DNP3]]></category>
		<category><![CDATA[Gateways]]></category>
		<category><![CDATA[IEC 61850]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/?p=1155</guid>
		<description><![CDATA[KSGL Mobile Gateways comes with support for GSM/GPRS/EDGE/CDMA support, Analog and Digital I/O&#8217;s and upto 6 Serial and 1 Ethernet port all sub-station / EMI/EMC hardened for high availability and high EMI/EMC rugged requirements. Ideal for Smart Grid, APDRP applications with OpenVPN Support and Dynamic IP Support.
Remote monitoring and smart grid applications require extensive remote <a href="http://www.smartgridsblog.com/it_security_communication_network/smart-grid-enabled-mobile-gateways/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[<!--CusAds1--><p><span style="font-family: Arial; color: #333333;">KSGL Mobile Gateways comes with support for GSM/GPRS/EDGE/CDMA support, Analog and Digital I/O&#8217;s and upto 6 Serial and 1 Ethernet port all sub-station / EMI/EMC hardened for high availability and high EMI/EMC rugged requirements. Ideal for Smart Grid, APDRP applications with OpenVPN Support and Dynamic IP Support.</span></p>
<p><span style="color: #333333;">Remote monitoring and smart grid applications require extensive remote monitoring on standards based protocols. Kalkitech Mobile Gateways are ideal for this requirement. With a huge array of power system and metering protocols, together with substation hardened design, they are ideal for AMR/AMI and smart grid applications as well as distribution automation applications. </span> </p>
<p><span style="font-family: Arial; color: #333333;">The KSGL Mobile Platforms consists of the KSGL/S2/R1 product range which have the following features:</span></p>
<ul type="square">
<li><span style="font-family: Arial; color: #333333;">Protocol Converter &#8211; Convert standard or proprietary device protocols to control center protocols such as DNP3, IEC 101/103/104, IEC 61850, Modbus, DLMS, ANSI and many others</span></li>
<li><span style="font-family: Arial; color: #333333;">Data Concentrator &#8211; Collect data from all local devices, using standard and proprietary protocol, and make it available to control centers and the local HMI, using LAN, WAN, serial connections and GSM/GPRS/PSTN modems on one or two standard protocols. </span></li>
<li><span style="font-family: Arial; color: #333333;">Serial Port Pass-Through &#8211; Use the KSGL  to connect to any substation device for settings, remote maintenance, monitoring and control using the devices Proprietary Software.</span></li>
<li><span style="font-family: Arial; color: #333333;">GPRS/GSM/CDMA &#8211; KSGL supports communication over GPRS, GSM, PSTN and Radio for Distribution Automation requirements, including interfacing Meters, RMU, Feeder RTU, Transformer Monitoring and similar applications.</span></li>
<li><span style="font-family: Arial; color: #333333;">Security Adapter &#8211; KSGL product act as a security adapter that support AES, 3DES and SSL Support. This enables two KSGL units to communicate in a secured manner over standard protocols over a public communication networks or similar technologies. KSGL/S can support FIPS 140-2 specifications.</span></li>
</ul>
<p><strong><span style="font-family: Arial; color: #333333;">Gateway Models</span></strong></p>
<table style="height: 111px;" border="1" cellspacing="0" cellpadding="0" width="95%">
<tbody>
<tr>
<td width="33%" height="15" align="center"><span style="font-family: Arial; color: #333333;"><strong>Model Name</strong></span></td>
<td width="14%" height="15" align="center"><span style="font-family: Arial; color: #333333;"><strong>Serial Ports</strong></span></td>
<td width="18%" height="15" align="center"><span style="color: #333333;"><strong>Mobile<br />
Support</strong></span></td>
<td width="18%" height="15" align="center"><span style="font-family: Arial; color: #333333;"><strong>Ethernet Ports</strong></span></td>
<td width="33%" height="15" align="center"><span style="font-family: Arial; color: #333333;"><strong>Point Support*</strong></span></td>
</tr>
<tr>
<td width="33%" height="17" align="center"><span style="font-family: Arial; color: #333333;">KSGL/S2/R1</span></td>
<td width="14%" height="17" align="center"><span style="font-family: Arial; color: #333333;">2</span></td>
<td width="18%" height="17" align="center"><span style="font-family: Arial; color: #333333;">GPRS/ CDMA/ GSM</span></td>
<td width="18%" height="17" align="center"><span style="font-family: Arial; color: #333333;">1</span></td>
<td width="33%" height="17" align="center"><span style="font-family: Arial; color: #333333;">500-5000</span></td>
</tr>
<tr>
<td width="33%" height="3" align="center"><span style="font-family: Arial; color: #333333;">KSGL/S4/R1</span></td>
<td width="14%" height="3" align="center" valign="top"><span style="color: #333333;">4</span></td>
<td width="18%" height="3" align="center"><span style="font-family: Arial; color: #333333;">GPRS/ CDMA/ GSM</span></td>
<td width="18%" height="3" align="center"><span style="font-family: Arial; color: #333333;">1</span></td>
<td width="33%" height="3" align="center"><span style="font-family: Arial; color: #333333;">500-5000</span></td>
</tr>
<tr>
<td width="33%" height="17" align="center"><span style="font-family: Arial; color: #333333;">KSGL/S6/R1</span></td>
<td width="14%" height="17" align="center"><span style="color: #333333;">6</span></td>
<td width="18%" height="17" align="center"><span style="font-family: Arial; color: #333333;">GPRS/ CDMA/ GSM</span></td>
<td width="18%" height="17" align="center"><span style="color: #333333;">1</span></td>
<td width="33%" height="17" align="center"><span style="font-family: Arial; color: #333333;">500-5000</span></td>
</tr>
<tr>
<td colspan="5" width="138%" height="21" align="center"><span style="font-family: Arial; color: #333333;"><a href="http://www.kalkitech.com/protocolsupport.htm">Click here for more information on protocols supported</a></span><br />
<span style="color: #000000; font-size: xx-small;">* Point support will vary from protocol to protocol. The numbers given are indicative only.</span></td>
</tr>
</tbody>
</table>
<p><span style="font-family: Arial; color: #333333;">The gateway comes with a EasyConnect Configuration and Diagnostic&#8217;s software. The same can be downloaded from our download site for evaluation. These tools are easy to use and offer both local and remote access to the gateway configuration, security settings, log files, communication traces, and system statistics.</span></p>
<p><span style="font-family: Arial; color: #333333;">If you would like to know more about this product or any other of Kalki&#8217;s products, solutions or services, please e-mail at <a href="mailto:sales@kalkitech.com?subject=Information request on Kalki Products and Solutions">sales@kalkitech.com</a> or submit our <a href="http://www.kalkitech.com/substationgatewayqtn.htm">Quotation Request Form</a></span></p>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/it_security_communication_network/smart-grid-enabled-mobile-gateways/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Manufacturing Message Specification</title>
		<link>http://www.smartgridsblog.com/it_security_communication_network/manufacturing-message-specification/</link>
		<comments>http://www.smartgridsblog.com/it_security_communication_network/manufacturing-message-specification/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 02:28:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IT&Security&Communication&Network]]></category>
		<category><![CDATA[ASN.1]]></category>
		<category><![CDATA[Ethernet]]></category>
		<category><![CDATA[MMS]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/?p=1152</guid>
		<description><![CDATA[Manufacturing Message Specification (MMS) is an international standard (ISO 9506) dealing with messaging system for transferring real time process data and supervisory control information between networked devices and/or computer applications. The standard is developed and maintained by the ISO Technical Committee 184 (TC184). MMS defines the following

A set of standard objects which must exist in <a href="http://www.smartgridsblog.com/it_security_communication_network/manufacturing-message-specification/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[<!--CusAds1--><p><strong>Manufacturing Message Specification</strong> (MMS) is an international standard (ISO 9506) dealing with messaging system for transferring real time process data and supervisory control information between networked devices and/or computer applications. The standard is developed and maintained by the ISO Technical Committee 184 (TC184). MMS defines the following</p>
<ul>
<li>A set of <em>standard objects</em> which must exist in every device, on which operations like read, write, event signaling etc can be executed. Virtual manufacturing device (VMD) is the main object and all other objects like variables, domains, journals, files etc comes under VMD.</li>
</ul>
<ul>
<li>A set of <em>standard messages</em> exchanged between a client and a server stations for the purpose of monitoring and/or controlling these objects.</li>
</ul>
<ul>
<li>A set of <em>encoding rules</em> for mapping these messages to bits and bytes when transmitted.</li>
</ul>
<h2>MMS original communication stack</h2>
<p>MMS was standardized in 1990 under two separate standards as</p>
<ul>
<li>1. ISO/IEC 9506-1 (2003): Industrial Automation systems &#8211; Manufacturing Message Specification &#8211; Part 1: Service Definition</li>
<li>2. ISO/IEC 9506-2 (2003): Industrial Automation systems &#8211; Manufacturing Message Specification &#8211; Part 2: Protocol Specification</li>
</ul>
<p>This version of MMS used seven layers of OSI network protocols as its communication stack:</p>
<table width="40%">
<tbody>
<tr>
<td>Application</td>
<td><strong>Association Control Service Element ( ACSE )- ISO 8649/8650</strong></td>
</tr>
<tr>
<td>Presentation</td>
<td><strong>Connection Oriented Presentation &#8211; ISO 8822/8823</strong><strong>Abstract Syntax Notation (ASN)- ISO 8824/8825</strong></td>
</tr>
<tr>
<td>Session</td>
<td><strong>Connection Oriented Session &#8211; ISO 8326/8327</strong></td>
</tr>
<tr>
<td>Transport</td>
<td><strong>Connection Oriented Transport &#8211; ISO 8072/8073</strong></td>
</tr>
<tr>
<td>Network</td>
<td><strong>Connectionless network &#8211; ISO 8348</strong></td>
</tr>
<tr>
<td>Link</td>
<td><strong>MAC &#8211; ISO 8802-3 [Ethernet]</strong><strong>MAC &#8211; ISO 8802-4 [Token Ring]</strong></td>
</tr>
<tr>
<td>Physical</td>
<td><strong>Ethernet</strong><strong>Token Ring</strong></td>
</tr>
</tbody>
</table>
<h2>MMS stack over TCP/IP</h2>
<p>Because the Open Systems Interconnection protocols are challenging to implement, the original MMS stack never became popular. In 1999, Boeing created a new version of MMS using Internet protocols instead of the bottom four layers of the original stack plus RFC 1006 (&#8220;ISO Transport over TCP&#8221;) in the Transport layer. The top three layers use the same OSI protocols as before.</p>
<p>In terms of the seven-layer OSI model, the new MMS stack looks like this:</p>
<table width="40%">
<tbody>
<tr>
<td>Application</td>
<td><strong>Association Control Service Element ( ACSE )- ISO 8649/8650</strong></td>
</tr>
<tr>
<td>Presentation</td>
<td><strong>Connection Oriented Presentation &#8211; ISO 8822/8823</strong><strong>Abstract Syntax Notation (ASN)- ISO 8824/8825</strong></td>
</tr>
<tr>
<td>Session</td>
<td><strong>Connection Oriented Session &#8211; ISO 8326/8327</strong></td>
</tr>
<tr>
<td>Transport</td>
<td><strong>ISO transport over TCP &#8211; RFC 1006</strong><strong>Transmission Control Protocol (TCP) &#8211; RFC 793</strong></td>
</tr>
<tr>
<td>Network</td>
<td><strong>Internet Control Message Protocol (ICMP) &#8211; RFC 792</strong><strong>Internet Protocol (IP)- RFC 791</strong></p>
<p><strong>Address Resolution Protocol (ARP)- RFC 826</strong></td>
</tr>
<tr>
<td>Link</td>
<td><strong>IP datagrams over Ethernet &#8211; RFC 894</strong><strong>MAC &#8211; ISO 8802-3 [Ethernet]</strong></td>
</tr>
<tr>
<td>Physical</td>
<td><strong>Ethernet</strong></td>
</tr>
</tbody>
</table>
<p>With the new stack, MMS has become a globally accepted standard.<sup title="This claim needs references to reliable sources from September 2009">[<em>citation needed</em>]</sup></p>
<h2>External links</h2>
<ul>
<li>MMS Overview</li>
<li>MMS Protocol Stack and test tools</li>
<li>Protocol gateways for MMS based protocols</li>
</ul>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/it_security_communication_network/manufacturing-message-specification/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A concise introduction to the IEC 61850 standard</title>
		<link>http://www.smartgridsblog.com/standards/a-concise-introduction-to-the-iec-61850-standard/</link>
		<comments>http://www.smartgridsblog.com/standards/a-concise-introduction-to-the-iec-61850-standard/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 02:23:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Standards]]></category>
		<category><![CDATA[IEC 61850]]></category>
		<category><![CDATA[MMS]]></category>
		<category><![CDATA[SCL]]></category>

		<guid isPermaLink="false">http://www.smartgridsblog.com/?p=1149</guid>
		<description><![CDATA[








Contents


1 Standard Documents
2 History
3 IEC 61850 Features
4 IEC 61850 &#8211; Related Developments
5 See also
6 References
7 External links









IEC 61850[1] is a standard for the design of electrical substation automation. IEC 61850 is a part of the International Electrotechnical Commission&#8217;s (IEC) Technical Committee 57 (TC57)[2] reference architecture for electric power systems. The abstract data models defined in <a href="http://www.smartgridsblog.com/standards/a-concise-introduction-to-the-iec-61850-standard/" class="more-link">More &#62;</a>]]></description>
			<content:encoded><![CDATA[<!--CusAds1--><table cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>
<table id="toc">
<tbody>
<tr>
<td>
<div id="toctitle">
<h2>Contents</h2>
</div>
<ul>
<li>1 Standard Documents</li>
<li>2 History</li>
<li>3 IEC 61850 Features</li>
<li>4 IEC 61850 &#8211; Related Developments</li>
<li>5 See also</li>
<li>6 References</li>
<li>7 External links</li>
</ul>
</td>
</tr>
</tbody>
</table>
<p><script type="text/javascript"></script></td>
</tr>
</tbody>
</table>
<p><strong>IEC 61850</strong><sup id="cite_ref-0">[1]</sup> is a standard for the design of electrical substation automation. IEC 61850 is a part of the International Electrotechnical Commission&#8217;s (IEC) Technical Committee 57 (TC57)<sup id="cite_ref-1">[2]</sup> reference architecture for electric power systems. The abstract data models defined in IEC 61850 can be mapped to a number of protocols. Current mappings in the standard are to MMS (Manufacturing Message Specification), GOOSE, SMV, and soon to Web Services. These protocols can run over TCP/IP networks and/or substation LANs using high speed switched Ethernet to obtain the necessary response times of &lt; 4 ms for protective relaying.</p>
<h2>Standard Documents</h2>
<p>IEC 61850 consists of the following parts detailed in separate IEC 61850 standard documents</p>
<ul>
<li>IEC 61850-1: Introduction and overview</li>
<li>IEC 61850-2: Glossary</li>
<li>IEC 61850-3: General requirements</li>
<li>IEC 61850-4: System and project management</li>
<li>IEC 61850-5: Communication requirements for functions and device models</li>
<li>IEC 61850-6: Configuration description language for communication in electrical substations related to IEDs</li>
<li>IEC 61850-7: Basic communication structure for substation and feeder equipment
<ul>
<li>IEC 61850-7-1: Principles and models</li>
<li>IEC 61850-7-2: Abstract communication service interface (ACSI)</li>
<li>IEC 61850-7-3: Common Data Classes</li>
<li>IEC 61850-7-4: Compatible logical node classes and data classes</li>
</ul>
</li>
<li>IEC 61850-8: Specific communication service mapping (SCSM)
<ul>
<li>IEC 61850-8-1: Mappings to MMS (ISO/IEC9506-1 and ISO/IEC 9506-2)</li>
</ul>
</li>
<li>IEC 61850-9: Specific communication service mapping (SCSM)
<ul>
<li>IEC 61850-9-1: Sampled values over serial unidirectional multidrop point to point link</li>
<li>IEC 61850-9-2: Sampled values over ISO/IEC 8802-3</li>
</ul>
</li>
<li>IEC 61850-10: Conformance testing</li>
</ul>
<h2>History</h2>
<p>Multiple protocols exist for substation automation, which include many proprietary protocols with custom communication links. Interoperation of devices from different vendors would be an advantage to users of substation automation devices. An IEC project group of about 60 members from different countries worked in three IEC working groups from 1995. They responded to all the concerns and objectives and created IEC 61850. The objectives set for the standard were:</p>
<ol>
<li>A single protocol for complete substation considering modeling of different data required for substation.</li>
<li>Definition of basic services required to transfer data so that the entire mapping to communication protocol can be made future proof.</li>
<li>Promotion of high interoperability between systems from different vendors.</li>
<li>A common method/format for storing complete data.</li>
<li>Define complete testing required for the equipments which confirms to the standard.</li>
</ol>
<h2>IEC 61850 Features</h2>
<p>IEC 61850 features include:</p>
<ol>
<li><em>Data Modeling</em> &#8212; Primary process objects as well as protection and control functionality in the substation is modelled into different standard logical nodes which can be grouped under different logical devices. There are logical nodes for data/functions related to the logical device (<em>LLN0</em>) and physical device (<em>LPHD</em>).</li>
<li><em>Reporting Schemes</em> &#8212; There are various reporting schemes (<em>BRCB &amp; URCB</em>) for reporting data from server through a server-client relationship which can be triggered based on pre-defined trigger conditions.</li>
<li><em>Fast Transfer of events</em> &#8212; Generic Substation Event (<em>GSE</em>) are defined for fast transfer of event data for a peer-to-peer communication mode. This is again subdivided into <em>GOOSE</em> &amp; <em>GSSE</em>.</li>
<li><em>Setting Groups</em> &#8212; The setting group control Blocks (<em>SGCB</em>) are defined to handle the setting groups so that user can switch to any active group according to the requirement.</li>
<li><em>Sampled Data Transfer</em> &#8212; Schemes are also defined to handle transfer of sampled values using Sampled Value Control blocks (<em>SVCB</em>)</li>
<li><em>Commands</em> &#8212; Various command types are also supported by IEC 61850 which include direct &amp; select before operate (SBO) commands with normal and enhanced securities.</li>
<li><em>Data Storage</em>&#8211; SCL(Substation Configuration Language) is defined for complete storage of configured data of the substation in a specific format.</li>
</ol>
<h2>IEC 61850 &#8211; Related Developments</h2>
<ul>
<li>IEC 61850-7-410 &#8212; IEC 61850-7-410 Ed.1 Communication networks and systems for power utility automation &#8211; Part 7-410: Hydroelectric Power Plants &#8211; Communication for monitoring and control. [Published]</li>
<li>IEC 61850-7-420 &#8212; Communications systems for Distributed Energy Resources (DER) &#8211; Logical nodes [Draft]</li>
<li>IEC 62445
<ul>
<li>IEC 62445-1 &#8212; Use of IEC 61850 for the communication between substations [Approved New Work]</li>
<li>IEC 62445-2 &#8212; Use of IEC 61850 for the communication between control centers and substations [Approved New Work]</li>
<li>IEC 62445-3 &#8212; Mapping of IEC 61850 based Common Data Classes (CDC&#8217;s), information addressing, services onto IEC 60870-5-104/101 [Approved New Work]</li>
</ul>
</li>
<li>IEC 61400-25 &#8212; IEC 61850 Adaptation for Wind Turbines
<ul>
<li>IEC 61400-25-1 &#8212; Wind turbines &#8211; Part 25-1: Communications for monitoring and control of wind power plants &#8211; Overall description of principles and models [Published]</li>
<li>IEC 61400-25-2 &#8212; Wind turbines &#8211; Part 25-2: Communications for monitoring and control of wind power plants &#8211; Information models [Published]</li>
<li>IEC 61400-25-3 &#8212; Wind turbines &#8211; Part 25-3: Communications for monitoring and control of wind power plants &#8211; Information exchange models [Published]</li>
<li>IEC 61400-25-4 &#8212; Wind turbines &#8211; Part 25-4: Communications for monitoring and control of wind power plants &#8211; Mapping to communication profile
<ul>
<li>Mapping to Web services [Work under progress]</li>
<li>Mapping to MMS [Refer to IEC 61850-8-1 (published)]</li>
<li>Mapping to OPC XML DA [Work under progress]</li>
<li>Mapping to IEC 60870-5-104 [Refer to IEC 62445-3 (Work under progress)]</li>
<li>Mapping to DNP3 [Work under progress]</li>
</ul>
</li>
<li>IEC 61400-25-5 &#8212; Wind turbines &#8211; Part 25-5: Communications for monitoring and control of wind power plants &#8211; Conformance testing [Published]</li>
<li>IEC 61400-25-6 &#8212; Wind Turbines &#8211; Part 25-6: Communications for monitoring and control of wind power plants &#8211; Logical node classes and data classes for condition monitoring [Work under progress]</li>
</ul>
</li>
<li>IEC 62271-3 &#8212; Communications for monitoring and control of high-voltage switchgear (published)</li>
</ul>
<h2>See also</h2>
<ul>
<li>GSE (Generic Substation Events)</li>
<li>Substation Configuration Language (IEC)</li>
<li>IEC 60870-5</li>
<li>IEC 60870-5-101</li>
<li>IEC 60870-5-103</li>
<li>IEC 60870-5-104</li>
<li>DNP3</li>
</ul>
<h2>References</h2>
<ol>
<li id="cite_note-0"><strong>^</strong> IEC 61850 overview.</li>
<li id="cite_note-1"><strong>^</strong> Technical Committee 57 (TC57)</li>
</ol>
<h2>External links</h2>
<dl>
<dt>General Information </dt>
</dl>
<ul>
<li>Detailed Introduction to IEC 61850</li>
<li>IEC Website for IEC 61850 standards</li>
<li>IEC 61850 Technical Issues Website</li>
<li>UCA International Users Group</li>
<li>IEC 61850-3 standard and requirement</li>
<li>PRAXIS PROFILINE Special edition: IEC 61850 &#8211; Generating Tomorrow’s Electricity</li>
</ul>
<p><!--  NewPP limit report Preprocessor node count: 102/1000000 Post-expand include size: 345/2048000 bytes Template argument size: 6/2048000 bytes Expensive parser function count: 0/500 --><!-- Saved in parser cache with key enwiki:pcache:idhash:2127941-0!1!0!default!!en!2 and timestamp 20100114032714 --></p>
<div>Retrieved from &#8220;http://en.wikipedia.org/wiki/IEC_61850&#8243;</div>

<div style="font-size:0px;height:0px;line-height:0px;margin:0;padding:0;clear:both"></div>]]></content:encoded>
			<wfw:commentRss>http://www.smartgridsblog.com/standards/a-concise-introduction-to-the-iec-61850-standard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
