- 1. Introduction
- 2. Understanding the IEC 61850 Data Model
- 3. What Is an IEC 61850 Dataset?
- 4. Understanding FCDA
- 5. GOOSE Dataset Engineering
- 6. GOOSE Control Block (GoCB)
- 7. MMS Reporting and Report Control Blocks
- 8. URCB – Unbuffered Report Control Block
- 9. BRCB – Buffered Report Control Block
- 10. URCB vs BRCB
- 11. Report Trigger Options
- 12. MMS Dataset and Report Configuration Example
- 13. GOOSE and MMS Dataset Comparison
- 14. SCL Engineering: DataSet, GSEControl and ReportControl
- 15. Practical MiCOM Engineering Workflow
- 16. Testing GOOSE Datasets and Control Blocks
- 17. Testing MMS Reports and RCBs
- 18. Common Dataset and Control Block Problems
- 19. Important Engineering Considerations
- 20. Conclusion
- 21. Practical IEC 61850 and MiCOM Training by Elec-Engg
1. Introduction
Datasets and control blocks are fundamental elements of IEC 61850 engineering. They determine which information an Intelligent Electronic Device (IED) makes available to other devices and how that information is communicated.
In MiCOM protection relays, understanding datasets, Functional Constraint Data Attributes (FCDA), GOOSE Control Blocks (GoCB), and Report Control Blocks (RCB) is essential for engineers working on protection, SCADA integration and substation automation.
Although GOOSE and MMS use datasets, they serve different communication purposes:
- GOOSE: Transfers event-driven information directly between IEDs over Ethernet.
- MMS reporting: Transfers selected information from an IED to an MMS client, such as a SCADA system or substation automation controller.
This article explains how to engineer these elements, how they relate to the IEC 61850 data model, and how to test them in practical MiCOM applications.
An important consideration is that IEC 61850 capabilities differ between MiCOM models, order codes, communication hardware and firmware versions. Always verify the required functions using the relevant device documentation, MICS, PICS, PIXIT, ICD files and release notes.
2. Understanding the IEC 61850 Data Model
Before creating a dataset, engineers must understand the structure of the IEC 61850 data model.
The general hierarchy is:
IED
└── Logical Device (LD)
└── Logical Node (LN)
└── Data Object (DO)
└── Data Attribute (DA)
For example, a feeder protection relay may contain logical nodes representing overcurrent protection, breaker operation and measurements.
Illustrative references include:
IED1/PROT/PTOC1.Op.general
IED1/PROT/PTRC1.Tr.general
IED1/CTRL/XCBR1.Pos.stVal
IED1/MEAS/MMXU1.A.phsA.cVal.mag.f
These examples illustrate IEC 61850 naming conventions. Actual logical device names, logical nodes, instances and supported attributes must be checked in the specific MiCOM relay data model.
2.1 Logical Device
A Logical Device groups related logical nodes.
For example, a relay may contain logical devices associated with:
- Protection functions.
- Measurements.
- Control functions.
- General IED information.
The naming and organization depend on the manufacturer’s implementation.
2.2 Logical Node
A Logical Node represents a particular function or information category.
Examples include:
| Logical node | General purpose |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIS | Distance protection |
| PDIF | Differential protection |
| PTRC | Protection trip conditioning |
| MMXU | Measurement information |
| XCBR | Circuit breaker information |
| CSWI | Switch control |
| GGIO | Generic process I/O |
These are standard logical node classes. Their presence and available data objects in a particular MiCOM relay must be confirmed.
2.3 Data Objects and Data Attributes
A logical node contains data objects, and data objects contain data attributes.
For example:
PTOC1
└── Op
├── general
├── phsA
├── phsB
└── phsC
The exact structure varies according to the supported logical node and implementation.
3. What Is an IEC 61850 Dataset?
A dataset is a named collection of data attributes selected from an IED’s data model.
Instead of communicating every available signal, the engineer selects only the information required by a particular application.
For example, a feeder relay might publish a dataset containing:
- Overcurrent protection start.
- Overcurrent protection operation.
- Circuit breaker position.
- Protection trip status.
- Breaker failure initiation.
The dataset can be used by a GOOSE control block or by an MMS report control block, depending on the intended communication service and device capabilities.
3.1 Why Are Datasets Important?
Datasets provide several benefits:
- Organize the required information.
- Reduce unnecessary communication.
- Simplify SCADA integration.
- Support GOOSE communication.
- Support MMS reporting.
- Improve engineering documentation.
- Make communication configuration easier to maintain.
A dataset should be designed around the actual protection, control or monitoring application.
4. Understanding FCDA
FCDA stands for Functional Constraint Data Attribute.
It identifies a particular data attribute included in a dataset.
An FCDA reference can contain:
- Logical device name.
- Logical node name.
- Data object name.
- Data attribute name.
- Functional constraint.
For example:
<FCDA
ldInst="PROT"
prefix=""
lnClass="PTOC"
lnInst="1"
doName="Op"
daName="general"
fc="ST"/>
This is an illustrative SCL example.
It identifies the general status attribute of an overcurrent protection operation logical node, assuming that the specific IED implements that reference.
4.1 Understanding Functional Constraints
Functional constraints identify the purpose or category of data attributes.
Important examples include:
| Functional constraint | Meaning |
|---|---|
| ST | Status information |
| MX | Measurement information |
| CO | Control information |
| SP | Setpoint information |
| CF | Configuration information |
| DC | Description information |
| SG | Setting group information |
| SE | Setting information |
| SV | Substitution information |
| BL | Blocking information |
| OR | Operational rating information |
| EX | Extended definition information |
Not every functional constraint is applicable to every data object.
For example, a breaker position status is typically associated with status information, while a measured current is associated with measurement information.
4.2 Choosing the Correct FCDA
Suppose an engineer wants to transmit the circuit breaker position through GOOSE.
The relevant information may be represented by an XCBR logical node and its position data object.
An illustrative reference is:
XCBR1.Pos.stVal
The engineer must check:
- Whether XCBR is implemented.
- Whether the Pos data object is available.
- Whether stVal is exposed.
- Whether the selected functional constraint is correct.
- Whether the data attribute is supported for GOOSE publication.
Do not assume that a logical node reference from another manufacturer’s relay will work identically in a MiCOM device.
5. GOOSE Dataset Engineering
GOOSE datasets are used to transmit information between IEDs.
A GOOSE publisher selects the dataset and associates it with a GOOSE control block.
The receiving IED subscribes to the relevant information.
5.1 Example GOOSE Dataset
Consider a MiCOM feeder protection relay.
The required GOOSE dataset contains:
| Dataset member | Application |
|---|---|
| Overcurrent start | Protection indication |
| Overcurrent trip | Trip indication |
| Breaker position | Equipment status |
| Breaker failure initiation | Protection coordination |
The dataset might be named:
DS_FEEDER_GOOSE
The name is project-specific and must be consistent with the configuration.
5.2 Dataset Definition in SCL
A simplified SCL representation is:
<DataSet name="DS_FEEDER_GOOSE">
<FCDA
ldInst="PROT"
lnClass="PTOC"
lnInst="1"
doName="Op"
daName="general"
fc="ST"/>
<FCDA
ldInst="CTRL"
lnClass="XCBR"
lnInst="1"
doName="Pos"
daName="stVal"
fc="ST"/>
</DataSet>
This example illustrates the concept. A complete configuration must follow the applicable SCL schema and the actual device model.
5.3 Dataset Design Recommendations
When creating GOOSE datasets:
- Include only signals required by subscribers.
- Use meaningful dataset names.
- Avoid unnecessary dataset members.
- Document every signal and its purpose.
- Check data types and functional constraints.
- Confirm the subscriber supports the transmitted information.
- Revalidate the configuration after dataset changes.
Changing a dataset can affect the GOOSE configuration revision and the subscriber configuration. The complete communication relationship must be checked after any modification.
6. GOOSE Control Block (GoCB)
The GOOSE Control Block defines how the dataset is transmitted.
It is commonly represented by the GSEControl element in SCL.
The GOOSE control block associates a dataset with communication parameters and transmission behavior.
Important information includes:
- Control block name.
- Dataset reference.
- GOOSE application identifier.
- Configuration revision.
- GOOSE identifier.
- Communication addressing.
6.1 Example GOOSE Control Block
<GSEControl
name="GCB_FEEDER"
type="GOOSE"
datSet="DS_FEEDER_GOOSE"
appID="FEEDER_GOOSE"
confRev="1"/>
This is a simplified illustration, not a complete device configuration.
6.2 Relationship Between Dataset and GoCB
The relationship is:
MiCOM IED
|
+---- Logical Nodes
|
+---- DataSet
| |
| +---- FCDA 1
| +---- FCDA 2
| +---- FCDA 3
|
+---- GOOSE Control Block
|
+---- Dataset Reference
|
+---- Communication Parameters
|
+---- GOOSE Transmission
The publisher transmits the dataset according to the GOOSE control block configuration.
7. MMS Reporting and Report Control Blocks
MMS reporting is another important IEC 61850 communication mechanism.
While GOOSE is mainly used for direct event-driven communication between IEDs, MMS reporting is commonly used to transfer information from protection relays to SCADA systems.
For example, a MiCOM relay can provide:
- Protection operation indications.
- Circuit breaker status.
- Alarm information.
- Current and voltage measurements.
- Event information.
- Selected equipment status.
The MMS client establishes communication with the IED and receives reports according to the configured reporting mechanism.
7.1 What Is a Report Control Block?
A Report Control Block (RCB) defines how an IED reports selected dataset information to an MMS client.
The report control block references a dataset and specifies reporting behavior.
Important parameters may include:
- Report identifier.
- Dataset reference.
- Buffering type.
- Trigger options.
- Integrity period.
- Optional fields.
- Buffer time.
- Configuration revision.
- Report enable status.
The exact supported options depend on the IED implementation.
8. URCB – Unbuffered Report Control Block
URCB stands for Unbuffered Report Control Block.
It is used for reporting information to an MMS client without the persistent event buffering behavior provided by a BRCB.
If the client is disconnected, events generated during that period are not generally retained for later delivery through the URCB mechanism.
URCB is useful for applications where continuous client connection is expected and recovery of all missed events is not essential.
8.1 URCB Characteristics
- Unbuffered reporting.
- Client-associated reporting configuration.
- Reporting of configured dataset changes.
- Optional integrity reporting where supported.
- Suitable for applications where a persistent event history is not required from the report buffer.
8.2 URCB Example
Consider a SICAM PAS system communicating with a MiCOM feeder relay.
The relay provides:
- Breaker status.
- Protection start.
- Protection trip.
- Current measurements.
The SCADA client enables the appropriate report control block and receives reports when configured reporting conditions occur.
The exact reporting configuration must be compatible with both the MiCOM server and the MMS client.
9. BRCB – Buffered Report Control Block
BRCB stands for Buffered Report Control Block.
It provides buffering of report events so that events can be retained during a temporary client disconnection and delivered later, subject to the buffer capacity and implementation.
This is particularly useful for event recording and SCADA systems where missing important indications during a communication interruption is undesirable.
9.1 BRCB Characteristics
- Buffered reporting.
- Event retention during client disconnection.
- Sequence information for report handling.
- Buffer capacity limitations.
- Potential recovery of missed events after reconnection.
- Support for reporting configuration and reservation behavior as implemented by the IED.
9.2 Practical BRCB Example
Suppose a MiCOM relay is connected to a SICAM PAS station controller.
The MMS communication link is interrupted for several minutes.
During the interruption:
- A protection element operates.
- A breaker changes position.
- An alarm is generated.
- A fault indication becomes active.
If the relay supports and has correctly configured a BRCB, the relevant report events can be retained in its buffer.
When communication is restored, the client may receive the buffered reports, provided the buffer has not overflowed and the reporting configuration supports recovery.
BRCB does not guarantee unlimited event retention.
10. URCB vs BRCB
The following comparison summarizes the principal differences.
| Feature | URCB | BRCB |
|---|---|---|
| Full name | Unbuffered Report Control Block | Buffered Report Control Block |
| Event buffering | No persistent event buffer | Events can be buffered |
| Client disconnection | Events may be missed | Events may be retained |
| Recovery of missed events | Not generally provided | Supported within buffer and implementation limits |
| Typical application | Live monitoring | Event reporting and recovery |
| Buffer capacity | Not applicable as persistent event storage | Limited by configured or available capacity |
The choice between URCB and BRCB should be based on the SCADA requirements and the capabilities of the IED.
11. Report Trigger Options
Report control blocks can use different trigger conditions to determine when information is transmitted.
Important trigger options include:
11.1 Data Change
A report can be generated when a selected data value changes.
For example:
Breaker Position:
CLOSED → OPEN
The SCADA client receives the corresponding status change.
11.2 Quality Change
A report can be generated when the quality of a data attribute changes.
For example, a measurement may become invalid because of an internal signal or measurement problem.
The quality information helps SCADA distinguish valid data from questionable or unavailable information.
11.3 Data Update
A report can be triggered when a data value is updated, even if its value has not changed.
The exact behavior depends on the selected data and implementation.
11.4 Integrity Period
An integrity report periodically sends the selected dataset information.
This can help the client refresh its view of the IED data model.
11.5 General Interrogation
General interrogation (GI) allows the client to request a report of relevant current information.
This is useful when establishing communication or recovering the current state after an interruption.
GI behavior and supported trigger options should be verified for the specific device and client.
12. MMS Dataset and Report Configuration Example
Consider a substation with a MiCOM relay and a SICAM PAS station controller.
The objective is to transmit protection and equipment information to the SCADA system.
The engineering process can be organized as follows.
Step 1 – Identify the required information
Select:
- Protection start.
- Protection trip.
- Breaker position.
- Phase currents.
- Phase voltages.
- General alarms.
Step 2 – Identify the data model references
Check the logical devices, logical nodes and data attributes in the MiCOM IEC 61850 model.
Step 3 – Create the dataset
Create an MMS reporting dataset containing the selected information.
Step 4 – Configure the report control block
Select a suitable report control block and configure its reporting parameters.
Step 5 – Configure the MMS client
Configure the station controller to communicate with the relay.
Step 6 – Enable reporting
Enable the report control block using the supported MMS client services.
Step 7 – Test reporting
Change a protection or equipment signal and verify that the client receives the correct report.
13. GOOSE and MMS Dataset Comparison
Although both GOOSE and MMS can use datasets, they have different engineering purposes.
| Feature | GOOSE | MMS Reporting |
|---|---|---|
| Main purpose | Fast IED-to-IED event communication | SCADA and client-server data exchange |
| Communication | Ethernet multicast | MMS client-server communication |
| Transport | Layer 2 Ethernet | TCP/IP |
| Ethernet type | 0x88B8 | Typically carried over TCP port 102 |
| Dataset | Yes | Yes |
| Control block | GoCB | RCB |
| Typical application | Interlocking, blocking, trip signals | Alarms, status, measurements |
| Event handling | State-based retransmission | Report trigger and buffering options |
GOOSE and MMS can coexist in the same IEC 61850 substation network.
They should not be considered interchangeable.
14. SCL Engineering: DataSet, GSEControl and ReportControl
SCL provides the engineering structure for describing datasets and communication control blocks.
The following elements are particularly important.
| SCL element | Function |
|---|---|
| DataSet | Defines selected information |
| FCDA | Defines individual dataset members |
| GSEControl | Defines a GOOSE control block |
| ReportControl | Defines an MMS report control block |
| GSE | Defines GOOSE communication information |
| Address | Contains communication address parameters |
| Inputs | Describes external inputs |
| ExtRef | Describes external references |
14.1 Example ReportControl
A simplified SCL example is:
<ReportControl
name="Report01"
rptID="FEEDER_REPORT"
datSet="DS_SCADA"
buffered="true"
confRev="1">
<TrgOps
dchg="true"
qchg="true"
period="true"
gi="true"/>
<OptFields
seqNum="true"
timeStamp="true"
dataSet="true"
reasonCode="true"/>
</ReportControl>
This illustrates the general structure of a buffered report control block.
It is not a universal MiCOM configuration template. The supported options, attributes and constraints must be checked against the applicable IEC 61850 edition and the device implementation.
15. Practical MiCOM Engineering Workflow
The engineering workflow may involve S1 Agile and a separate IEC 61850 system configuration tool.
The division of responsibilities depends on the MiCOM model and supported software functions.
15.1 Device Engineering
Use the supported MiCOM engineering tool to:
- Identify the relay model.
- Configure protection functions.
- Review available IEC 61850 data.
- Check device communication settings.
- Verify the supported configuration workflow.
15.2 System-Level Engineering
Use an appropriate system configuration tool, where required, to:
- Import IED capability descriptions.
- Build the substation configuration.
- Define datasets.
- Configure GOOSE control blocks.
- Configure report control blocks.
- Establish subscriber relationships.
- Generate device-specific SCL configuration files where supported.
15.3 Configuration Validation
Before transferring configuration to the devices:
- Validate SCL syntax.
- Check data references.
- Verify dataset members.
- Check control block references.
- Confirm communication parameters.
- Check device compatibility.
- Review the configuration revision.
- Confirm the final files match the approved project.
A syntactically valid SCL file does not necessarily mean the configuration can be loaded or operated correctly by the IED.
16. Testing GOOSE Datasets and Control Blocks
GOOSE dataset testing should verify both communication and application behavior.
Recommended tests include:
- Confirm the publisher’s dataset.
- Check the FCDA references.
- Verify the GOOSE control block.
- Confirm the destination multicast address.
- Verify APPID and VLAN settings.
- Capture GOOSE packets using Wireshark.
- Change the published signal.
- Check the dataset value in the packet.
- Verify the subscriber receives the signal.
- Confirm the subscriber application responds correctly.
Useful Wireshark filters:
goose
eth.type == 0x88b8
vlan.id == 10
Check stNum, sqNum, confRev and timeAllowedToLive during the analysis.
17. Testing MMS Reports and RCBs
MMS reporting should be tested separately from GOOSE.
A practical procedure includes:
Communication tests
- Verify relay IP address.
- Verify network connectivity.
- Confirm TCP port 102 connectivity.
- Establish the MMS association.
- Discover the available data model.
Dataset tests
- Check dataset references.
- Verify dataset members.
- Read the selected data.
- Confirm data types and quality.
Report control block tests
- Identify available URCBs and BRCBs.
- Enable the required report control block.
- Verify data-change reporting.
- Verify quality-change reporting.
- Test integrity reporting where supported.
- Test general interrogation.
- Test reconnection and event recovery for BRCBs.
SCADA tests
- Verify point mapping.
- Check indications.
- Check measurements.
- Confirm timestamp handling.
- Verify alarm presentation.
- Test controls separately where applicable.
18. Common Dataset and Control Block Problems
| Problem | Possible cause | Recommended solution |
|---|---|---|
| Dataset cannot be created | Unsupported data attribute | Check the IED data model |
| FCDA reference invalid | Incorrect logical node or data object | Verify the ICD and actual model |
| GOOSE message not transmitted | Incorrect GoCB or publisher configuration | Check control block and communication settings |
| Subscriber receives incorrect signal | Incorrect external reference mapping | Check ExtRef and dataset order |
| Report not received | RCB not enabled or incorrect configuration | Check client association and RCB settings |
| Events lost after disconnection | URCB used where buffering was required | Evaluate BRCB support |
| BRCB recovery incomplete | Buffer overflow or configuration problem | Check buffer capacity and report sequence |
| Quality information incorrect | Wrong data attribute or mapping | Verify quality attributes and functional constraints |
| SCL import fails | Unsupported configuration or schema mismatch | Check the device-specific engineering requirements |
19. Important Engineering Considerations
When working with MiCOM IEC 61850 datasets and control blocks, engineers should pay particular attention to the following.
19.1 Configuration Revision
Changing a dataset or relevant GOOSE control block configuration may require an updated configuration revision.
The publisher and subscribers must be engineered consistently.
19.2 Dataset Ordering
The ordering of dataset members is important when interpreting the transmitted dataset values.
A subscriber must map the correct dataset member to the intended application signal.
19.3 Data Quality
Status and measurement values should not be evaluated without considering quality information.
For example, a measurement may have a numerical value but be marked invalid or questionable.
19.4 Time Information
Timestamp information can be important for event analysis and sequence-of-events reporting.
Correct time synchronization and appropriate timestamp handling are essential.
19.5 Device Compatibility
Do not assume that all MiCOM relays support the same:
- Number of datasets.
- Number of GOOSE control blocks.
- Number of report control blocks.
- Dataset members.
- Trigger options.
- BRCB buffering capacity.
- SCL configuration functions.
Check the exact model and firmware documentation before finalizing the design.
20. Conclusion
Datasets, FCDA references, GOOSE control blocks and MMS report control blocks form an essential part of IEC 61850 engineering.
For MiCOM protection systems, engineers must understand how the data model is structured, how dataset members are selected, how GOOSE information is published and subscribed, and how MMS reports are delivered to SCADA clients.
The distinction between URCB and BRCB is particularly important when designing event reporting and recovery after communication interruptions.
Correct configuration, careful SCL engineering and practical communication testing are necessary to achieve reliable IEC 61850 integration.
21. Practical IEC 61850 and MiCOM Training by Elec-Engg
Elec-Engg provides practical training in power system protection, MiCOM relays, IEC 61850 communication and substation automation.
Training topics include:
- MiCOM protection relay configuration.
- IEC 61850 logical nodes and data models.
- GOOSE datasets and control blocks.
- MMS datasets and report control blocks.
- ICD, CID, IID and SCD engineering.
- URCB and BRCB configuration.
- SICAM PAS integration.
- Wireshark communication analysis.
- Practical testing and commissioning.
Training formats:
- Pre-recorded video courses.
- Structured self-paced training.
- Face-to-face training.
- Customized in-house training.
Practical courses by Dr Saeed Roostaee / Elec-Engg
Website: https://elec-engg.com/
