TASE.2

from Wikipedia, the free encyclopedia

The Telecontrol Application Service Element 2 ( TASE.2 ) protocol is used to couple different network control centers . It is also known as the Inter-control Center Communications Protocol ( ICCP ). TASE.2 was developed under the leadership of the Electric Power Research Institute (EPRI) in the USA and has now established itself worldwide as a manufacturer-neutral interface.

history

At the end of 1988, the Electric Power Research Institute (EPRI) started the Utility Communication Architecture (UCA) project in the USA , which was supposed to develop standards for communication in the power supply industry. Very early on, the focus was on exchanging data between control centers, e.g. B. in power plants and high-voltage networks, because here a standardization for the areas of generation, transport and distribution was most urgent due to different companies. At that time there were essentially three standards in this area, WSCC (western USA), IDEC (eastern USA) and ELCOM (Europe). The result of the work was TASE.2. TASE.2 has been an international standard as IEC 60870-6 since the end of 1997 .

technology

TASE.2 only uses MMS services ( Manufacturing Messaging Specification ). It is thus decoupled from the transport protocol. Currently only the full 7-layer stack is used as a pure OSI or OSI / TCP stack (RFC1006). When using TASE.2 in embedded systems with limited resources, however, “more economical” protocol architectures, as described above, are also possible. The functionality of TASE.2 is divided into nine groups, so-called conformance blocks , whereby only the implementation of the first block is mandatory.

Block 1 Basic services DataValue, DataSet and DataSet TransferSet objects
Block 2 Extended condition monitoring enables data points to be sent from the server to the client in the event of a change ('Report-by-Exception')
Block 3 Block-by-block data transfer reduces the overhead by omitting the MMS syntax (blocking of data points)
Block 4 Messages Sending of freely defined data blocks from the server to the client
Block 5 Device control General interface for setting commands and setpoint specification (e.g. device assignment with timeout monitoring 'Select-before-Operate')
Block 6 Program control Starting, stopping and resetting programs on the server
Block 7 Events Clients can register for events with the server and are informed about their occurrence
Block 8 Plans, matrices Tables as data types, special types for delivery schedules, transmission routes, etc.
Block 9 Value series The client can initiate the recording of data points and the transmission of the resulting series of values, specifying time intervals on the server

Existing TASE.2 installations primarily use blocks 1, 2 and 5. The basis for data exchange between server and client is an agreement on the data objects and their access rights, referred to as bilateral table in the TASE.2 documents . The client can use the data sets to combine individual data points from the server into groups and link these groups with transfer orders. The server then sends the affected data points in the event of a change and / or at time intervals specified by the client.

Norms and standards

See IEC 60870-6 series of standards , especially the following three standards for TASE.2:

  • IEC 60870-6-503: Services and Protocol
  • IEC 60870-6-802: Object Models
  • IEC 60870-6-702: Application Profile

Web links