Professional Documents
Culture Documents
Siprotec 5 IEC61850 Pixit, Pics, Tics: Preface Applications IEC 61850 Conformance Statements
Siprotec 5 IEC61850 Pixit, Pics, Tics: Preface Applications IEC 61850 Conformance Statements
Siprotec 5 IEC61850 Pixit, Pics, Tics: Preface Applications IEC 61850 Conformance Statements
Preface
Contents
SIPROTEC 5 Applications 1
IEC61850
IEC 61850 Conformance Statements 2
PIXIT, PICS, TICS
V1.1
Manual
C53000-G5040-C013-2
SIP5xx_PIXIT_A2_V051000_en.book Page 2 Wednesday, October 17, 2012 1:15 PM
This document has been subjected to rigorous technical review Copyright © Siemens AG 2012. All rigths reserved.
before being published. It is revised at regular intervals, and any The disclosure, duplication, distribution and editing of this
modifications and amendments are included in the subsequent document, or utilization and communication of the content are not
issues. The content of this document has been compiled for permitted, unless authorized in writing. All rights, including rights
information purposes only. Although Siemens AG has made best created by patent grant or registration of a utility model or a design,
efforts to keep the document as precise and up-to-date as possible, are reserved.
Siemens AG shall not assume any liability for defects and damage
which result through use of the information contained herein.
Registered Trademarks
This content does not form part of a contract or of business
relations; nor does it change these. All obligations of Siemens AG SIPROTEC® and DIGSI® are registered trademarks of
are stated in the relevant contractual agreements. SIEMENS AG. An unauthorized use is illegal.
Siemens AG reserves the right to revise this document from time to All other designations in this document can be trademarks whose
time. use by third parties for their own purposes can infringe the rights of
the owner.
Document Release: 02
Release 02.2012
Product version: V1.1
SIP5xx_PIXIT_A2_V051000_en.book Page 3 Wednesday, October 17, 2012 1:15 PM
Preface
In this Manual, you will find the Specification of the applications of the IEC 61850 interface
Target audience
This manual is intended mainly for all persons who configure, parameterize and operate a SIPROTEC 5 device.
Scope of validity
Standards
This manual has been created according to the ISO 9001 quality standards.
Additional support
For questions about SIPROTEC IEC 61850 interface, please contact your Siemens sales representative.
Hotline
Training courses
If you are interested in our current training program, please contact our training center:
Siemens AG
Siemens Power Academy TD
Humboldtstr. 59
90459 Nuremberg
Germany
Preface
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 Association model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 Server model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4 Data set model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.5 Substitution model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.6 Setting group control model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.7 Reporting model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.8 Generic substation event model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.9 Control model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.10 Time and time synchronisation model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.11 File transfer model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.12 General items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.13 TICS - Technical Issues Implementation Conformance Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.13.1 TISSUES Edition 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.13.2 TISSUES Edition 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Contents
1 Applications
Contents
This chapter specifies the protocol implementation extra information for testing (PIXIT) of the IEC 61850 inter-
face in SIPROTEC 5.
1.1 General 8
Applications
1.1 General
1.1 General
This manual specifies the protocol implementation extra information for testing (PIXIT) of the IEC 61850 inter-
face in SIPROTEC 5.
It is based on the service subset definition given in the protocol implementation conformance statement (PICS),
which is specified within the user manual SIPROTEC 5 IEC61850.
Together with the PICS and the MICS the PIXIT forms the basis for a conformance test according to
IEC 61850-10.
The mapping between the IEC 61850 server data model and the SIPROTEC specific data is specified in DIGSI.
Applications
1.2 Association model
Where
Y means: as defined within the ICD-File
ANY means: any value accepted
As7 What is the maximum and minimum MMS Max MMS PDU size 65536
PDU size ? Min MMS PDU size
As8 What is the maximum startup time after a Typical 100 seconds
power supply interrupt ? The value depends on the size of the object directory
<additional items>
Applications
1.3 Server model
Source:
Y Process
Y Substituted
Y Test
Y OperatorBlocked
Sr2 Which status value (ST) quality bits are sup- Validity:
ported (can be set by server) ? Y Good,
Y Invalid,
N Reserved,
Y Questionable
N BadReference
Y Oscillatory
Y Failure
Y OldData
N Inconsistent
N Inaccurate
Source:
Y Process
Y Substituted
Y Test
Y OperatorBlocked
Sr3 What is the maximum number of data Not restricted; depends on the max. MMS PDU size given
values in one GetDataValues request ? above.
Sr4 What is the maximum number of data Not restricted; depends on the max. MMS PDU size given
values in one SetDataValues request ? above. No Data Attribute within our object directory is writ-
able with the service SetDataValues.
<additional items>
What is the behaviour of the device by GetAllDataValues is not supported without functional con-
GetAllDataValues? straint indication.
The functional contraints SG, SP and SE can not be
readen as functional contraint logical nodes;
for those functional constraint only FCD's and FCDA's
access are supported: GetDataValues, GetSGValues.
Applications
1.4 Data set model
Ds1 What is the maximum number of data ele- Not limited by an internal configuration parameter. It
ments in one data set? depends on the available memory.
(compare ICD setting)
Ds2 How many persistent data sets can be 30 data sets for each LD. It depends on the available
created by one or more clients ? memory.
Ds3 How many non-persistent data sets can be 10 data sets. It depends on the available memory.
created by one or more clients ?
additional items:
Applications
1.5 Substitution model
additional items:
What is the behavoir of the substitution As long as subEna is true, further substitution can be per-
model when subEna is true for the object? formed without having to disable the substitution first.
Applications
1.6 Setting group control model
Sg1 What is the number of supported setting There is at least one setting group control block in the
groups for each logical device (compare device available.
NumSG in the SGCB)? The number of supported setting groups is from 1 or 8, it
depends on the given configuration.
Specified in the ICD-File.
Sg2 What is the effect of when and how the non- The settings will be available after a restart since they are
volatile storage is updated ? non-volatile, as long as the setting group editing succeed.
(compare IEC 61850-8-1 $16.2.4)
Sg3 Can multiple clients edit the same setting Y but not at the same time
group?
Sg4 What happens if the association is lost while The setting group edition is cancelled
editing a setting group?
Sg5 Is EditSG value 0 allowed? Y It cancels the current editing and unreserve the SGCB.
<additional items>
What happens if during the editing of a The current edit buffer is overwritten with the value con-
setting goup, the EditSG is set again by the tained in the setting group. The edited value that were not
client that performs the editing confirmed are lost.
What is the behaviour of the device by GetAllDataValues is not supported without functional
GetAllDataValues? constraint indication.
The functional contraints SG, SP and SE can not be
readen as functional contraint logical nodes;
for those functional constraint only FCD's and FCDA's
access are supported: GetDataValues, GetSGValues.
Applications
1.7 Reporting model
Rp5 Multi client URCB approach Each URCB is visble to all clients
(Compare IEC 61850-7-2 §14.2.1)
Rp7 What is the buffer size for each BRCB or About 1 MB are available for the buffering.
how many reports can be buffered ? Each BRCB has an extension attribute Memory that
display the percentage of those 1 MB that have been re-
served/forseen for its own entries.
Amount is 1 MB/Number of all BRCB‘s
Rp8 Pre-configured RCB attributes that cannot For Buffered and Unbuffered:
be changed online when RptEna = FALSE
(see also the ICD report settings) All pre-configured RCB attributes can be changed online
when RptEna = FALSE
additional items:
Applications
1.7 Reporting model
Dynamic URCB reservation after an abort of Reservation of the URCB is lost. After a re-establishment
the client/server association of the association the URCB reservation has to be
renewed by the client. This behavior is implemented to
avoid unnecessary memory residuals if temporarily client
associations (e.g. for maintenance) are established.
Optional use of a flow control for transmit- As specified in the IEC61850-7-2, transmission of entries
ting history of a BRCB may required some times, depending of the amount of
entries that have to be transmitted.
Therefore, the SIPROTEC has an optional flow control
feature to accelerate the transmission of the entries: each
BRCB has an extended attribute MaxOutReports that can
be set from the associated-client to change the transmmi-
sion strategy of the entries. Those attributes are located in
VMD variables.The number ordered will then be transmit-
ted as long as they exist in the buffer; the server then reset
the attribute to 0 and wait for the client to set it again in
order to continue the history transmission with MaxOutRe-
ports entries. The attribute only influences the flow control
of entries while dealing with the history, and not after the
history transmission has completed.
Applications
1.8 Generic substation event model
Go3 What is the behavior when the GOOSE DUT will send GOOSE with NdsCom = TRUE as long as
publish configuration is incorrect the minimum required configuration is available
(dstAddress)
Go4 When is a subscribed GOOSE marked as When message does not arrive by 1 · TAL
lost ?
(TAL = time allowed to live value from the
last received GOOSE message)
Go5 What is the behavior when one or more sub- Last received data as mark as invalid and resend to the ap-
scribed GOOSE message isn’t received or plication
syntactically incorrect ?
(missing GOOSE)
Go6 What is the behavior when a subscribed When a given state Number n, sequence Number l is re-
GOOSE message is out-of-order ? ceived, only the following telegrams will be accepted:
n, l+1;
n, l+2;
n+1, 0;
n+1,1,
1,0
All other telegramms are ignored
Go7 What is the behavior when a subscribed The repetition will be ignored
GOOSE message is duplicated ?
Go8 Does the device subscribe to GOOSE mes- Y with the VLAN tag
sages with/without the VLAN tag? Y without the VLAN tag
Applications
1.8 Generic substation event model
additional items:
Interpretation of GOOSE messages at sub- 1. Received GOOSE data objects without assigned
scriber side quality attribute are interpreted as invalid.
2. Received GOOSE data objects which quality attribute
are set to questionable are changed to invalid.
GOOSE subscriber behavior in case of After a GOOSE multicast application association has been
missing GOOSE messages interrupted, the reception of a valid GOOSE telegram is re-
quired to validate the state of this GOOSE association
again.
However, the IED tolerates a missing telegram as long as
the next telegram (expected n, received n+1) is received
within the time allowed to live time out detection (the time
allowed to live timeout detection occurs after 1 · TAL).
What is the behavior when a GOOSE The Rx-mismatch counter available at the diagnostic
header parameter is mismatching with the buffer is incremented.
expected one? The received telegram with the mismatched attribute will
(datSet, goID, confRev, numDatSetEntries, be discarted: it has not been subscribed. In that case only
number of allData) the timeout detection will set the data to invalid.
What is the behavior when there is an out- The confRev attribute in the header guarantees that the
of-order entry in the allData? allData entries are in the correct order. Therefore, it’s nec-
essary to check the confRev attribute. There is no chance
to detect a semantic out-of-order if the types are identical.
What is the behavior when numDatSetEn- The telegram is discarded since it is corrupt (not well
tries and number of allData are inconsis- formed). The data objects are declared invalid.
tent?
Applications
1.9 Control model
Ct5 What is the behavior of the DUT when the The request will be proceed if the Beh of the logical node
test attribute is set in the SelectWithValue where the controlled object is located is Test.
and/or Operate request Otherwise, it will be discarted as "Blocked-by-mode".
Ct6 What are the conditions for the time (T) at- Time attribute is not relevant
tribute in the SelectWithValue and/or
Operate request
Ct10 How to force a “test-not-ok” respond with Test and logical node Beh do not match
SelectWithValue request? Wrong orCat
Ct11 How to force a “test-not-ok” respond with When the control object has already been selected
Select request?
Applications
1.9 Control model
Ct12 How to force a “test-not-ok” respond with DOns: Test and logical node Beh do not match
Operate request? Wrong orCat
SBOns: Test and logical node Beh do not match
Wrong orCat
DOes: Test and logical node Beh do not match
Wrong orCat
SBOes: Test and logical node Beh do not match
Wrong orCat
Ct14 What happens if the orCat value is not sup- DOns: oper.Resp-, not-supported
ported? SBOns: oper.Resp-, not-supported
DOes: oper.Resp-, not-supported
SBOes: SelectWithValue.Resp- Not-supported
Ct18 Is for SBOes the internal validation per- SelectWithValue and Operate
formed during the SelectWithValue and/or
Operate step?
additional items:
Inconsistency between Select and Oper or cancel will be acknowledged with negative re-
(Oper or cancel) sponse if inconsistencies to the select request are detect-
ed.
The following attributes will not be checked in this case:
T (Time)
The controlled object returns then in state "unselected"
Applications
1.9 Control model
Format of the control time stamp attribute ? Time stamp instead of EntryTime
acc. to the 7-2 Errata List.
Negative response for select request could If the logical Mod and the Test attribute do not match.
be performed only If the selection is already done.
If the service parameter of Select are not supported (e.g.
wrong or Cat)
What is the behaivor of the control state ma- For SBOes and SBOns:
chines when the association is lost with the If the current state is “Ready”, then the selection ends.
client that issued a successfull control?
Applications
1.10 Time and time synchronisation model
Tm2 Describe the behavior when the time syn- The quality attribute “ClockNotSychronized” will be set to
chronization signal/messages are lost TRUE after a configured time period
Tm3 When is the time quality bit "Clock failure" Clock failure is set when the device internal clock drifts
set? from the external synchonization
Tm4 When is the time quality bit "Clock not syn- The “ClockNotSynchronized” attribute is set to TRUE as
chronised” set? long as no time synchronization is established.
Tm7 Which attibutes of the SNTP response N Leap indicator not equal to 3?
packet are validated? Y Mode is equal to SERVER
Y OriginateTimestamp is equal to value sent by the
SNTP client as Transmit Timestamp
Y RX/TX timestamp fields are checked for
reasonableness
Y SNTP version 3 and/or 4
Y Other (describe):
Stratum is not KISS OF DEATH
Clock of STNP Server is synchronized
Response comes from the server to which the request
was sent
additional items:
Applications
1.11 File transfer model
Ft7 Is the wild char supported MMS fileDirectory Y only as *; not as name completion wild card
request?
additional items:
Applications
1.12 General items
additional items:
What is the type of the attribute actVal in the The type is integer 32 (INT32).
BCR (Binary Counter Reading) CDC?
What is the behaviour of the Device by GetAllDataValues is not supported without functional con-
GetAllDataValues? straint indication.
Applications
1.13 TICS - Technical Issues Implementation Conformance Statement
Applications
1.13 TICS - Technical Issues Implementation Conformance Statement
Applications
1.13 TICS - Technical Issues Implementation Conformance Statement
1) No impact as long as the IED Name and the logical device inst have together a length smaller than 13 char.
Contents
This chapter describes conformity with IEC 61850. It does not describe the entire standard but only parts in
which there is a choice in the services.
This section on using the ISO application (application profile) and transport profiles (T profile) describes the
various stack profiles. An ISO application profile is a set of specifications and declarations regarding the top 3
layers of the ISO/OSI reference model (i.e. the application, presentation, and session layers). The T profile is
a set of specifications and declarations regarding the lower 4 layers (i.e. transport, network, data link, and phys-
ical layers).
A and T profiles can be combined in various ways to form different types of services and information items that
can be exchanged. The services specified in Part 7-2 of the IEC 61850 standard are mapped onto 4 different
combinations of the profiles. These 4 combinations are used for
• Client/server services,
• GOOSE/GSE management services,
• GSSE services,
• Time synchronization,
• Services for measured value sampling.
The tables refer to Part 7 of the standard and the corresponding information must be contained in the PICS.
This section describes the conformance statements. The standard groups them together under the term Pro-
tocol Implementation Conformance Statement (PICS).
Mandatory services
Please note that a number of services are prescribed and must be implemented to comply with the standard.
Only the optional services and protocols are listed here because they constitute freedom of implementation.
None of the mandatory services is explicitly explained here. Please refer to the standard IEC 61850, Part 8-1.
Time
T1 Time resolution of internal clock 10 (1 ms) nearest negative power of 2 in seconds
T2 Time accuracy of internal clock T0 (10 ms)
Y T1 (1 ms)
N T2 (100 μs)
N T3 (25 μs)
N T4 (4 μs)
N T5 (1 μs)
T profile support
Please refer to the services of Part 7 to see whether these profiles are supported. No distinction is
made between A and T profiles there because the definition only refers to the application.
These services are all identified as mandatory and are therefore implemented in compliance with the standard.
Client-CR Server-CR
MMS Service Supported CBB value/ value/
realized realized
range range
status Y
getNameList Y
identify Y
rename N
read Y
write Y
getVariableAccessAttributes Y
defineNamedVariable N
defineScatteredAccess N
getScatteredAccessAttributes N
deleteVariableAccess N
defineNamedVariableList Y
getNamedVariableListAttributes Y
deleteNamedVariableList Y
defineNamedType N
getNamedTypeAttributes N
deleteNamedType N
input N
output N
takeControl N
relinquishControl N
defineSemaphore N
deleteSemaphore N
reportPoolSemaphoreStatus N
reportSemaphoreStatus N
initiateDownloadSequence N
downloadSegment N
terminateDownloadSequence N
initiateUploadSequence N
1. MMS. Manufacturing Message Specification, is defined in standard ISO 9506 and was defined for indus-
trial automation systems ranging from simple to complex.
Client-CR Server-CR
MMS Service Supported CBB value/ value/
realized realized
range range
uploadSegment N
terminateUploadSequence N
requestDomainDownload N
requestDomainUpload N
loadDomainContent N
storeDomainContent N
deleteDomain N
getDomainAttributes Y
createProgramInvocation N
deleteProgramInvocation N
start N
stop N
resume N
reset N
kill N
getProgramInvocationAttributes N
obtainFile N
devineEventCondition N
deleteEventCondition N
getEventConditionAttributes N
getEventConditionStatus N
getEventConditionMonitoring N
triggerEvent N
defineEventAction N
deleteEventAction N
alterEventEnrollment N
reportEventEnrollmentstatus N
getEventEnrollmentAttributes N
acknowledgeEventNotification N
getAlarmSummary N
getAlarmEnrollmentSummary N
readJournal N
writeJournal N
initializeJournal N
reportJournalStatus N
createJournal N
deleteJournal N
Client-CR Server-CR
MMS Service Supported CBB value/ value/
realized realized
range range
fileOpen Y
fileRead Y
fileClose Y
fileRename N
fileDelete N
fileDirectory Y
unsolicitedStatus N
informationReport Y
eventNotification N
attachToEventCondition N
attachToSemaphore N
conclude Y
cancel Y
getDataExchangeAttributes N
exchangeData N
defineAccessControlList N
getAccessControlListAttributes N
reportAccessControlledObjects N
deleteAccessControlList N
alterAccessControl N
reconfigureProgramInvocation N
Client-CR Server-CR
MMS Service Supported CBB value/ value/
realized realized
ranged range
STR1 Y
STR2 Y
VNAM Y
VALT Y
VADR Y
VSCA N
TPY Y
VLIS Y
REAL N
CEI N
Client-CR Server-CR
AlternateAccessSelection value/ value/
realized realized
ranged ranged
accessSelection Y
component Y
index Y
indexRange Y
allElements N
alternateAccess Y
selectAccess Y
component Y
index Y
indexRange Y
allElements N
Client-CR Server-CR
VariableAccessSpecification value/ value/
realized realized
range range
listOfVariable Y
variableSpecification Y
alternateAccess Y
variableListName Y
Client-RC Server-CR
VariableSpecification value/ value/
realized realized
range range
name Y
address N
variableDescription Y
scatteredAccessDescription N
invalidated N
Client-CR Server-CR
Read value/ value/
realized realized
range range
Request
specificationWithResult Y
variableAccessSpecification Y
Response
variableAccessSpecification Y
listOfAccessResult Y
Client-CR Server-CR
GetVariableAccessAttributes value/ value/
realized realized
range range
Request
name Y
address N
Response
mmsDeletable Y
address N
typeSpecification Y
Client-CR Server-CR
GetNamedVariableListAttributes value/ value/
realized realized
range range
Request
IObjectName Y
Respose
mmsDeletable Y
listOfVariable Y
variableSpecification Y
alternateAccess N
Client-CR Server-CR
DeleteNamedVariableList value/ value/
realized realized
range range
Request
Scope Y
listOfVariableListName Y
domainName Y
Response
numberMatched Y
numberDeleted Y
DeleteNamedVariableList-Error Y
This statement contains the description of all objects that are provided by a device and is especially important
if devices are connected to a central system that supplies data to certain applications via the objects provided
by the device.
In the case of SIPROTEC 5, this document depends on both the device type and the defined user objects and
can therefore not be a permanent part of the manual. It is therefore generated from DIGSI.
Generation in DIGSI 5
Generation is selected in the device processing. Select the device and open via context menue Export Æ
IEC 61850 data formats:MICS the dialog to enter an editable filename under which the MICS document to be
generated will be stored ( XML file and the corresponding files MICS.css and MICS.xslt).
The XML file can be opened, viewed and printed within a web browser.
The document is generated with the correct version and device type data. It shows the model implementation
of the SIPROTEC 5 device. The whole document is shown in a hyperlinked table of contents. The MICS is a
readable form of the current mapping of a device on IEC 61850.
In addition to the MICS, an ICD file and IID file (XML files) are created which describes the mapping of a device.
Those ICD/IID files are used by the System Configurator, or can be imported into the system configurators of
other manufacturers, in order to integrate these devices into the communication.