Thursday, November 19, 2026

How Events could Issue Reports according to IEC 61850

Reporting in IEC 61850 is a very powerful and efficient service model to inform monitoring and other systems (SCADA, RTU, ...) about changes in the power delivery (and any other) system. The flow of information reported by an IEC 61850 Server is as described in the following three services:

Unsolicited Reporting based on events (Report by exception, buffered Reporting, buffer time)

Appl.<--Client<--Report<--Server:Report Control Block<--DataSet<-DataAttributes<--process

Requested Report (General Interrogation, gi, all values according to DataSet)

Appl.-->Client-->Request Report-->Server:Report Control Block<--DataSet<-DataAttributes<--process
Appl.<--Client<--Report<--Server

Periodic Reporting (Integrity reporting, all values according to DataSet)

Appl.<--Client<--Report<--Server:Report Control Block<--DataSet<-DataAttributes<--process

The reporting services are impacted by four definitions/configurations:

  1. Abstract reporting service model in IEC 61850-7-2
  2. Data Attributes of Logical Nodes (IED Instances, Type Templates) - SCL describing the semantic (context) of the data and its relation to the application and physics ...
  3. Report Control Block (RCB) Configuration - SCL
  4. Mapping to MMS (IEC 61850-8-1) and DMS (IEC 61850-8-3)

Explanation of crucial details:

  • report by exception - A DataSet with n Members (DataAttributes), only the value of the Member that shows a change or update will be reported ... means: short messages
  • buffer time - same as above, but (during buffer time) collect all events after the first event happened ... send them together in one message
  • buffered Reporting - buffer all reports in the server as long as no communication is available ... when communication is available, client can request buffered events.
  • Trigger Option attribute of DataAttributes: dchg (Data Change), dupd (Data Update), qchg (Quality Change) - possible trigger options
  • TriggerConditions in Report Control Blocks: data-change, quality-change, data-update, integrity, general-interrogation - which conditions are monitored by a specific RCB
  • ReasonForInclusionInReport in Report messages: data-change, quality-change, data-update, integrity, general-interrogation - which condition did issue sending the report
  • Services and ReportControl elements in SCL - all details how a specific IED (in the sense of SCL ... it is a kind of a virtual device) uses reporting ... many combinations are possible ... not all combinations are valid ...

Here we have the chicken and egg problem: If you don't know what you need, it is hard to recommend what you should do. If you don't know what IEC 61850 reporting offers, it is hard to decide which features you want to use.

I have seen many people struggling with reporting ... 

In case you want to understand the possible features of reporting, please contact me ... to tap my experience.

By the way, IEC 61850-8-3 (DMS) simplifies the syntax of the report message explicitly ... people appreciate it very much ...

No comments: