It is preferred among the electric utilities, in part, because;. All these characteristics that are highly-valued among electric utilities and the oil and gas industry with widely remote field stations. DNP3 is a robust, flexible, reliable and non-proprietary community managed by dnp. It supports;.

Author:Arashizuru Dakinos
Language:English (Spanish)
Genre:Health and Food
Published (Last):20 January 2013
PDF File Size:4.71 Mb
ePub File Size:9.53 Mb
Price:Free* [*Free Regsitration Required]

The development of DNP3 was a comprehensive effort to achieve open, standards-based Interoperability between substation computers, RTUs, IEDs Intelligent Electronic Devices and master stations except inter-master station communications for the electric utility industry. Also important was the time frame; the need for a solution to meet today's requirements.

As ambitious an undertaking as this was, we reached this objective. DNP3 has been designed to be as close to compliant as possible to the standards as they existed at time of development with the addition of functionality not identified in Europe but needed for current and future North American applications e. In November , responsibility for defining further DNP3 specifications and ownership of the DNP3 specifications was turned over to the DNP3 Users Group, a group composed of utilities and vendors who are utilizing the protocol.

DNP3 is an open and public protocol. In order to ensure interoperability, longevity and upgradeability of the protocol, the DNP3 Users Group has taken ownership of the protocol and assumes responsibility for its evolution. The DNP3 Users Group Technical Committee evaluates suggested modifications or additions to the protocol and then amends the protocol description as directed by the Users Group members. Complete, comprehensive documentation of the protocol is available to the public.

Member Fee Guide. Public Documents. DNP3: Building on Success. Fast Find.


Overview of the DNP3 Protocol

DNP3 Distributed Network Protocol represents a set of communication protocols that are deployed between components in process automation systems. It is mainly used in utilities such as electric and water companies and was developed for communications between different types of data acquisition and control equipment. The transport layer is presented on only one byte and is mainly used for fragmenting large DNP3 packets. The length of each packet is bound by the one byte length field, so a maximum of bytes, excluding CRCs, is permitted. The six bit sequence number is used for fragment reassembly. The object type sent in a DNP3 object range is determined by the object group and variation within that group e.


SCADA Distributed Network Protocol (DNP3)

Distributed Network Protocol 3 DNP3 is a set of communications protocols used between components in process automation systems. Its main use is in utilities such as electric and water companies. Usage in other industries is not common. It was developed for communications between various types of data acquisition and control equipment. Competing standards include the older Modbus protocol and the newer IEC protocol. While IEC was still under development and had not been standardized, there was a need to create a standard that would allow interoperability between various vendors' SCADA components for the electrical grid. Thus, in , GE-Harris Canada formerly known as Westronic used the partially completed IEC protocol specifications as the basis for an open and immediately implementable protocol that specifically catered to North American requirements.

IEC 60268 5 PDF

DNP3 Tutorial Part 1: An Introduction to DNP3

It is widely used because it is an open protocol, meaning any manufacturer can develop DNP3 equipment that is compatible with other DNP3 equipment. Since its introduction in as an immediately deployable solution for monitoring critical infrastructure status and allowing reliable remote control, Distributed Network Protocol DNP or DNP3 has achieved widespread acceptance. DNP3 is based on an object model that greatly reduces the bit mapping of data that is traditionally required by other less object oriented protocols. It also reduces the wide disparity of status monitoring and control paradigms generally found in protocols that provide virtually no pre-defined objects. Purists of these alternate protocols would insist that any required object can be 'built' from existing objects. DNP3 is typically used between centrally located masters and distributed remotes. The master provides the interface between the human network manager and the monitoring system.

Related Articles