“SCADA Systems Benefit from IEC 61850” http://blog.iec61850.com/2011/02/scada-systems-benefit-from-iec-61850.html "IEC 61850 allows protection and control functionality in the substation to be modelled into different logical nodes, and grouped under different logical devices. This saves considerable time in implementing new protection devices because you do not have to map device points to SCADA points as in the case of DNP protocol."
The Standard is a vendor-agnostic system-engineering process (from specification to implementation to operation and into maintenance) to configure IEDs to be able to communicate between them to monitor, protect, control and manage infrastructure associated with electrical networks.
Please note the sequencing of the Parts of the Standard as an indication of the way in which the Standard should be applied ... - many fall into the trap of going straight to Part 8 or 9 where the different real time messages (MMS / GOOSE / Sampled Values) are defined, but our objective should not be simply to boast "we have a GOOSE in the substation".
Part 3: Physical requirements of the IED for environmental withstand including temperature etc., EMC, auxiliary supply ranges etc. (N.B.: a device can comply to just IEC 61850-3 without having any IEC 61850 functionality)
Part 4: a project management methodology
Part 5: the definition of the system communication requirements in the substation
Part 6: the prescription of the engineering environment for configuring of functions (which is ultimately supplied in IEDs) to communicate with other functions interoperably
Part 7: a set of defined object structures with semantics of what could need to be communicated
Part 8 and Part 9 There are two principal types of communication processes for the real time communication between the functions (supplied in IEDs) Client-Server communications mechanisms Part 8-1: SCADA master-slave command/polling server event triggered reporting to the client Publisher-Subscriber communication mechanism Part 8-1 repetitive retransmission of the status of a function with fast repetition of that changed status when an event occurs (GOOSE) Part 9-2 (and independent IEEE Guideline 9-2LE) for continuous transmission of instantaneous Sampled Values Across all of these above (IEC 61850 Part 8-1 and 9-2) is the mapping onto TCP/IP Ethernet networks to actually get the message from device A to device B, C, D.... This is where the confusion of a protocol stems from.
Just "limiting" the definition of IEC 61850 to some small part of Part 8-1 and 9-2 as being a "protocol" clearly misses the whole point of IEC 61850 with the inevitable poor experiences.
Ignoring Parts 3, 4, 5, 6 and 7 in projects and specifications is quite possibly (probably) going to lead you into the same sorts of problems that have been reported by ENTSO-E as 41 transmission utilities in Europe following their first 8 years of using IEC 61850.
A phone call is nearly always welcome depending on the time of night wherever I am in the world. Based in Adelaide UTC +9:30 hours e.g.
Noon UK = 2030 Adelaide
Noon UK = 2230 Adelaide
Office + 61 8 7127 6357 Mobile + 61 419 845 253
No Liability: Rod Hughes Consulting Pty Ltd accepts no direct nor consequential liability in any manner whatsoever to any party whosoever who may rely on or reference the information contained in these pages. Information contained in these pages is provided as general reference only without any specific relevance to any particular intended or actual reference to or use of this information. Any person or organisation making reference to or use of this information is at their sole responsibility under their own skill and judgement.