Transmission Fast Simulation and

Modeling Tech Update:

Telecommunications Infrastructure Assessment for
Monitoring and Voltage Security Prediction in the
Northern Area of the Polish Power Grid

Case Study at PSE-Operator in Poland

1014781
 Transmission Fast Simulation and
Modeling Tech Update:
Telecommunications Infrastructure Assessment for
Monitoring and Voltage Security Prediction in the Northern
Area of the Polish Power Grid
Case Study at PSA-Operator in Poland

1014781

Technical Update, 2007

EPRI Project Manager

M. Samotyj

PSE-Operator Project Manager

P. Antos

ELECTRIC POWER RESEARCH INSTITUTE

3420 Hillview Avenue, Palo Alto, California 94304-1395 ▪ PO Box 10412, Palo Alto, California 94303-0813 ▪ USA
800.313.3774 ▪ 650.855.2121 ▪ [email protected] ▪ www.epri.com
DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITIES
THIS DOCUMENT WAS PREPARED BY THE ORGANIZATION(S) NAMED BELOW AS AN ACCOUNT OF
WORK SPONSORED OR COSPONSORED BY THE ELECTRIC POWER RESEARCH INSTITUTE, INC. (EPRI).
NEITHER EPRI, ANY MEMBER OF EPRI, ANY COSPONSOR, THE ORGANIZATION(S) BELOW, NOR ANY
PERSON ACTING ON BEHALF OF ANY OF THEM:

(A) MAKES ANY WARRANTY OR REPRESENTATION WHATSOEVER, EXPRESS OR IMPLIED, (I) WITH
RESPECT TO THE USE OF ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM
DISCLOSED IN THIS DOCUMENT, INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, OR (II) THAT SUCH USE DOES NOT INFRINGE ON OR INTERFERE WITH PRIVATELY OWNED
RIGHTS, INCLUDING ANY PARTY'S INTELLECTUAL PROPERTY, OR (III) THAT THIS DOCUMENT IS
SUITABLE TO ANY PARTICULAR USER'S CIRCUMSTANCE; OR

(B) ASSUMES RESPONSIBILITY FOR ANY DAMAGES OR OTHER LIABILITY WHATSOEVER (INCLUDING
ANY CONSEQUENTIAL DAMAGES, EVEN IF EPRI OR ANY EPRI REPRESENTATIVE HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES) RESULTING FROM YOUR SELECTION OR USE OF THIS
DOCUMENT OR ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM DISCLOSED IN
THIS DOCUMENT.

ORGANIZATION(S) THAT PREPARED THIS DOCUMENT

Institute of Energy, Gdansk Division

This is an EPRI Technical Update report. A Technical Update report is intended as an informal report of
continuing research, a meeting, or a topical study. It is not a final EPRI technical report.

NOTE
For further information about EPRI, call the EPRI Customer Assistance Center at 800.313.3774 or
e-mail [email protected].

Electric Power Research Institute, EPRI, and TOGETHER…SHAPING THE FUTURE OF ELECTRICITY
are registered service marks of the Electric Power Research Institute, Inc.

Copyright © 2007 Electric Power Research Institute, Inc. All rights reserved.
 CITATIONS
This document was prepared by
Institute of Energy, Gdansk Division
12 Mikolaja Reja
Gdanks, Poland
Principal Investigator
A. Babs
This document describes research sponsored by the Electric Power Research Institute (EPRI)
This publication is a corporate document that should be cited in the literature in the following
manner:
Transmission Fast Simulation and Modeling Tech Update: Telecommunications Infrastructure
Assessment for Monitoring and Voltage Security Prediction in the Northern Area of the Polish
Power Grid: Case Study at PSE-Operator in Poland. EPRI, Palo Alto, CA, 2006. 1014781.

iii
 ABSTRACT
This technical update describes the status of effort to date on two first tasks of the project with
Polish transmission system operator (PSE-Operator) to help define needs for IntelliGrid-based
architecture, an enhanced electricity delivery model that is expected to dramatically improve
power line reliability and capability. The tasks were performed at the northern part of the
national grid system in Poland.
Task 2: Telecommunications Infrastructure Assessment
This task involves investigating the existing telecommunications infrastructure and comparing
the results with requirements obtained in Task 1 to determine if any changes or additions are
required to implement those requirements. Potential issues include bandwidth, latency, network
management capability, and security.
EPRI considers this project pivotal because it represents the first demonstration of how to
transform the electric grid into more responsive and resilient delivery system and that will prove
vital as the utility industry plan, designs, upgrades, and replaces equipment that will serve
customer needs over the next 40 to 50 years.

v
 ACKNOWLEDGEMENTS
The authors and the project managers would like to express appreciation to the following
individuals who generously contributed their time and knowledge to the development of this
report. They provided important information about fast simulation and modeling needs at their
respective organizations. They also offered valuable review and feedback on elements of the
report:
Stefania Kasprzyk
President, PSE-Operator
Andrzej Botor
Manager, PSE-Poludnie
Jerzy Dudzik
Director, PSE-Operator
Marek Fulczyk
Project manager, ABB-Polska
Marek Glaz
Manager, PSE-Operator
Jerzy Pilar
Technical staff member, PSE-Operator
Krzysztof Slimak
Manager, PSE-Polnoc
Magdalena Wasiluk-Hassa
Director, PSE-Operator
Jacenty Weglinski
Director, PSE-Operator

vii
 CONTENTS
1 ASSUMPTIONS CONCERNING TELECOMMUNICATION INFRASTRUCTURE ................1-1

2 ANALYSIS OF ABILITIES TO UTILIZE EXISTING PSE-OPERATOR SA

TELECOMMUNICATION INFRASTRUCTURE ........................................................................2-1

3 CHARACTERISTICS OF COMMUNICATION PROTOCOLS................................................3-1

IEC 60870-5-x Series Protocols...........................................................................................3-1
DNP 3.0 Protocol .................................................................................................................3-4

4 ESTIMATE OF REQUIRED CAPACITY OF COMMUNICATION CHANNELS .....................4-1

IEC 61870-5-101 protocol ....................................................................................................4-1
DNP 3.0 protocol..................................................................................................................4-2

5 CONCLUSIONS .....................................................................................................................5-1

ix
1
ASSUMPTIONS CONCERNING TELECOMMUNICATION
INFRASTRUCTURE
The TFSM project assumes that Data Concentrators will be installed in selected high-voltage
(HV) substations. These concentrators will send collected data received from substations (for
example from measuring transformers, relays and also from ARNE and SSiN systems) to the
M&VSP System server that will be installed at the dispatching center in PSE North (ODM
Bydgoszcz). If the SSiN substation system is the only data source at a selected substation, this
system will directly send data to the server. The proposed system configuration is shown in
Figure 1-1.

Figure 1-1
Proposed System Configuration

1-1
The data sources (e.g. Data Concentrators, SSiN systems) and the data communication system
connecting these concentrators with the server have to fulfill the following requirements:

• Data updating cycle has to be no longer than 1 s

• The total data transmission delay (i.e., the sum of communication network delay, data
processing delay at a given substation and data processing delay in the server) has to be no
longer than 1 s
• Data received from substations should be aggregated – the Data Concentrator has to
aggregate data before transmission to the system server
• It is recommended that widely used (standard) communication protocols be utilized, e.g., IEC
870-5-101, IEC 870-5-104, DNP 3.0.
Figure 1-2 shows selected substations from which data will be sent to the M&VSP System server
(directly from SSiN systems or indirectly from Data Concentrators).

Figure 1-2
Location of HV substations selected for the M&VSP System

1-2
Table 1 contains a list of the selected HV substations that will serve as a data source for the
M&VSP System. Data communication supervision is also shown in this table.

Table 1
List of the Selected HV Substations

HV substation selected for the Data Concentrator Supervision of data transmission

TFSM project (DC) /SSiN
Dunowo DUN (400, 220 kV) DC
ydowo ZYD (220 kV) DC
Słupsk SLK (400 kV) SSiN
arnowiec ZRC (400 kV) DC
Gda sk Błonia GBL (400 kV) DC
Gda sk GDA (220 kV) SSiN
Jasiniec JAS (220 kV) SSiN PSE North (Bydgoszcz)
Bydgoszcz BYD (220 kV) DC
Olsztyn M tki OLM (400 kV) SSiN
Olsztyn OLS (220 kV) SSiN
Grudzi dz GRU (400, 220 kV) SSiN
Włocławek Azoty WLA (220 kV) SSiN
Toru Elana TEL (220 kV) SSiN
Krajnik KRA (400, 220 kV) DC
PSE West (Pozna )
P tnów PAT (220 kV) DC
Ostroł ka OST (220 kV) DC PSE Center (Warszawa)

1-3
2
ANALYSIS OF ABILITIES TO UTILIZE EXISTING PSE-
OPERATOR SA TELECOMMUNICATION
INFRASTRUCTURE
Data communication for the TFSM project can be realized by employing the existing
telecommunication infrastructure that belongs to PSE-Operator. This infrastructure consists of
cross-connecting PCM nodes connected by dedicated 2 Mbit/s links based on a SDH Exatel
network. Figure 2-1 shows a fragment of this network that is relevant to the TFSM project.
FMX (FMX2R3.1) multiplexers are installed in HV substations. Each FMX multiplexer is a
flexible, programmable communication device that uses a standard PCM-30 time frame. These
multiplexers are either terminal (end) or add-drop devices in the mentioned PCM communication
network. Among other things, they enable one to create point-to-point, serial, asynchronous
channels with the required capacity of 9.6 - 38.4 kbit/s. These multiplexers, as well as cross-
connecting nodes, can be managed (and monitored) from one supervisory center that is located at
PSE-Operator headquarters in Warszawa.

Figure 2-1
PCM Network Fragment that is Relevant to the TFSM Project

2-1
The FMX multiplexer provides the following services:
• data transmission in accordance with V.24, V.35, V.36, RS 530, X.21, G.703 standards
• analog transmission: POTS, 2/4-wire with/without E&M
• ISDN transmission
Each FMX2R3.1 multiplexer is equipped with one central unit CUD, two G.703 (2 Mbit/s) ports
and enables addition of up to 6 multi-port cards (with both analog and digital ports). It is possible
to extend the number of multi-port cards up to 12 in case the BEC card is installed.
As a terminal multiplexer („Terminal multiplexer TMX60” mode) FMX enables connection of
up to sixty 64 kbit/s lines. As an add-drop multiplexer („Add-drop multiplexer DIMX2x30”
mode) it enables one to connect up to thirty 64 kbit/s lines.
MXS19 racks are installed in HV substations. Each rack enables installation of two FMX2R3.1
multiplexers. In case the BEC card is used, the rack is able to hold one multiplexer at most. The
multi-port line cards can be replaced by up to nine line LTx (e.g. xDSL or PDH 2 x 2Mbit/s
designed for fiber-glass connections) terminals.
The technical characteristics of selected multiplexer cards that can be used for data transmission
are given below.
• CPF2 – the card that enables insertion of up to 4 different interface modules:
• CIM-X.21 – provides X.21/V.11 interface for either 0.3 - 38.4 kbit/s and 115.2 kbit/s
asynchronous or 0.6 - 48 kbit/s, 56 kbit/s and n x 64 kbit/s (n<=31) synchronous
transmission (for a distance up to 1000 m).
• CIM-V.24 – provides V.24/V.28 interface for either 0.3 - 38.4 kbit/s and 115.2 kbit/s
or 0.6 do 48 kbit/s, 56 kbit/s, 64 kbit/s, 128 kbit/s synchronous transmission (for a
distance up to 15 m).
• CIM-V.35 – provides V.28/V.35 interface for either 0.3 - 38.4 kbit/s and 115.2 kbit/s
asynchronous or 0.6 - 48 kbit/s, 56 kbit/s and n x 64 kbit/s (n<=31) synchronous
transmission (for a distance up to 1000 m for V.35 or up to 15 m for V.28).
• CIM-V.36/RS530 – provides V.10/V.11 interface for 0.3 - 38.4 kbit/s and 115.2 kbit/s
asynchronous or 0.6 - 48 kbit/s, 56 kbit/s and n x 64 kbit/s (n<=31) synchronous
transmission (for a distance up to 1000 m).
• DSC6-nx64G – provides six G.703 ports with bit rate of n x 64 kbit/s (n=1,2,...,8) in co-
directional operating mode or with bit rate of 64 kb/s in centralized clock operating mode. It
also provides two G.703 ports with bit rate of n x 64 kbit/s (n=1,2,...,31) in co-directional
operating mode.
Table 2 shows possible connections between Data Concentrators or SSiN systems in substations
and the M&VSP System server located at PSE North in Bydgoszcz. The shortest communication
path has been taken into account. All routes are directed to the cross-connect multiplexer at
Jasiniec JAS substation. This multiplexer is connected with the PSE North dispatching center
(ODM Bydgoszcz) with a SDH STM-16 trunk (currently ODM Bydgoszcz is connected with
other objects with four STM-16 and one STM -4 trunks).

2-2
Table 2
Feasibility of Point-to-Point asynchronous data communication channels between substations
and PSE North in Bydgoszcz assuming that the PCM communication network supervised by PSE-
Operator SA is used

Substation considered in The closest Transit and the last

the TFSM project cross-connect (Jasiniec) cross-
Remerks -
multiplexer connect
connection feasibility
multiplexers.
Dunowo DUN Słupsk Bygdoszcz Jasiniec Currently feasible
ydowo ZYD Słupsk Bygdoszcz Jasiniec Currently feasible
Słupsk SLK Słupsk Bygdoszcz Jasiniec Currently feasible
arnowiec ZRC Gda sk Błonia Bygdoszcz Jasiniec Currently feasible
Gda sk Błonia GBL Gda sk Błonia Bygdoszcz Jasiniec Currently feasible
Gda sk Le no GDA Gda sk Błonia Bygdoszcz Jasiniec Currently feasible
Bydgoszcz Jasiniec JAS Bydgoszcz Bydgoszcz Jasiniec Will be feasible at the
Jasiniec end of the fourth quarter
of 2006
Bydgoszcz Zachód BYD Bydgoszcz Bydgoszcz Jasiniec Currently feasible
Jasiniec
Olsztyn M tki OLM Gda sk Błonia Bydgoszcz Jasiniec Will be feasible at the
end of the second quarter
of 2007
Olsztyn 1 OLS Gda sk Błonia Bydgoszcz Jasiniec Will be feasible at the
end of the second quarter
of 2007
Toru Elana TEL Bydgoszcz Bydgoszcz Jasiniec Currently feasible
Jasiniec
Grudzi dz GRU Bydgoszcz Bydgoszcz Jasiniec Currently feasible
Jasiniec
Krajnik KRA Krajnik Słupsk - Bydgoszcz Currently feasible
Jasiniec
Włocławek Azoty WLA Bydgoszcz Bydgoszcz Jasiniec Currently feasible
Jasiniec
P tnów PAT P tnów Bydgoszcz Jasiniec Currently feasible
Ostroł ka OST - - Will be feasible at the
end of the second quarter
of 2007

Point-to-point <substation - PSE North, Bydgoszcz> channels can be created by the Department
of Data Communications, PSE-Operator SA in Warszawa. The information given above on
channel feasibility was received from this Department.
It will be possible to create standby point-to-point channels in the same PCM network by the end
of the second quarter of 2007.

2-3
3
CHARACTERISTICS OF COMMUNICATION
PROTOCOLS
Since it is possible to create the point-to-point asynchronous channels required for the TFSM
project, short characteristics of communication protocols enabling data communication over
these channels can be found below. The following protocols are considered:
• IEC 60870-5-x series protocols
• DNP 3.0 protocols
In order to evaluate required channel capacity, data frame formats are described for both the data
link and application layers

IEC 60870-5-x Series Protocols

A broad application field of V.24/V.28 standard serial asynchronous links led to development of
a group of international standards entitled, Telecontrol equipment and systems – Part 5:
Transmission protocols.” These standards were issued by the IEC Technical Committee No. 57
(Telecontrol, teleprotection and associated telecommunications for electric power systems) in
1990-1995.
The IEC 60870-5-x series consists of the following standards:
• IEC 60870-5-1: Transmission frame formats
• IEC 60870-5-2: Link Transmission procedures
• IEC 60870-5-3: General structure of application data
• IEC 60870-5-4: Definition and coding of application information elements
• IEC 60870-5-5: Basic application functions
Besides these standards, a series of so called companion standards was developed. IEC 60870-5-
101 standard belongs to this series and is entitled “Companion standard for basic telecontrol
tasks.”
The companion standard IEC 60870-5-101 for the link layer admits data frame format FT1.2
with fixed and variable block length. The latter format, which contains user data, is shown in
Figure 3-1 (the frame with fixed length has no link user data). The link layer frames are called
Link Protocol Data Units. Each variable length data frame consists of a start character, two equal
characters which specify the number L of user data octets, the second start character, the frame
check sum character and the end character. Each octet consists of 8-bit data, a start bit, a parity
bit and a stop bit, i.e., it consists of 11 bits.

3-1
 Start 68H
L
L
Start 68H
C
A User data saved by checksum - the
number of octets is specified by L
field content (the control C and
Link user data = IEC 60870-5-101 address A fields are included)
application layer protocol frame

Checksum
End 16H

Figure 3-1
Variable Length LPDU, Compatible with FTI.2 Format

L: length field range 0-255; L specifies the number of subsequent user data octets including the
control and address fields
C: control field – it specifies protocol service function
A: address field, optional

It stems from Figure 3-1 that the maximum LPDU frame length is equal to 261 octets (253 user
data octets + 2 octets of A and C fields + 6 remaining octets). Moreover, the link user data field
contains an IEC-60870-5-101 application layer protocol frame called Application Service Data
Unit (ASDU). All possible ASDUs formats are precisely defined by the IEC 60870-5-101
standard. Figure 3-2 shows the ASDU frame format.

3-2
 Type identification
Variable structure qualifier Data Unit Identifier (DUI)
Cause of transmission
Common address of ASDU
Information object address
Set of information elements Information Object (IO) no. 1
Time tag
. .
. .
. .
Information object address
Set of information elements Information Object (IO) no. n

Time tag
Figure 3-2
ASDU Frame Format Defined by IEC 61870-5-101
The ASDU frame consists of the following fields:
• Type identification – octet 1 of Data Unit Identifier (DUI) that defines structure, type and
format of the following information objects (clause 7.3 of IEC 60870-5-101 defines all
possible type identification fields)
• Variable structure qualifier - octet 2 of DUI that defines the variable structure qualifier
specified in clause 7.2.2 of IEC 60870-5-101. For example, this qualifier can specify the
number of information objects contained in the ASDU frame
• Cause of transmission – octet 3 of DUI that defines the cause of transmission of the ASDU
frame. All possible causes of transmission are given and described in table 9 of IEC 60870-5-
101.
• Common address of ASDU – octet 4 and optionally 5 of DUI that define the station address
specified in clause 7.2.4 of IEC 60870-5-101. The length of this field (one or two octets) is a
parameter which is fixed per system. This address is a broadcast address (255 or 65535) for
ASDU frames sent in control direction (i.e., from monitoring station to controlled station)
• Information object address – octet 1, optionally 2 and optionally 3 of the Information
Object (IO) that is used as a destination address in control direction (e.g. it determines an IO
in a RTU) and a source address in monitor direction
• Information elements - information elements that are contained in a given information
object. Information element (data) format is precisely defined in clause 7.2.6 of IEC 60870-
5-101 according to the definitions of IEC 60870-5-4. For example, in type 21 ASDU an
-15
information element is a normalized value in the range [-1, +1-2 ];
• Time tag – this is the time tag of an Information object that is seven, three or two octets
long. The time tag is defined in clause 6.8 of IEC 60870-5-4

3-3
It is assumed that two byte addresses are used at the application layer. Thus, the DUI part of an
ASDU frame is 5 octets long. Moreover, information objects have different lengths:
• Measured analog value - 10 octets (2 address octets + 3 time tag octets + 5 analog value
octets)
• Binary state - 6 octets (2 address octets + 3 time tag octets + 1 octet of quality descriptor)
• Tap changer state - 7 octets (2 address octets + 3 time tag octets + 2 octets that describe tap
changer state, i.e., the step position).
Only information objects of the same type can be transmitted in one ASDU frame.

DNP 3.0 Protocol

As with IEC60870-5-101, the DNP 3.0 Basic 4 Document Set defines multilevel protocol data
communication. The Data Link layer protocol supports services for the transport layer protocol,
and the transport layer protocol supports services for the application layer protocol.
At the data link layer, balanced transmission protocol procedures are used. They are carried out
in a hand-shaking mode. A primary station initializes a sequence of orders and the secondary
station responds. In a balanced mode one station can play a role of primary and secondary station
as well. The communication protocol is consistent with IEC 60870-5-1 and IEC 60870-5-2
standards (class FT3 data frames are used).
At the data link layer, LSDU data received from upper layers is converted into data link layer
frame Link Protocol Data Unit - LPDU. Figure 3-3 shows LPDU format. LPDU's maximum
length is 292 octets.

Header Data – information part (Body - LSDU)

Figure 3-3
Format of the LPDU Frame (The Data Link Layer)
The header of the LPDU is 10 octets long. The maximum length of the frame body part is 282
octets (it consists of at most 250 octets of user data divided into 16 data blocks and each data
block is saved with two octets of CRC).
The Data part of the LPDU frame is filled by a transport layer frame. As shown in Figure 3-4,
the transport layer frame (Transport Protocol Data Unit - TPDU) consists of the header
(Transport Header - TH) and the data (information) part (User Data). The length of each TPDU
frame is given in the brackets.

Transport Header (1) Data – information part (User Data (1 - 249))

Figure 3-4
Format of the TPDU Frame (The Transport Layer)

Since the TPDU header is one octet long and the maximum TPDU frame length cannot exceed
250 octets, the length of User Data part of the frame is no longer than 249 octets.

3-4
All messages (i.e., requests and responses) that are exchanged at the application layer by the
DNP 3.0 application layer protocol are called Application Protocol Data Units (APDU). Figure
3-5 shows the APDU format.

APCI ASDU
Request/Response Header Object Data ......... Object Data
Header Header
Figure 3-5
Format of the APDU Frame (The Application Layer)
The APDU frame consists of the header called the Application Protocol Control Information
(APCI) and the data part called the Application Service Data Unit (ASDU). The APCI part
contains control data of the message and the ASDU part contains the body (i.e., user data) of the
message. The APCI is also called the Response Header in case of response messages or the
Request Header in case of request messages. If the APCI contains all required data, there is no
ASDU part in a message.
The length of the ASDU part of the message is not limited.
Figure 3-6 shows the structure of the Request Header of the APDU transmitted from Master to
Slave station. It consists of two 1-octet fields: Application Control - AC, and Function Code -
FC. Figure 3-6 also shows the structure of the Response Header of the APDU transmitted from
Slave to Master station. It consists of four 1-octet fields: Application Control - AC, Function
Code - FC and Slave's status field - Internal Indications (INN).

Request/Response Header

1 octet 1 octet 2 octets

Application Control (AC) Function Code (FC) Internal Indications (INN)

7 6 5 4 0 7 0 7 0

FIR FIN CON 0 0 0 0 0 INN1 INN2

Figure 3-6
APCI Format – The INN Field in Response Header is Marked with the Dashed Line

Figure 3-6 shows that an APCI of each message sent from substations to the M&VSP System
server will consist of four octets.
Data objects contained in a given APDU frame (this is the ASDU part) are preceded by an
Object Header. Figure 3-7 shows the Object Header format. The Object Header defines the type

3-5
of the contained data objects and the way they are transmitted. The data type consists of two
parts: the Object Group and the Object Variation.

Object Header

2 octets 1 octet 1 octet

Object Qualifier Range

first octet second octet 7 6 5 4 3 2 1 0

Object Group Object Variation 0 Index Size Qualifier Code
Figure 3-7
Object Header Format

The Object Header part consists of four octets. One or more Object Header parts can be
contained in a given ASDU.
Data objects have different lengths. For example:
• Measurement data - 4 octets
• Binary state - 1 octet
• Tap changer status - 4 octets

3-6
4
ESTIMATE OF THE REQUIRED CAPACITY OF
COMMUNICATION CHANNELS
In order to evaluate the required capacity of communication channels that enable required data to
be transmitted from selected substations to PSE North (ODM Bydgoszcz), the following
assumptions are taken into account:
• the period of data transmission for each substation is equal to 1 s
• from each substation, the following data will be transmitted:
• 80 binary states
• 39 measurements (U, P, Q)
• 2 tap changer positions
• data compression before transmission is not applied
• IEC 61870-5-101 or DNP 3.0 communication protocol is used.
From Chapter 3, it is clear that the amount of overhead data transmitted using either IEC 61870-
5-101 or DNP 3.0 protocol is different. Therefore, required channel capacity evaluation is carried
out independently for both communication protocols.

IEC 61870-5-101 protocol

The amount of octets having to be transmitted every second from a given substation to the
M&VSP System server at PSE North is calculated below.
Binary states 80 x 6 octets = 480 octets
Measurements 39 x 10 octets = 390 octets
Tap changer positions 2 x 7 octets = 14 octets
---------------------------------------------------------------------------------
Total = 884 octets
In order to transmit theis data it is necessary to use:
• two application layer ASDU frames (binary states)
• two application layer ASDU frames (measurements)
• one application layer ASDU frame (tap changer positions)
The overhead of 5 octets is needed for each ASDU frame. Thus, an overhead of 25 octets is
needed for the application protocol to be employed.
At the data link layer, each ASDU frame will be transmitted as a body of one data link protocol
frame. Each frame introduces an 8 octet overhead. Therefore, an overhead of 40 octets is
introduced at the data link layer.

4-1
As a result, it is necessary to transmit 949 octets (884 + 25 + 40) every second. This means that
the required channel capacity is 10.5 k/bits.

DNP 3.0 protocol

In case the DNP 3.0 protocol is employed, all required data can be transmitted in one application
protocol data frame. The amount of octets that have to be transmitted every second from a given
substation to the system server at PSE North is calculated below.
Binary states 80 x 1 octets + 4 octets of Obj. Header = 84 octets
Measurements and tap changer positions 41 x 4 octets + 4 octets of Obj. Header = 168 octets
APCI header 1 x 4 octets = 4 octets
---------------------------------------------------------------------------------------------------------------------
Total = 256 octets
In order to transmit this data, it is necessary to use two transport layer frames of the total length
equal to 258 octets.
Two frames are needed at the data link layer. The first frame is 292 octets long and the second
frame is 20 octets long. Therefore, it is necessary to transmit 312 octets every second. This
means that the required channel capacity is 3.2 k/bits.

4-2
5
CONCLUSIONS
1. Based on information received from the Department of Data Communications of PSE-
Operator SA in Warszawa, it can be stated that with the exception of the Ostroł ka OST,
Olsztyn 1 OLS and Olsztyn M tki OLM substations, 19.2 k/bits asynchronous channels
can be created between PSE North and substations listed in Table 2. Asynchronous port
availability at both sides of each considered channel has been checked. Also, an available
link capacity for each considered channel has been checked.
2. At the end of the second quarter of 2007, it will be possible to create the channels
connecting Ostroł ka OST, Olsztyn 1 OLS and Olsztyn M tki OLM with PSE North.
3. The evaluation of the required capacity of required communication channels carried out
in chapter 4 shows that in case the DNP 3.0 protocol is applied, the required channel
capacity cannot be less than 3.2 k/bits. This required capacity is three times lower than if
the IEC 60870-5-101 protocol is employed. Therefore, the minimum channel capacity
should not be lower than 19.2 k/bits.

5-1
Export Control Restrictions The Electric Power Research Institute (EPRI)
Access to and use of EPRI Intellectual Property is The Electric Power Research Institute (EPRI),
granted with the specific understanding and with major locations in Palo Alto, California;
requirement that responsibility for ensuring full Charlotte, North Carolina; and Knoxville,
compliance with all applicable U.S. and foreign export Tennessee, was established in 1973 as an
laws and regulations is being undertaken by you and independent, nonprofit center for public interest
your company. This includes an obligation to ensure energy and environmental research. EPRI brings
that any individual receiving access hereunder who is together members, participants, the Institute's
not a U.S. citizen or permanent U.S. resident is scientists and engineers, and other leading
permitted access under applicable U.S. and foreign experts to work collaboratively on solutions to the
export laws and regulations. In the event you are challenges of electric power. These solutions
uncertain whether you or your company may lawfully span nearly every area of electricity generation,
obtain access to this EPRI Intellectual Property, you delivery, and use, including health, safety, and
acknowledge that it is your obligation to consult with environment. EPRI's members represent over
your company’s legal counsel to determine whether 90% of the electricity generated in the United
this access is lawful. Although EPRI may make States. International participation represents
available on a case-by-case basis an informal nearly 15% of EPRI's total research,
assessment of the applicable U.S. export classification development, and demonstration program.
for specific EPRI Intellectual Property, you and your
company acknowledge that this assessment is solely Together…Shaping the Future of Electricity
for informational purposes and not for reliance
purposes. You and your company acknowledge that it
is still the obligation of you and your company to make
your own assessment of the applicable U.S. export
classification and ensure compliance accordingly. You
and your company understand and acknowledge your
obligations to make a prompt report to EPRI and the
appropriate authorities regarding any access to or use
of EPRI Intellectual Property hereunder that may be in
violation of applicable U.S. or foreign export laws or
regulations.

© 2007 Electric Power Research Institute (EPRI), Inc. All rights reserved.
Electric Power Research Institute, EPRI, and TOGETHER•SHAPING THE
FUTURE OF ELECTRICITY are registered service marks of the Electric
Power Research Institute, Inc.

Printed on recycled paper in the United States of America 1014781

ELECTRIC POWER RESEARCH INSTITUTE

3420 Hillview Avenue, Palo Alto, California 94304-1395 • PO Box 10412, Palo Alto, California 94303-0813 • USA
800.313.3774 • 650.855.2121 • [email protected] • www.epri.com