SE-330 IEC 61850 Communication Conformance Statement

3714 Kinnear Place
Saskatoon, SK
Canada
S7P 0A6
Ph: (306) 373-5505
Fx: (306) 374-2245 www.littelfuse.com/relayscontrols
SE-330 IEC 61850 COMMUNICATION CONFORMANCE STATEMENT
REVISION 0-A-072314
Copyright © 2014 by Littelfuse Startco
All rights reserved.
SE-330 IEC 61850 Communication Conformance Statement
Page i
Rev. 0-A-072314
TABLE OF CONTENTS
SECTION
1
PAGE
Introduction .................................................................................................................................................................. 1
1.1 Scope .............................................................................................................................................................................. 1
1.2 Terms and Abbreviations............................................................................................................................................... 1
2
PICS Details .................................................................................................................................................................. 1
2.1 ASCI Basic Conformance Statement ............................................................................................................................ 2
2.2 ASCI Models Conformance Statement......................................................................................................................... 2
2.3 ASCI Service Conformance Statement......................................................................................................................... 4
2.4 Protocol Profile Support ................................................................................................................................................ 7
3
SCL Conformance Degree .......................................................................................................................................... 7
4
MICS Details................................................................................................................................................................. 8
4.1 Classes of Logical Nodes Supported in the Server....................................................................................................... 8
4.2 Logical Nodes Extensions ........................................................................................................................................... 11
4.2.1 New Logical Nodes ......................................................................................................................................... 11
4.2.2 Extended Logical Nodes.................................................................................................................................. 11
4.3 Common Data Class Extensions ................................................................................................................................. 11
4.3.1 New Common Data Classes ............................................................................................................................ 11
4.3.2 Extended Common Data Classes .................................................................................................................... 11
4.4 Enum Types Extensions .............................................................................................................................................. 11
4.4.1 New Enum Types............................................................................................................................................. 11
4.4.2 Extended Enum Types ..................................................................................................................................... 11
5
PIXIT Details .............................................................................................................................................................. 12
5.1 PIXIT for Association Model ...................................................................................................................................... 12
5.2 PIXIT for Server Model............................................................................................................................................... 13
5.3 PIXIT for Data Set Model ........................................................................................................................................... 14
5.4 PIXIT for Reporting Model ......................................................................................................................................... 14
5.5 PIXIT for Generic Substation Events Model (GOOSE) ............................................................................................ 16
5.6 PIXIT for GOOSE Performance ................................................................................................................................. 18
5.7 PIXIT for Control Model ............................................................................................................................................. 18
5.8 PIXIT for Time Synchronization ................................................................................................................................ 20
5.9 PIXIT for File Transfer Model .................................................................................................................................... 21
6
TICS Details ................................................................................................................................................................ 22
6.1 Introduction .................................................................................................................................................................. 22
6.2 Mandatory IntOp Tissues ............................................................................................................................................ 22
6.3 Optional IntOp Tissues ................................................................................................................................................ 24
6.4 Other Implemented Tissues ......................................................................................................................................... 24
Appendix A Document Revision History............................................................................................................................ 25
SE-330 IEC 61850 Communication Conformance Statement
Page 1
Rev. 0-A-072314
1. INTRODUCTION
1.1 SCOPE
The purpose of this document is to declare the conformance of the SE-330 IEC 61850 server to the IEC 61850 standard.
1.2 TERMS AND ABBREIVATIONS
ACSI
Abstract Communication Service Interfaces
BDA
Basic Data Attribute (Not Structured)
DA
Data Attributes
DO
DATA in IEC 61850-7-2, Data Object Type or Instance
FCD
Functionally Constrained Data
FCDA
Functionally Constrained Data Attribute
ID
Identifier
IED
Intelligent Electronic Device
LD
Logical Device
LN
Logical Node
MSV
Multicast Sampled Value
RCB
Report Control Block
GCB
GOOSE Control Block or GSSE Control Block
SCL
Substation Configuration Language
SCSM
Specific Communication Service Mapping
XML
Extensible Markup Language
GSSE
Generic Substation State Events
GOOSE
Generic Object Oriented Substation Events
SCD
Substation Configuration Description File
ICD
IED Configuration Description
CID
Configured IED Description
PICS
Protocol Implementation Conformance Statement
MICS
Model Implementation Conformance Statement
PIXIT
Protocol Implementation eXtra Information for Testing
TICS
Tissue Implementation Conformance Statement
2. PICS DETAILS
Conformance of the IEC 61850 server in SE-330 relays:
Supported Models and Services
Unsupported
Not applicable to Server/publisher
Yes
No
--
SE-330 IEC 61850 Communication Conformance Statement
Page 2
Rev. 0-A-072314
2.1 ASCI BASIC CONFORMANCE STATEMENT
Basic ASCI Conformance
Client/
Subscriber
Client – Server Roles
Server Side (of Two-Party Application
B11
Association)
B12
Server/
Publisher
Comment
Yes
Client Side (of Two-Party Application
Association)
N/A
SCSMs Supported
B21
SCSM: IEC 61850-8-1 Used
Yes
B22
SCSM: IEC 61850-9-1 Used
No
B23
SCSM: IEC 61850-9-2 Used
No
B24
SCSM: Other
N/A
Generic Substation Event Model (GSE)
B31
Publisher Side
Yes
B32
Yes
Subscriber Side
Transmission of Sampled Value Model (SVC)
B41
Publisher Side
No
B42
No
Subscriber Side
2.2 ASCI MODELS CONFORMANCE STATEMENT
ASCI Model Conformance
Client/
Subscriber
Server/
Publisher
M1
Logical Device
Yes
M2
Logical Node
Yes
M3
Data
Yes
M4
Data Set
Yes
M5
Substitution
No
M6
Setting Group Control
No
Reporting
M7
Buffered Report Control
Yes
M7-1
Sequence-Number
Yes
M7-2
Report-Time-Stamp
Yes
Comment
One LD Instance
Only standard LN types defined in
Part 7-4.
Only standard object types defined
in Part 7-3, 7-4.
Mandatory objects and attributes
and selected optional objects and
attributes.
Three pre-defined persistent data
sets, not configurable via SCL.
Supports dynamically created
persistent and non-persistent data
sets.
Data set member selection
restricted to ST and MX FCs.
SE-330 IEC 61850 Communication Conformance Statement
Page 3
Rev. 0-A-072314
ASCI Models Conformance Statement (continued)
ASCI Model Conformance
Client/
Subscriber
Server/
Publisher
M7-3
Reason-for-Inclusion
Yes
M7-4
Data-Set-Name
Yes
M7-5
Data-Reference
Yes
M7-6
Buffer-Overflow
Yes
M7-7
entryID
Yes
M7-8
BufTm
Yes
M7-9
IntgPd
Yes
M7-10
GI
Yes
M7-11
Conf-Revision
Yes
M8
Unbuffered Report Control
Yes
M8-1
Sequence-Number
Yes
M8-2
Report-Time-Stamp
Yes
M8-3
Reason-for-Inclusion
Yes
M8-4
Data-Set-Name
Yes
M8-5
Data-Reference
Yes
M8-6
BufTm
Yes
M8-7
IntgPd
Yes
M8-8
GI
Yes
M8-9
Conf-Revision
Yes
Logging
M9
Log control
No
M10
Log
No
Other
M11
Control
Yes
M12
GOOSE
Yes
M13
GSSE
No
M14
Multicast SVC
No
M15
Unicast SVC
No
M16
Time
Yes
M17
File Transfer
No
Comment
Type 1B, Class P2/2, < 20ms
SE-330 IEC 61850 Communication Conformance Statement
Page 4
Rev. 0-A-072314
2.3 ASCI SERVICE CONFORMANCE STATEMENT
ASCI Service Conformance
Server
S1
ServerDirectory
Application Association
S2
Associate
Client/
Subscriber
Server/
Publisher
Yes
Yes
S3
Abort
Yes
S4
Release
Yes
Logical Device
S5
LogicalDeviceDirectory
Yes
Logical Node
S6
LogicalNodeDirectory
Yes
GetAllDataValues
Yes
Data
S8
GetDataValues
Yes
S9
SetDataValues
Yes
S10
GetDataDirectory
Yes
S11
GetDataDefinition
Yes
Data set
S12
GetDataSetValues
Yes
S7
Comment
S13
SetDataSetValues
Yes
S14
CreateDataSet
Yes
S15
DeleteDataSet
Yes
S16
GetDataSetDirectory
Yes
Substitution
S17
SetDataValues
No
Setting Group Control
S18
SelectActiveSG
No
S19
SelectEditSG
No
S20
SetSGValues
No
S21
ConfirmEditSGValues
No
Alternate access is also supported.
All values of a particular logical
node can be obtained through the
use of a single MMS read request
with the logical node name as the
MMS variable name.
Supported, but all dataset values
are read only attributes from ST
and MX functional constraints so
values cannot be set.
SE-330 IEC 61850 Communication Conformance Statement
ASCI Service Conformance Statement (continued)
ASCI Service Conformance
Client/
Subscriber
Server/
Publisher
S22
GetSGValues
Yes
S23
GetSGCBValues
No
Reporting
Buffered Report Control Block (BRCB)
S24
Report
Yes
S24-1
Data-Change (dchg)
Yes
S24-2
Qchg-Change (qchg)
Yes
S24-3
Data-Update (dupd)
Yes
S25
GetBRCBValues
Yes
S26
SetBRCBValues
Yes
Unbuffered Report Control Block (URCB)
S27
Report
Yes
S27-1
Data-Change (dchg)
Yes
S27-2
Qchg-Change (qchg)
Yes
S27-3
Data-Update (dupd)
Yes
S28
GetURCBValues
Yes
S29
SetURCBValues
Yes
Logging
Log Control
S30
GetLCBValues
S31
No
SetLCBValues
No
QueryLogByTime
No
S33
QueryLogAfter
No
S34
GetLogStatusValues
No
Generic Substation Event Model (GSE)
GOOSE Control Block
S35
SendGOOSEMessage
Yes
Log
S32
S36
GetGoReference
No
S37
GetGOOSEElementNumber
No
S38
GetGoCBValues
Yes
S39
SetGoCBValues
Yes
Comment
Page 5
Rev. 0-A-072314
SE-330 IEC 61850 Communication Conformance Statement
Page 6
Rev. 0-A-072314
ASCI Service Conformance Statement (continued)
ASCI Service Conformance
GSSE Control Block
S40
SendGSSEMessage
Client/
Subscriber
Server/
Publisher
No
S41
GetGsReference
No
S42
GetGSSEElementNumber
No
S43
GetGsCBValues
No
S44
SetGsCBValues
No
Transmission of Sampled Value Model (SVC)
Multicast SVC
S45
SendMSVMessage
No
S46
GetMSVCBValues
No
S47
SetMSVCBValues
No
Unicast SVC
S48
SendUSVMessage
No
S49
GetUSVCBValues
No
S50
SetUSVCBValues
No
Control
S51
Select
No
S52
SelectWithValue
No
S53
Cancel
No
S54
Operate
Yes
S55
Command-Termination
No
S56
TimeActivated-Operate
No
File Transfer
S57
GetFile
No
S58
SetFile
No
S59
DeleteFile
No
S60
GetFileAttributeValues
No
Time Resolution of Internal Clock
10 bits
T2
Time Accuracy of Internal Clock
T1: 1ms
T3
Supported TimeStamp Resolution
1 ms
T4
TimeSynchronization
Yes
Time
T1
Comment
Direct-operate model supported.
SE-330 IEC 61850 Communication Conformance Statement
Page 7
Rev. 0-A-072314
2.4 PROTOCOL PROFILE SUPPORT
Client/
Subscriber
A-Profile
Server/
Publisher
Comment
A1
Client/Server A-Profile
Yes
A2
GOOSE/GSE Management A-Profile
Yes
A3
GSSE A-Profile
No
A4
TimeSync A-Profile
Yes
SNTP
Server/
Publisher
Comment
Client/
Subscriber
T-Profile
T1
TCP/IP T-Profile
Yes
T2
OSI T-Profile
No
T3
GOOSE/GSE T-Profile
Yes
T4
GSSE T-Profile
No
T5
TimeSync T-Profile
Yes
Performance Class T1 (1 ms
Accuracy)
Server/
Publisher
Comment
3. SCL CONFORMANCE DEGREE
SCL Conformance Degree
Client/
Subscriber
SCL.1
SCL File for Implementation Available Offline
Yes
SCL.2
SCL File Available From Implementation
Online
No
SCL.3
SCL Implementation Reconfiguration Supported
Online
No
Supported ASCI Services for SCL.2 and SCL.3
Client/
Subscriber
Server/
Publisher
GetFileAttributeValues
No
GetFile
No
SetFile
No
DeleteFile
No
GetDataValues
No
SetDataValues
No
SCL Control Block
No
SCL File Structure
No
Remote Creation of SCL File
No
Comment
SE-330 IEC 61850 Communication Conformance Statement
Additional MMS Services for SCL.2 and SCL.3
Client/
Subscriber
Server/
Publisher
GetCapabilityList
Yes
GetDomainAttributes
Yes
LoadDomainContent
No
StoreDomainContent
No
Definition of SCL Control Block (IEC61850-8-1
Component Name)
Client/
subscriber
Server/
publisher
Validate
No
ValState
No
Activate
No
Comment
Comment
4. MICS DETAILS
4.1 CLASSES OF LOGICAL NODES SUPPORTED IN THE SERVER
The following table shows the Common Data Class Logical Nodes that are supported by the SE-330.
LN
Name
LN Description
Server
L - System Logical Nodes
LLN0
Common Logical Node Zero
Yes
LPHD
Physical Device
Yes
P – Protection Functions
PDIF
Differential
PDIR
Directional
PDIS
Distance
PDOP
Directional Over Power
PDUP
Directional Under Power
PFRC
Rate of Frequency Change
PHAR
Harmonic Restraint
PHIZ
Ground Detector
PIOC
Instantaneous Over Current
PMRI
Motor Restart Inhibition
PMSS
Motor Starting Time Supervision
POPF
Over Power Factor
PPAM
Phase Angle Measuring
PSCH
Protection Scheme
Comment:
Page 8
Rev. 0-A-072314
SE-330 IEC 61850 Communication Conformance Statement
Page 9
Rev. 0-A-072314
Classes of Logical Nodes Supported in the Server (continued)
LN
Name
LN Description
PSDE
Sensitive Directional Earth Fault
PTEF
Transient Earth Fault
PTOC
Time Over Current
PTOF
Over Frequency
PTOV
Over Voltage
PTRC
Protection Trip Conditioning
PTTR
Thermal Overload
PTUC
Under Current
PTUV
Under Voltage
PUPF
Under Power Factor
PTUF
Under Frequency
PVOC
Voltage Controlled Time Over Current
PVPH
Volts per Hz
PZSU
Zero Speed or Under Speed
R – Protection Related Functions
RDRE
Disturbance Recorder Function
RADR
Disturbance Recorder Channel Analogue
RBDR
Disturbance Recorder Channel Binary
RDRS
Disturbance Record Handling
RBRF
Breaker Failure
RDIR
Directional Element
RFLO
Fault Locator
RPSB
Power Swing Detection/Blocking
RREC
Auto Reclosing
RSYN
Synchronism Check or Synchronizing
C – Control Functions
CALH
Alarm Handling
CCGR
Cooling Group Control
CILO
Interlocking
CPOW
Point on Wave Switching
CSWI
Switch Controller
G – Generic Functions
GAPC
Generic Automatic Process Control
Server
Comment:
Yes
Ground Fault Trip (50/51)
Yes
Resistor Fault Trip (59N)
SE-330 IEC 61850 Communication Conformance Statement
Classes of Logical Nodes Supported in the Server (continued)
LN
Name
LN Description
Server
Comment:
GGIO
Generic Process I/O
Yes
SE-330 Event Records
GSAL
Generic Security Application
Yes
NGR Resistance
NGR Neutral voltage
NGR Neutral current
I – Interfacing and Archiving Functions
IARC
Archiving
IHMI
Human Machine Interface
ITCI
Telecontrol Interface
ITMI
Telemonitoring Interface
A – Automatic Control Functions
ANCR
Neutral Current Regulator
ARCO
Reactive Power Control
ATCC
Automatic Tap Changer Controller
AVCO
Voltage Control
M – Metering and Measurement Functions
MDIF
Differential Measurements
MHAI
Harmonics or Interharmonics
MHAN
Non-Phase Related Harmonics or Interharmonics
MMTR
Metering
MMXN Non-Phase Related Measurement
MMXU Measurement
MSQI
Sequence and Imbalance
MSTA
Metering Statistics
S – Sensors and Monitoring Functions
SARC
Monitoring and Diagnostics for Arcs
SIMG
Insulation Medium Supervision (gas)
SIML
Insulation Medium Supervision (liquid)
SPDC
Monitoring and Diagnostics for Partial Discharges
X – Switchgear Functions
XCBR
Circuit Breaker
XSWI
Circuit Switch
T – Instrument Transformers
TCTR
Current Transformer
Page 10
Rev. 0-A-072314
SE-330 IEC 61850 Communication Conformance Statement
Classes of Logical Nodes Supported in the Server (continued)
LN
Name
LN Description
TVTR
Voltage Transformer
Server
Comment:
Y – Power Transformers
YEFN
Earth Fault Neutralizer
YLTC
Tap Changer
YPSH
Power Shunt
YPTR
Power Transformer
Z – Further Power Systems Equipment
ZAXN
Auxilliary Network
ZBAT
Battery
ZBSN
Bushing
ZCAB
Power Cable
ZCAP
Capacitor Bank
ZCON
Converter
ZGEN
Generator
ZGIL
Gas Insulated Line
ZLIN
Power Overhead Line
ZMOT
Motor
ZREA
Reactor
LN Classes From Edition 2
4.2 LOGICAL NODE EXTENSIONS
4.2.1 NEW LOGICAL NODES
No new LN classes are implemented.
4.2.2 EXTENDED LOGICAL NODES
None.
4.3 COMMON DATA CLASS EXTENSIONS
4.3.1 NEW COMMON DATA CLASSES
No new common data classes are implemented.
4.3.2 EXTENDED COMMON DATA CLASSES
No extensions to common data class definitions given in IEC 61850-7-3 are implemented.
4.4 ENUM TYPES EXTENSIONS
4.4.1 NEW ENUM TYPES
None.
4.4.2 EXTENDED ENUM TYPES
None.
Page 11
Rev. 0-A-072314
SE-330 IEC 61850 Communication Conformance Statement
Page 12
Rev. 0-A-072314
5. PIXIT DETAILS
The following sections define additional information for the performance of the SE-330 IEC 61850 server
implementation.
5.1 PIXIT FOR ASSOCATION MODEL
ID
Description
Value / Clarification
As1
Maximum number of clients that can
set-up an association
simultaneously.
4
As2
TCP_KEEPALIVE Value
Configurable: from 1 to 1000 s
As3
Lost Connection Detection Time
Default 10 s
(default cycle of TCP Keep-alive message 1 s, 10 retransmissions)
As4
Is Authentication Supported
No
As5
What association parameters are
necessary for successful association?
Association Param.
Transport Selector
Session Selector
Presentation Selector
AP Title
AE Qualifier
Required?
Yes (Checking can be Disabled)
Yes (Checking can be Disabled)
Yes (Checking can be Disabled)
Yes (Checking can be Disabled)
Yes (Checking can be Disabled)
Checking for ALL or for NONE
As6
Association Parameters are
Configurable
Configurable Param.
Transport selector Session
selector Presentation
selector AP Title
AE Qualifierr
Default Value
1
1
1
1.1.1.999.1
12
As7
What is the Maximum and
Minimum MMS PDU Size?
Max: 12 kB
Min: There is no limit (message syntax must be correct).
As8
Time Taken for Startup
10 s
SE-330 IEC 61850 Communication Conformance Statement
5.2 PIXIT FOR SERVER MODEL
ID
Description
Sr1
Which analogue value (MX) quality
bits are supported (can be set by
server)?
Sr2
Which status value (ST) quality bits
are supported (can be set by server)?
Sr3
What is the maximum number of
data values in one GetDataValues
request?
Value / Clarification
Validity:
Y Good
Y Invalid
N Reserved
N Questionable
N Overflow
N OutofRange
N BadReference
N Oscillatory
N Failure
N OldData
N Inconsistent
N Inaccurate
Source:
Y Process
N Substituted
N Test
N OperatorBlocked
Validity:
Y Good
Y Invalid
N Reserved
N Questionable
N BadReference
N Oscillatory
N Failure
N OldData
N Inconsistent
N Inaccurate
Source:
Y Process
N Substituted
N Test
N OperatorBlocked
Limited by PDU size. 12kB
Page 13
Rev. 0-A-072314
Page 14
Rev. 0-A-072314
SE-330 IEC 61850 Communication Conformance Statement
PIXIT for Server Model (continued)
ID
Description
Sr4
What is the maximum number of
data values in one SetDataValues
request.
Sr5
Which Mode / Behaviour values are
supported.
5.3 PIXIT FOR DATA SET MODEL
ID
Description
Ds1
Ds2
Ds3
Ds4
Ds5
Ds6
Maximum Number of Data Sets
Handled by Device.
Maximum Number of Data
Elements in One Data Set .
How many persistent data sets can
be created by one or more clients?
How many non-persistent data sets
can be created by one or more
clients?
Maximum Number of Data
Elements in GOOSE Publisher Data
Set
Data Set Members in RCB Data Set
Ds7
Data Set Members in GOOSE
Publisher Data Set
Persistent Data Sets – Pre-Defined
Ds8
Ds9
GOOSE Publisher Data Set
SetDataSetValues Service
5.4 PIXIT FOR REPORTING MODEL
ID
Description
Rp1
The Supported Trigger Conditions
Value / Clarification
Limited by PDU size. 12kB
On
Blocked
Test
Test/Blocked
Off
Y
N
N
N
N
Value / Clarification
30 data sets, where 3 are fixed, and 27 are pre-defined or dynamically
created.
30 data attributes in pre-defined data sets to be referenced by RCB,
30 data attributes in dynamically created data sets to be referenced by RCB.
27 Persistent Datasets
27 Non-Persistent Datasets
LLN0$DS3_GOOSE is Referenced by GCB
Only functionally constrained data with FC = ST or FC = MX. Value,
quality and time stamp only. Process data only.
Only functionally constrained data with FC = ST or FC = MX. Pre-selected
list of signals. Only value attribute from process data included.
3 for RCB and
1 for GCB (all Pre-Defined Data Sets are Fixed)
Pre-defined and Fixed
Supported but with negative response for all data sets (data sets are
composed of read-only attributes).
Value / Clarification
Integrity
Yes
Data Change
Yes
Quality Change
Yes
Data Update
No
General Interrogation
Yes
SE-330 IEC 61850 Communication Conformance Statement
PIXIT for Reporting Model (continued)
ID
Description
Rp2
Rp3
Rp4
Rp5
The Supported Optional Fields
Support for Sending Segmented
Reports
Mechanism on second internal data
change notification of the same
analogue data value within buffer
period.
Multi client URCB approach
(compare IEC 61850-7-2 $14.2.1)
Value / Clarification
Sequence-Number
Yes
Report-Time-Stamp
Yes
Reason-for-Inclusion
Yes
Data-Set-Name
Yes
Data-Reference
Yes
EntryID
Yes
Conf-Rev
Yes
No
Send Report Immediately
All RCB instances are visible to clients; client can reserve selected instances
and subscribe for reports.
4 BRCB Instances
4 URCB Instances
Octet string 8, four LSB bytes are used as counter.
Rp6
Format of EntryID
Rp7
Buffer size for each BRCB or how
many reports can be buffered.
64 kbytes per Report Control Block
Rp8
Pre-configured RCB attributes that
cannot be changed online when:
RptEna = FALSE
(see also the ICD report settings)
May the Reported Data Set Contain:
- Structured Data Objects?
- Data Attributes?
- Timestamp Data Attributes?
None
Rp9
Rp
10
Rp
11
Rp
12
What is the scan cycle for binary
events?
Is this fixed, Configurable
Does the device support preassigning an RCB to a specific client
in the SCL?
Can unbuffered or buffered
reporting be disabled by changing
Mod or Beh to Off or Blocked?
Page 15
Rev. 0-A-072314
Y
Y
Y
10 ms
Fixed
N
N
SE-330 IEC 61850 Communication Conformance Statement
Page 16
Rev. 0-A-072314
5.5 PIXIT FOR GENERIC SUBSTATION EVENTS MODEL (GOOSE)
ID
Description
Value / Clarification
Go1
What elements of a subscribed
GOOSE header are checked to
decide the message is valid and the
allData values are accepted? If yes,
describe the conditions.
Note: The VLAN tag may be
removed by an Ethernet switch and
should not be checked.
N
Y
Y
Y
N
N
N
Y
N
Y
N
Y
Y
Y
Y
Source MAC address
Destination MAC Address (Equal to Configured)
Ethertype = 0x88B8
APPID (Equal to Configured)
gocbRef
timeAllowedtoLive (See Remarks)
datSet
goID (Equal to configured, checking can be set off.
t
stNum (see Remarks)
sqNum (see Remarks)
test (If True, Values not Passed to Application)
confRev (Equal to Configured)
ndsCom (if True, Values not Passed to Applic)
numDatSetEntries (see Remarks)
Go2
Can the test flag in the published
GOOSE be turned on / off?
Y
Go3
Does the device accept a
configuration with a GOOSE control
block with empty data set or too
large data set?
Data set for GOOSE publisher control blocks is fixed.
Go4
What is the behavior when the
GOOSE publish configuration is
incorrect?
If in device the GOOSE publisher configuration is incorrect the publisher
keeps GoEna=F and ndsCom=T
Go5
When is a subscribed GOOSE
marked as lost?
(TAL = time allowed to live value
from the last received GOOSE
message)
Delayed messages are processed as normal.
No need of status indication to the relay application about GOOSE problem
(data marked as OLD if the message does not arrive prior to TAL).
Go6
What is the behavior when one or
more subscribed GOOSE messages
isn’t received or syntactically
incorrect (missing GOOSE)
The subsequently received GOOSE message is accepted even if the new
state number is not equal to the incremented value of the previously
received state number. It is enough that it is not equal to the last received
state number or the last received state number minus 1 (see notes).
Go7
What is the behavior when a
subscribed GOOSE message is outof-order?
Message is treated as normal (it is assumed that previous messages have
been lost).
Go8
What is the behavior when a
subscribed GOOSE message is
duplicated?
Duplicated message is ignored.
SE-330 IEC 61850 Communication Conformance Statement
Page 17
Rev. 0-A-072314
PIXIT for Generic Substation Events Model (continued)
ID
Description
Value / Clarification
Go9
Does the device subscribe to
GOOSE messages with/without the
VLAN tag?
Go10
May the GOOSE data set contain:
- structured data objects?
- data attributes?
- timestamp data attributes?
Go11
Published FCD Supported
Common Data Classes / Data
Types Are
Y With the VLAN tag
Y Without the VLAN tag
Subscribed
N
Y
N
BOOL Only
Published
N
Y
N
DS3_GOOSE – common for both of GOOSE publishers, with 5 binary data
elements: GF start, GF trip, RF start, RF trip, Remote trip.
BOOL
Go12
Subscribed FCD Supported
Common Data Classes / Data
Types Are
Go13
What is the slow retransmission
time?
Is it fixed or configurable?
Default 2,000 ms with TAL = 2*2000
Configurable by Configuration Tool
Go14
What is the fast retransmission
scheme?
First message upon data change. Then the retransmission interval is
calculated from the geometric growth formula by doubling the interval.
Is it fixed or configurable?
Can the Goose publish be turned on
/ off by using
SetGoCBValues(GoEna)?
Maximum Number of Different
GOOSE Data Items that can be
Received and Processed by
GOOSE Subscriber
Maximum Number of GOOSE
Publishers From Which the Data
Can be Received and Processed
Subscriber
Fixed
Y
Go15
Go16
Go17
16 boolean data items (it is possible to receive GOOSE data of boolean type
and also of integer and bit string type with selection of valid bit)
16
(with Maximum Number of Publishers Only One Data Item per Publisher)
Go18
TAL = Time Allowed to Live
NOTES:
A GOOSE message will be accepted and processed by the subscriber:
- Even if it is received after expiration of the time allowed to live sent in the previous message
- Even if the new state number is not equal to the incremented value of the previously received state number - it is
enough that it is not equal to the last received state number or the last received state number minus 1 which allows
for retransmission on crossed redundant networks
- If the state number differs from the previously received state number, the sequence number is accepted with any
value (if the state number is equal to the previously received state number or equal to the previously received state
number minus 1, the message is treated as retransmission)
SE-330 IEC 61850 Communication Conformance Statement
Page 18
Rev. 0-A-072314
-
Even if the received message contains a dataset of the size different than the size of the previously received
dataset.
The value of numDatSetEntries from the header determines how many data entries from the message are processed. With
numDatSetEntries = 0 no data entries are processed from the received message.
5.6 PIXIT FOR GOOSE PERFORMANCE
ID
Description
Value / Clarification
Gp1
Performance Class
Type 1B, Class P2/3
Gp2
GOOSE Ping-Pong Processing
Method
Scan Cycle Based
Gp3
Application Logic Scan Cycle (ms)
Gp4
Maximum number of data attributes
in GOOSE dataset (value and
quality has to be counted as separate
attributes).
Maximum number of GOOSE to be
published .
Maximum number of GOOSE to be
subscribed.
Data types in GOOSE dataset for
published according to 7-2 Table 2.
Data types in GOOSE dataset for
subscribed according to 7-2 Table 2.
Time Slice Based OS
Approx. 5 ms
5 (Fixed Data Set)
Gp5
Gp6
Gp7
Gp8
5.7 PIXIT FOR CONTROL MODEL
ID
Description
Ct1
Control Modes Supported
5 (Two GoCB but with Identical Data Set)
16
BOOL
BOOL, INT, and BITSTRING
Value / Clarification
Y Status-Only
Y Direct-with-Normal-Security
N sbo-with-Normal-Security
N Direct-with-Enhanced-Security
N sbo-with-Enhanced-Security
Ct2
Is the control model fixed,
configurable and/or online
changeable?
FIXED FOR GGIO
All controllable objects under GGIO class the control model is fixed:
direct-with-normal-security.
Ct3
Time Activated Operate (operTm)
Supported
N
Ct4
Is “operate-many” Supported?
N
Ct5
What is the behavior of the device
when the test attribute is set in the
SelectWithValue and/or Operate
request?
Device will accept the command but will not perform it on the hardware.
SE-330 IEC 61850 Communication Conformance Statement
PIXIT for Control Model (continued)
ID
Description
Ct6
Page 19
Rev. 0-A-072314
Value / Clarification
No Functionality
ID
What are the conditions for the time
(T) attribute in the SelectWithValue
and/or Operate request?
Description
Ct7
Is pulse configuration supported?
N
Ct8
What is the behavior of the device
when the check conditions are set?
N Synchrocheck
N Interlock-Check
Device ignores the check value and the command is executed as usual.
Is this behavior fixed, configurable,
online changeable?
What additional cause diagnosis are
supported?
How to force a “test-not-ok”
respond with SelectWithValue
request?
How to force a “test-not-ok”
respond with Select request?
How to force a “test-not-ok”
respond with Operate request?
Fixed
Ct9
Ct10
Ct11
Ct12
Ct13
Ct14
Ct15
Ct16
Ct17
Which origin categories are
supported?
What happens if the orCat is not
supported?
Out of range or within the range but
not supported?
Does the IED accept an
selectwithvalue/operate with the
same ctlVal as the current status
value?
Does the IED accept a select/operate
on the same control object from 2
different clients at the same time?
Does the IED accept a
select/selectwithvalue from the same
client when the control object is
already selected (tissue 334)?
Value / Clarification
N/A (the Only Model Supported is Direct with Normal Security)
N/A
N/A
DOns:
SBOns:
DOes:
SBOes:
All
Operate with orCat out of range
N/A
N/A
N/A
DOns:
SBOns:
DOes:
SBOes:
DOns:
SBOns:
DOes:
SBOes:
DOns:
SBOns:
DOes:
SBOes:
SBOns:
SBOes:
Negative response
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Y (see Remarks)
N/A
N/A
N/A
N/A
N/A
SE-330 IEC 61850 Communication Conformance Statement
PIXIT for Control Model (continued)
ID
Description
Ct18
Ct19
Ct20
Ct21
Is for SBOes the internal validation
performed during the
SelectWithValue and/or Operate
step?
Can a control operation be blocked
by Mod=Off or Blocked?
Does the IED support local / remote
operation?
Does the IED send an
InformationReport with
LastApplError as part of the Operate
response- for control with normal
security?
Page 20
Rev. 0-A-072314
Value / Clarification
N/A
N (if Mod Not Configurable)
Y
DOns: N
SBOns: N/A
NOTES:
In DOns model: When two client sends Operate request with very short interval (e.g. 10 ms) then for processing the
second command the object position is still unchanged due to the first command, thus both clients receive positive Operate
response.
5.8 PIXIT FOR TIME SYNCHRONIZATION
ID
Description
Tm1
What quality bits are supported?
Tm2
Describe the behavior when the time
synchronization signal/messages are
lost?
When is the time quality bit “Clock
failure” set?
When is the time quality bit “Clock
not synchronized” set?
Tm3
Tm4
Tm5
Tm6
Tm7
Is the timestamp of a binary event
adjusted to the configured scan
cycle?
Does the device support time zone
and daylight saving?
Which attributes of the SNTP
response packet are validated?
Value / Clarification
N LeapSecondsKnown
N ClockFailure
Y ClockNotSynchronized
Time is taken from internal RTC.
Not Set
It is done when the device detects that the configured NTP server does not
respond; the latency depends on measured drift of the internal clock.
Typically takes 1 minute.
Y
Y
N
N
N
Y
Y
N
Leap indicator Not Equal to 3.
Mode is Equal to SERVER.
OriginateTimestamp is Equal to Value.
Sent by the SNTP Client as Transmit.
Timestamp
RX/TX Timestamp Fields are Checked for Reasonable Values
SNTP Version 3 or 4
Other
SE-330 IEC 61850 Communication Conformance Statement
5.9 PIXIT FOR FILE TRANSFER MODEL
ID
Description
Ft1
What is structure of files and
directories?
Value / Clarification
N/A
Is the IETF FTP protocol also
implemented?
N/A
Ft2
Directory names are separated from
the file name by ?
N/A
Ft3
The maximum file name size
including path (recommended 64
chars)?
N/A
Ft4
Are directory/file name case
sensitive?
N/A
Ft5
Maximum File Size
N/A
Ft6
Is the requested file path included in
the file name of the MMS
fileDirectory respond?
N/A
Ft7
Is the wild char supported MMS
fileDirectory request?
N/A
Ft8
Is it allowed that 2 clients get a file
at the same time?
N/A
Page 21
Rev. 0-A-072314
SE-330 IEC 61850 Communication Conformance Statement
Page 22
Rev. 0-A-072314
6. TICS DETAILS
6.1 INTRODUCTION
This part of the document is based on a template for the tissues conformance statement. According to the UCA IUG QAP
the tissue conformance statement is required to perform a conformance test and is referenced on the certificate.
6.2 MANDATORY INTOP TISSUES
During the October 2006 meeting IEC TC57 working group 10 decided that:
 Green Tissues with the category “IntOp” are mandatory for IEC 61850 edition 1
 Tissues with the category “Ed.2” Tissues should not be implemented.
The table below gives an overview of the implemented IntOp Tissues.
Part
8-1
7-4
7-3
Tissue No.
116
165
183
None
28
54
55
60
63
219
270
Description
GetNameList with Empty Response?
Improper Error Response for GetDataSetValues
GetNameList Error Handling
Definition of APC
Point def xVal, Not cVal
Ineut = Ires ?
Services Missing in Tables
Mag in CDC CMV
operTm in ACT
WYE and DEL RMS Values
Implemented Y, N/A
Y
Y
Y
N/A
N/A
Y
N/A
Y
N/A
note 3
SE-330 IEC 61850 Communication Conformance Statement
Implemented IntOp Tissues (continued)
Part
Tissue No.
7-2
Part
6
30
31
32
35
36
37
39
40
41
42
43
44
45
46
47
50
51
52
53
151
166
185
189
234
278
453
Tissue No.
1
5
8
10
17
169
Description
Control Parameter T
Typo
Typo in Syntax
Typo Syntax Control Time
Syntax Parameter DSet-Ref Missing
Syntax GOOSE “T” Type
Add DstAddr to GoCB
GOOSE Message “AppID” to “GoID”
GsCB “AppID” to “GsID”
SV Timestamp: “EntryTime” to “TimeStamp”
Control “T” Semantic
AddCause - Object Not Sel
Missing AddCauses (Neg Range)
Synchro check Cancel
“.” in LD Name?
LNName Start with Number?
ARRAY [0..num] Missing
Ambiguity GOOSE SqNum
Add DstAddr to GsCB, SV
Name Constraint for Control Blocks etc.
DataRef Attribute in Log
Logging - Integrity Periode
SV Format
New Type CtxInt (Enums are Mapped to 8 Bit Integer)
EntryId Not Valid for a Server (Part of #453)
Reporting & Logging Model Revision
Description
Page 23
Rev. 0-A-072314
Implemented Y, N/A
Y
N/A
N/A
N/A
N/A
Y
Y
Y
N/A
N/A
N/A
Y
N/A, note 2
N/A
Y
Y
Y
Y
N/A
Y
N/A
N/A
N/A
N/A
Y
Y
Implemented Y, N/A
Syntax
tExtensionAttributeNameEnum is Restricted
SIUnit Enumeration for W
Base Type for Bitstring Usage
DAI/SDI Elements Syntax
Ordering of Enum Differs From 7-3
NOTES:
1) Editorial tissues are marked as “N/A”.
2) Final proposal on tissue 45 is not defined yet.
3) Tissue 270: In SE330 data model the LNs with WYE and DEL data are described (in the LN prefix and in the
description attributes) whether they provide amplitude or rms values.
N/A
Y
Y
Y
Y
N/A
SE-330 IEC 61850 Communication Conformance Statement
Page 24
Rev. 0-A-072314
6.3 OPTIONAL INTOP TISSUES
After the approval of the server conformance test procedures version 2.2 the following IntOp tissues were added or
changed. Implementation of all tissues in this section is specified as optional.
Part
8-1
8-1
7-4
7-2
7-2
6
6
Tissue No.
246
545
79
333
453
245
529
Description
Control Negative Response (SBOns) with LastApplError
Skip File Directories with No Files
AutoRecSt value 4 = “unsuccessful”
Enabling of an Incomplete GoCB
Combination of all Reporting and Logging Tissues
Attribute RptId in SCL
Replace sev - Unknown by Unknown
Implemented Y, N/A
N
Y
N/A
Y
Y
Y
N/A
6.4 OTHER IMPLEMENTED TISSUES
Other implemented tissues that should have no impact on interoperability.
Part
Tissue No.
Description
Implemented Y, N/A
SE-330 IEC 61850 Communication Conformance Statement
Page 25
Rev. 0-A-072314
APPENDIX A DOCUMENT REVISION HISTORY
DOCUMENT RELEASE DATE
DOCUMENT REVISION
July 23, 2014
0-A-072314
DOCUMENT REVISION 0-A-072314
Initial Release.
SE-330 IEC 61850 Communication Conformance Statement
This page intentionally left blank.
Page 26
Rev. 0-A-072314