PAP12: Mapping IEEE 1815 (DNP3) to IEC 61850 Objects | |
PAGE CONTENTS | |
|
RECENT NEWS
PAP12 met in conjunction with the SGIP Face to Face meeting in Portland, on July 11,2012. See the PAP-12 Meeting Minutes and Material section below for more information
SGIP Catalog of Standards (CoS ) – Summary and Artifacts Page for IEEE Std 1815TM-2010: IEEE Standard for Electric Power Systems Communications – Distributed Network Protocol (DNP3). http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/SGIPCosSIFIEEE18152010
PAP12 MEMBERSHIP AND MEETING DETAILS
MEETING TIME: Every 4th Tuesday at 8:00AM Pacific / 11:00AM Eastern Time (duration is 90 minutes)
CALL IN DETAILS: Toll Free 1-877-869-4197 Toll 1-503-295-8000 Code: 7260760
E-MAIL DISTRIBUTION LIST FOR PAP-12: WEBINAR (WEB CONFERENCE) MEETING SUPPORT: |
Status | IEEE 1815-2010 | IEEE 1815-2012 | IEEE 1815.1 (AKA IEEE P1815.1, since it is still an IEEE "project") |
---|---|---|---|
Title of the standard | Standard for Electric Power Systems Communications - Distributed Network Protocol (DNP3) | Standard for Electric Power Systems Communications - Distributed Network Protocol (DNP3) | Draft Standard for Exchanging Information Between Networks Implementing IEC 61850 and IEEE Std 1815 (DNP3) |
Listed in IEEE.org as: | Superseded Standard | Active Standard | Active Project |
Comment | Already in the Catalog of Standards | Update to IEEE 1815-2010 | |
TWiki Page | SGIPCosSIFIEEE18152010 | None yet | SGIPCosSIFIEEEP18151 |
IEEE Ballot | Done | Done | Done |
IEEE FInal Draft | Done | Done | October 2012 (projected) |
IEEE Publication | July 2010 | October 2012 (projected) | 2013 Q1 (projected) |
CSWG Review | Done | Preliminary | Preliminary |
SGAC Review | Done | Preliminary | Preliminary |
CoS Artifacts | Done | None yet | None yet |
Added to CoS | December 2011 | Not complete yet | Not complete yet |
Date | Updated By | Latest PAP Status |
---|---|---|
2012-10-05 | Ron Farquharson | PAP12 is focused on two major standards for utility communications: IEEE Std 1815 (DNP3) and IEEE P1815.1 (mapping IEEE Std 1815 to IEC 61850). IEEE Std 1815 was first published in July 2010. All Catalog of Standards (CoS ) artifacts for this standard were completed with documents posted on the CoS TWiki page in late October 2011. After successful votes by the SGIP Governing Board and the SGIP Plenary, the standard was added to the CoS in in December 2011. IEEE WG C12 and the DNP Technical Committee have now completed a major update of IEEE Std P1815 which will be published as IEEE Std 1815-2012. The update includes the new DNP3 Secure Authentication Version 5 and incorporates a large number of technical bulletins and other changes by the DNP User Group Technical Committee. Preparation of the CoS artifacts and the rest of the CoS process will commence once the standard is published which is expected in October 2012. The IEEE WG C14 have accomplished a great deal of work on IEEE P1815.1 (mapping between IEEE Std 1815 and IEC 61850). The sponsor ballot pool to review the document was formed with a total of 167 interested IEEE members. The sponsor ballot closed in early August 2012 with 391 comments. Since that time a Ballot Resolution Committee (BRC) formed from the C14 members has been meeting frequently (often weekly) to develop resolutions to the comments. In parallel, IEEE editorial staff have been updating the draft document. Once the resolutions to all comments are developed and the WG confirms by vote, the document will be issued for a recirculation ballot. Allowing for the IEEE review and publication cycles, it is anticipated that this will lead to publication in Q2 of 2013. Pursuit of dual logo with the IEC will follow after that.
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
These tasks have been revised and dates have been changed.
Task Description | Responsible | Completion Date | Notes |
Task 1: Define Use Cases |
Grant Gilchrist | 2010-05 | Define the Use Cases for transfer of information. The Use Cases will begin with DNP devices throughout the system and add 61850 devices at various points in the system. Data transfer needs will be developed for each Use Case |
Task 2: Gap Analysis: Identify to what extent DNP XML supports the use cases and what the gaps are |
Jim Coats | 2010-08 | Gap Analysis: Identify to what extent DNP XML supports the use cases and what the gaps are. It is understood at the outset that 61850 supports much richer data semantics which will not be transferrable to a 61850 system |
Task 3: Identify how 61850 SCL can make the external reference |
Christoph Brunner | 2010-08 | Identify how 61850 SCL can make the external reference to DNP3 objects. 61850 presently support a “sAddr” field, but this might not be able to contain enough information to provide a complete mapping to DNP3 |
Task 4: Gap Analysis: Verify how SCL could support all use cases |
Christoph Brunner | 2010-10 | Gap Analysis: Verify how SCL could support all use cases. Verify that SCL mechanisms exist to perform the entire mapping of semantics to DNP3 |
Task 5: Define rules for associating DNP XML and 61850 SCL in supporting use cases? |
Jim Coats/Christoph Brunner | 2010-10 | Define rules for associating DNP XML and 61850 SCL in supporting use cases. External reference to DNP Objects (Mapping points in DNP up to 61850 object models, so we don’t duplicate that file in the SCL file). Ensure that mapping in both directions is complete. |
Task 6: Create Example DNP XML file mappings |
Jim Coats | 2010-10 | Develop Guidelines for use of 61850 and DNP integration strategies. Need to provide guidance to users on how to choose optimal migration straegies. |
Task 7: Develop Guidelines for use of 61850 and DNP integration strategies |
Grant Gilchrist | 2010-10 | Create Example DNP XML file mappings. The example DNP XML file will illustrate most of the object conversion issues as possible in a single file. |
There is an urgent need for distribution and transmission communication networks currently using the DNP3 protocol to support the exchange of larger volumes of data (with low latency/time delays) necessary to achieve new Smart Grid capabilities. This action plan focuses on developing the means to enable transport of select Smart Grid data and related services over legacy DNP3 networks. This will be accomplished, in part, by defining a method to map the exchange of certain data types and services between DNP3 and the newer IEC 61850 Standard for Communication Networks and Systems in Substations. IEC 61850 is considered to be a standard better suited to support Smart Grid functions. IEC 61850 is a comprehensive standard for substation automation that supports monitoring and control of grid equipment (relays, circuit breakers, transformers) as well as renewable energy resources. Many of the new Smart Grid deployments, including those funded under Department of Energy Smart Grid grants programs, will require rapid, high-bandwidth communications that are better supported by IEC 61850. The tasks of this action plan include performing a gap analysis to identify the extent to which DNP3 meets Smart Grid requirements. Guidelines for achieving interoperable integration of DNP3 with IEC 61850 and other Smart Grid standards will be produced in 2010.
Data acquisition consists of three types of data: binary (digital) inputs, analog inputs, and counters. Supervisory control consists of commands for both digital and analog equipment. DNP3 was designed for low-bandwidth Supervisory Control and Data Acquisition (SCADA) operations that control grid equipment. Although this protocol allows any DNP data to be transported between two points, the semantic content of the messages depends upon lists of tables, which are not machine readable. In addition, mapping of objects in each direction presents difficult challenges. The goal is to ensure that select data is seamlessly transported between devices and readily used by them, even when there are communication constraints imposed by the DNP3 protocol.
Transmission and distribution domains at the application layer.
The integration of DNP3 and IEC 61850 systems will be accomplished by the insertion of protocol translators at the Master/Client side. In general, these protocol translators will consist of a configurable software module. The key problem is that this configuration must be made as automatically as possible in order to reduce the possibility of injection of translation errors into the system. Both DNP3 and 61850 use XML files for configuration, but these files contain different types of information. On the DNP3 side, the XML file contains a one-to-one mapping of DNP3 objects to 61850 object attributes. On the IEC side, there is also a one-to-one mapping of the data attributes to a (type-less) “short address”. The missing piece is the algorithm needed to transfer the data value and data semantic between the system. Adding the information to DNP3 XML files is a possibility, although the DNP3 XML format forbids extensions which are not built into the DNP3 specification. Here DNP3 has the advantage wherein the specification can be extended without lengthy balloting reviews. Adding the information to the IEC XML file is actually much simpler because multiple extension rules are built into the 61850 System Configuration Language (SCL) standard. One set of extension rules, known as “private data”, allows new (usually vendor-specific) information to be added almost anywhere within SCL. Another set of rules, “extension schemas”, allows more targeted extensions. It is unknown at this time which extensions to each of the XML file format will yield the optimal object transfer mechanism.
Project Team Leads |
---|
NIST Lead: Jerry FitzPatrick gerald.fitzpatrick@nist.gov |
Technical Champion: |
CSWG Liaison: Frances Cleveland |
SGAC Liaison: Stephan Amsbary |
Action Plan SDO Leads: DNP Technical Committee: Andrew West andrew.west@ieee.org IEEE PES Substations Committee WG C14 (IEEE P1815.1): Ron Farquharson ron@enernex.com IEEE PES Substations Committee WG C14 (IEEE P1815.1): Grant Gilchrist grant@enernex.com IEC TC57 WG10: Christoph Brunner christoph.brunner@utinnovation.com IEEE PES Substations Committee WG C12 (IEEE Std 1815): Ron Farquharson ron@enernex.com UCAIug Technical Committee: Kay Clinard Clinardkay@aol.com |
Stakeholder Leads |
Other SDO Representatives: DNP Technical Committee: Barry Shephard barry.shephard@grontmij.co.uk UCAIug Testing Committee: Bruce Muschlitz bruce@EnerNex.com IEC TC57 WG10 Barry Shephard barry.shephard@grontmij.co.uk IEC TC57 WG03: Wolfgang Brodt wolfgang.brodt@siemens.com UCAIug 61850 Technical Group: George Schimmel gs@trianglemicroworks.com |
Users Group Leaders: DNP User Group: Jim Coats jcoats@trianglemicroworks.com UCA International Users Group: Kay Clinard Clinardkay@aol.com Utility Representatives: Rick Murphy murphyr@FirstEnergyCorp.com |
Meeting minutes, slides, and other notes may be found here: PAP12MeetingMinutes
Meeting minutes, slides, and other notes may be found here: C14MeetingMinutes
Current chapter and document drafts may be found here: C14DocumentDrafts
The scope of this work seems clear, though no service providers or owner/operators are listed in Section 12.7. Do these stakeholders think this is a priority item? As the scope seems to look at a standard adaption between IEC 61850 and DNP, perhaps this would be best left to suppliers and integrators who must routinely confront this problem. | SteveWidergren | 2009-09-03 - 10:15 |
Please be aware that the IEC 61400-25-4 already contains a DNP3 mapping suitable for the IEC 61850 series. | KeldRasmussen | 2010-02-11 - 11:25 |