61850-8-1 © IEC:2004(E) – 59 –
17.3.3.3.2 ISO 9506 information type constraints
ISO 9506 allows the information type to be constrained to ANNOTATION, EVENT-DATA,
DATA.
ANNOTATION
The use of the ANNOTATION constraint is a local issue.
EVENT-DATA
The EVENT-DATA information type shall be used to indicate information entered into the
MMS Journal due to log control block control/processing. The use of this constraint is not
restricted solely to indicating LCB control, but other uses are considered to be a local issue.
The EVENT-DATA Information Type Event Transition Record shall be used for journalling
transitions of the LCD LogEna value as prescribed:
– The event condition name value shall be the MMS NamedVariable ObjectName
representing the log control block that caused the journal entry to be created.
– The event condition state shall be the state of the LogEna component of the log control
block that caused the journal entry to be created.
The value mapping between LogEna values and event condition state values shall be:
– A value of LogEna being FALSE shall be mapped to the event condition state of
DISABLED. The transition of the LogEna value from TRUE to FALSE shall cause a journal
entry to be created.
– A value of LogEna being TRUE shall be mapped to either the event condition state of
IDLE or ACTIVE. The IDLE state is reserved to indicate a transition of the value of LogEna
from FALSE to TRUE. Only a journal entry with an event condition state value of ACTIVE
shall have a list of journal variables.
For efficiency reasons, a sequence of entryDat(s) may be entered within a single MMS journal
entry.
On a power-up or reset the status of the LCB’s LogEna should be journaled with a value
IDLE.
DATA
DATA shall be used for logging of values from DataSets specified by an LCB.
17.3.3.3.3 ISO 9506 (all parts) information journal variables
MMS journal variables are represented as a sequence of a journal variable tag and data. This
document maps both the LogEntry datRef/value and reasonCode to individual journal
variables. These journal variables shall appear within a single information type entry and shall
be in the order of: the journal variable representing the datRef/value followed by the journal
variable representing the reasonCode.
Each individual journal variable is reflected as member of the listofVariables within the journal
entry content (see 16.8.1 of ISO 9506-2 (2003)). Each member of the listofVariables consists
of a variableTag and a valueSpecification.
The variableTag shall have a minimum-maximum size of 65 octets.
Journal variableTag for DatRef
A journal variable representing journal data relating to DatRef shall have a value of the form
ObjectReference.