23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DNP3 and IEC 60870-5 58-3<br />

protocol standards for those applications, but will adopt different standards for other applications<br />

(e.g., for safety interfaces such as signaling).<br />

Other major industries with large-scale widely distributed SCADA networks include oil and gas pipeline<br />

monitoring and water and wastewater monitoring. These industries have some requirements in<br />

common with electric power SCADA and some differences.<br />

The oil and gas industries and water and wastewater industries typically have a relatively long time<br />

domain associated with their monitoring requirements: Pressures in gas pipelines and rates of flow and<br />

levels for liquids generally do not change rapidly or need prompt attention. This generally allows for a<br />

slower data collection strategy with a period of data collection in the range from minutes to hours often<br />

being acceptable. One notable exception to this is the prompt reporting of “urgent” alarm conditions<br />

that might necessitate operator intervention or maintenance call out.<br />

For these pipeline industries, there are few additional requirements that are not covered by power system<br />

applications and therefore the electric power protocols and also Modbus (where no time tagging or SOE data<br />

is required) are applicable. Proprietary protocols are also still very common in the oil and gas industries.<br />

In recent years, the water industries in the United Kingdom and Australia have standardized on DNP3 for<br />

SCADA interfaces and are making use of the SOE functionality to allow accurate recording of field actions<br />

while allowing infrequent polling. DNP3 supports an unsolicited reporting mechanism where changes can<br />

be reported from the field without needing a request from the master station. The use of this feature allows<br />

prompt indication of urgent alarm conditions without requiring frequent polling of each remote site.<br />

The IEC 60870 series profiles have not been widely adopted in the oil and gas and water industries,<br />

possibly because of a perception that they are power-system specific.<br />

58.2 Features Common to IEC 60870-5 and DNP3: Data<br />

Typing, Report by Exception, Error Recovery<br />

The International Electrotechnical Commission’s 60870-5 series of standards were developed by the<br />

IEC Technical Committee 57 over the period 1988–2000. Some parts have been updated with subsequent<br />

revisions and extensions. This series includes the IEC 60870-5-101 [1] and 60870-5-104 [2] profiles<br />

for basic telecontrol tasks over serial and TCP/IP links. The IEC 60870-5 series are recognized as the<br />

international standards for electric power SCADA transmission protocols. Their use for that purpose is<br />

mandated in many countries by government legislation and they are widely adopted in Europe and in<br />

countries where European companies and conventions have significant influence.<br />

IEC 60870 parts -5-1 through to -5-5 define a “cookbook” of rules for specifying SCADA Telecontrol<br />

protocols. Part -5-101 (sometimes also known as “Telecontrol 101” or “T101”) specifies a fully defined<br />

profile for basic Telecontrol tasks based on these rules. T101 includes the definition of general-purpose<br />

and power-system-specific data objects and functions directly applicable to the substation to control<br />

center SCADA link. Part -5-104 (“T104”) defines the transmission of T101 over TCP/IP with some<br />

minor functional extensions such as the addition of time tags to control objects.<br />

DNP3 [3] is a general-purpose SCADA protocol based on the design rules in the early parts of IEC<br />

60870 that adds some concepts that are quite different from those defined in later parts of IEC 60870-5.<br />

It defines data types and functions for the transmission of generic SCADA data. While it was designed<br />

for power system application, it does not include power-system-specific data objects.<br />

DNP3 was initially developed by the Canadian SCADA company Westronic and was placed in the public<br />

domain in 1993. It is now maintained by an independent body called the DNP Users Group and is considered<br />

a de facto standard for electric power SCADA <strong>communication</strong> in North America where it is used by over 80%<br />

of power utilities [4]. DNP3 is also the de facto standard for electric power SCADA <strong>communication</strong>s in most<br />

other English-speaking countries and places where North American vendors have significant market influence.<br />

The creation of DNP3 appears to have been influenced by a pragmatic response to utility market demands for<br />

conformance to the IEC 60870 standard in the years prior to the publication of IEC 60870-5-101. Its placement<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!