This article provides insufficient context for those unfamiliar with the subject. ( January 2011) IEC 60870 part 5 is one of the set of standards which define systems used for telecontrol in and applications. Part 5 provides a communication profile for sending basic telecontrol messages between two systems, which uses permanent directly connected data circuits between the systems. The (Working Group 03) have developed a standard for telecontrol, teleprotection, and associated telecommunications for systems.
The result of this work is IEC 60870-5. Contents.IEC 60870-5-101 IEC 60870-5-101 IEC101 is a standard for power system monitoring, control & associated communications for telecontrol, teleprotection, and associated telecommunications for electric power systems. This is completely compatible with IEC 60870-5-1 to IEC 60870-5-5 standards and uses standard asynchronous serial tele-control channel interface between. Clarke et al, Practical modern SCADA protocols: DNP3, 60870.5 and related systems, Newnes, 2004. Maynard, Peter; McLaughlin, Kieran; Haberler, Berthold (11 September 2014). 2nd International Symposium for ICS & SCADA Cyber Security Research 2014: 30–42.:. Retrieved 30 June 2015.External links., IEC 60870-5-104 client and server Java implementation in Eclipse NeoSCADA™, -licensed., IEC 60870-5-104 client and server Java library at openmuc.org, GPL-licensed.
IEC 60870-5-101 & IEC 60870-5-104 client and server Go implementation, public domain.
URL:IEC60870-6 Telecontrol Application ServiceElement 2 (TASE.2) protocol (informally known as the InterControl CenterCommunications Protocol (ICCP)) was developed by IEC TC57 WG07 for dataexchange over Wide Area Networks (WANs) between a utility control center andother control centers, other utilities, power plants and substations.TASE.2 (ICCP) is used in almost every utility forinter-control center communications between SCADA and/or EMS systems. It issupported by most vendors of SCADA and EMS systems.Since it was first developed in the mid 1990's beforeobject models had been developed for SCADA applications, TASE.2 (ICCP) was notdesigned to support the transfer of different types of object models, beyondthose defined in Part 802.The TASE.2 protocol allows for data exchange overWide Area Networks (WANs) between a utility control center and other controlcenters, other utilities, power plants and substations. 60870-6-503 Services and Protocol - This part of IEC 60870 defines amechanism for exchanging time-critical data between control centers. Inaddition, it provides support for device control, general messagingand control of programs at a remote control center. It defines a standardizedmethod of using the ISO 9506 Manufacturing Message Specification (MMS) servicesto implement the exchange of data.
SPIDER supports the Inter-Control Center Communications Protocol (ICCP)( IEC 60870-6/TASE.2) for data exchange over Wide Area Networks (WANs). Data exchange between a utility and other control centers, power pools, regional control centers and generating plants is made easy and efficient with ICCP. Based on the specifications for the TASE.2/ICCP protocol, we do not currently have any products that support this protocol. Normally, we would try to use one of our user configurable OPC Servers for a protocol for which we have no standard product but this protocol would be too complex for such an implementation.
The definition of TASE.2 consists of threedocuments. This part of IEC 60870 defines the TASE.2 application modeling andservice definitions. 60870-6-602 Transport Protocols - This Technical Report describes theTransport Profiles for the IEC 60870-6 Series over WAN with Reference toInternational Standardized Profiles (ISP’s) used by distributed SCADA/EMSapplications in control centers, power plants andsubstations. The Transport Profiles use virtually any standard or de-factostandard (including TCP/IP) connection-mode and connectionless-mode networkservices over any type of transmission media.
60870-6-702 Profiles - This specification defines the ApplicationProfile (Layers 5-7) for use with ICCP. It is needed for vendors implementingprotocol stacks that support the ICCP application layer.
Most users of ICCPwill not be concerned with this specification. 60870-6-802 Object Model - This part of IEC 60870 proposes object modelsfrom which to define object instances. The object models represent objects fortransfer. The local system may not maintain a copy of every attribute of anobject instance.Keywords: IEC 61970 -CIM, CIM Extensions, and GIDIntelliGridArchitectureCopyright EPRI 2004.