<< Click to Display Table of Contents >>
PIXIT for Reporting Model |
Y: Supported Service; N: Unsupported Service
ID |
Description |
Value |
---|---|---|
Rp1 |
The supported trigger conditions are (compare PICS) |
integrity: Y; data change: Y; quality change: Y; data update: Y; general interrogation: Y |
Rp2 |
The supported optional fields are |
sequence-number: Y; report-time-stamp: Y; reason-for-inclusion: Y; data-set-name: Y; data-reference: Y; buffer-overflow: Y; entryID: Y; conf-rev: Y; segmentation: Y |
Rp3 |
Can the server send segmented reports? |
Y |
Rp4 |
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) |
Send report immediately OR Replace analogue value in pending report |
Rp5 |
Multi client URCB approach (compare IEC 61850-7-2 $14.2.1) |
Each URCB is visible to all clients |
Rp6 |
What is the format of EntryID |
Based on datetime and sequence number in hex: DDMMYYHHMMSS SEQNUMBER |
Rp7 |
What is the buffer size for each BRCB or how many reports can be buffered |
Not explicitly limited, depends on available memory |
Rp8 |
Pre-configured RCB attributes that cannot be changed online when RptEna = FALSE (see also the ICD report settings) |
N |
Rp9 |
May the reported data set contain: structured data objects and data attributes? |
Y |
Rp10 |
What is the scan cycle for binary events? Is this fixed, configurable |
Configurable |
Rp11 |
Does the device support to pre-assign a RCB to a specific client in the SCL |
N |