PIXIT for Reporting model
ID
Ed
Description
Rp1
1
The supported trigger conditions are
(compare PICS)
Rp2
1
The supported optional fields are
Rp3
1,2
Can the server send segmented reports
(when not supported, it is allowed to refuse an
association with a PDU smaller than the
supported minimum PDU size)
Rp4
1,2
Mechanism on second internal data change
notification of the same analogue data value
within buffer period (Compare IEC 61850-7-2
$14.2.2.9)
Rp5
1
Multi client URCB approach
(compare IEC 61850-7-2:2003 $14.2.1)
Rp6
-
What is the format of EntryID
Rp7
1,2
What is the buffer size for each BRCB or how
many reports can be buffered
Rp8
-
Pre-configured RCB attributes that are dynamic,
compare SCL report settings
Rp9
1
May the reported data set contain:
- structured data objects
- data attributes
Rp10
1,2
What is the scan cycle for binary events
Is this fixed, configurable
Rp11
1
Does the device support to pre-assign a RCB to a
specific client in the SCL
Value / Clarification
integrity
data change
quality change
data update
general interrogation
sequence-number
report-time-stamp
reason-for-inclusion
data-set-name
data-reference
buffer-overflow
entryID
conf-rev
segmentation
Y
The DUT behaves as if BufTm has
expired and sends the report
immediately, restarts the timer
with BufTm value and processes
the second change
Each URCB is visible to all clients
Deprecated
30 Kbytes
Deprecated
Y
Y
2 ms
Fixed
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
6
Capítulos
