GE SAS IEC 61850 Configuration: MMS, GOOSE, SCL Engineering, IED Integration and Communication Testing

Table Of Contents
  1. Introduction
  2. 1. IEC 61850 Architecture in GE SAS
  3. 2. Understanding the IEC 61850 Data Model
  4. 3. MMS Communication in GE SAS
  5. 4. IEC 61850 Datasets
  6. 5. Report Control Blocks
  7. 6. GOOSE Communication in GE SAS
  8. 7. SCL Engineering for GE IED Integration
  9. 8. Multi-Vendor IEC 61850 Integration
  10. 9. Practical Example: GE Relay Integration with a Station HMI
  11. 10. Practical Example: GOOSE-Based Feeder Blocking
  12. 11. IEC 61850 Communication Network Design
  13. 12. Testing IEC 61850 Communication
  14. 13. Using IEDScout and Wireshark
  15. 14. Common IEC 61850 Configuration Problems
  16. 15. Practical IEC 61850 Commissioning Checklist
  17. 16. Training on GE SAS IEC 61850 Engineering by Elec-Engg
  18. Conclusion
  19. Frequently Asked Questions
  20. Image

Introduction

IEC 61850 is one of the most important standards used in modern Substation Automation Systems (SAS). It provides a standardized approach to communication, data modelling and engineering between protection relays, bay controllers, station computers and other substation devices.

In a GE-based substation automation project, IEC 61850 can be used to integrate compatible GE Multilin protection relays with third-party IEDs, station-level HMI systems and SCADA gateways.

Successful implementation requires more than connecting devices to an Ethernet network. Engineers must understand the IEC 61850 data model, logical nodes, datasets, report control blocks, GOOSE communication, SCL files, network configuration and device-specific limitations.

This article explains the practical engineering principles of IEC 61850 configuration in a GE-based SAS.

1. IEC 61850 Architecture in GE SAS

IEC 61850 supports communication between substation devices using standardized data models and communication services.

A typical architecture includes:

Bay level

  • GE Multilin protection relays.
  • Bay controllers.
  • Transformer protection IEDs.
  • Feeder protection IEDs.
  • Other compatible protection and control devices.

Station level

  • IEC 61850 client.
  • Station HMI.
  • SCADA gateway.
  • Engineering workstation.
  • Communication switches.

Process level

  • Merging units, where applicable.
  • Digital interface devices.
  • Primary equipment status and measurement interfaces.

The actual architecture depends on the project design and the IEC 61850 services supported by the selected equipment.

2. Understanding the IEC 61850 Data Model

IEC 61850 uses a hierarchical data model to represent substation equipment and functions.

The main elements are:

  1. Server.
  2. Logical device.
  3. Logical node.
  4. Data object.
  5. Data attribute.

2.1 Server

The server represents the IEC 61850 communication endpoint of an IED.

For example, a GE Multilin relay may expose its protection and measurement data through an IEC 61850 server interface if supported by the specific model.

2.2 Logical Device

A logical device groups related functions within an IED.

A relay may contain logical devices associated with protection, measurement, control and monitoring functions.

2.3 Logical Node

Logical nodes represent standardized functions or equipment.

Examples include:

Logical nodeTypical function
PTOCTime overcurrent protection
PIOCInstantaneous overcurrent protection
PDIFDifferential protection
PDISDistance protection
MMXUMeasurement
XCBRCircuit breaker
XSWISwitch
CSWISwitch control
GGIOGeneric process I/O
LLN0Logical device common functions

The actual logical nodes implemented in a GE relay depend on its IEC 61850 data model and firmware.

2.4 Data Objects and Attributes

A logical node contains data objects, which in turn contain data attributes.

For example, an overcurrent protection logical node may expose information such as:

  • Protection start.
  • Protection operate.
  • General protection health.
  • Setting group information.

A circuit-breaker logical node may expose:

  • Position.
  • Operation count.
  • Health.
  • Control-related information.

The exact object references and functional constraints must be taken from the device’s SCL description or manufacturer documentation.

3. MMS Communication in GE SAS

Manufacturing Message Specification (MMS) provides client-server communication commonly used for monitoring and control.

In a typical architecture:

  • The GE relay operates as an IEC 61850 server.
  • The station-level system operates as an IEC 61850 client.
  • The client establishes an association with the server.
  • The client accesses supported data objects.
  • Reports can be used to communicate changes in selected information.

3.1 MMS Applications

MMS communication may be used for:

  • Reading measurements.
  • Monitoring breaker position.
  • Receiving protection indications.
  • Retrieving alarms.
  • Receiving event information.
  • Reading supported settings.
  • Operating supported control points.

The available services depend on the IED implementation.

3.2 Establishing an MMS Association

A typical engineering process includes:

  1. Confirm the relay’s IEC 61850 communication interface.
  2. Configure the correct network parameters.
  3. Verify IP connectivity.
  4. Confirm the server is enabled.
  5. Configure the client with the correct IED information.
  6. Establish the MMS association.
  7. Browse the server data model.
  8. Verify the required data objects.

A successful network ping does not prove that MMS communication is working. Application-level association and data access must also be verified.

4. IEC 61850 Datasets

A dataset is a structured collection of data attributes.

Datasets are used in several IEC 61850 services, including reporting and GOOSE.

For example, a feeder relay dataset may contain:

Dataset memberDescription
Feeder protection startOvercurrent pickup indication
Feeder tripProtection trip indication
Breaker positionCircuit-breaker status
Phase currentCurrent measurement
Earth-fault currentResidual current measurement
Relay healthDevice health information

The selected members must exist in the actual IED data model and be supported by the applicable service.

Dataset engineering should consider:

  • Required information.
  • Data type.
  • Functional constraint.
  • Reporting requirements.
  • GOOSE application requirements.
  • Communication loading.
  • Client compatibility.

Avoid creating unnecessarily large datasets. Organize information according to its intended communication and application purpose.

5. Report Control Blocks

Report Control Blocks (RCBs) are used to configure reporting from an IEC 61850 server to a client.

Reports allow the client to receive selected data changes without continuously polling every data object.

Two common reporting types are:

  • Buffered Report Control Blocks (BRCB).
  • Unbuffered Report Control Blocks (URCB).

5.1 Buffered Reporting

Buffered reporting can retain event information during temporary communication interruptions, subject to the server’s implementation and available buffer capacity.

This is useful for applications where event delivery after reconnection is important.

5.2 Unbuffered Reporting

Unbuffered reporting sends reports when communication conditions and report triggering requirements are satisfied, but does not provide the same event buffering behavior as a buffered report.

5.3 Report Configuration Parameters

Depending on the implementation, relevant parameters may include:

  • Dataset reference.
  • Report ID.
  • Buffer time.
  • Integrity period.
  • Trigger options.
  • Optional fields.
  • Client association.
  • Buffer time and retention behavior.

The engineering team must verify the reporting behavior supported by the GE relay and the station-level client.

6. GOOSE Communication in GE SAS

GOOSE is used for fast event-based communication between IEDs.

Unlike MMS client-server communication, GOOSE uses a publisher-subscriber model.

A publisher sends multicast Ethernet messages containing dataset information. Subscribers receive the messages and map the selected information to their internal logic.

Typical applications include:

  • Feeder protection blocking.
  • Transformer protection interlocking.
  • Breaker failure initiation.
  • Breaker position exchange.
  • Intertrip.
  • Busbar protection signals.

6.1 GOOSE Publisher Engineering

The publisher configuration generally requires:

  1. Selecting the required data objects.
  2. Creating a GOOSE dataset.
  3. Configuring the GOOSE control block.
  4. Assigning the communication parameters.
  5. Enabling publication.
  6. Validating the generated configuration.
  7. Testing actual transmission.

6.2 GOOSE Subscriber Engineering

The subscriber configuration generally requires:

  1. Identifying the publisher.
  2. Selecting the correct GOOSE control block.
  3. Identifying the required dataset member.
  4. Mapping the signal to an internal application point.
  5. Connecting it to the required logic.
  6. Configuring supervision and failure behavior.
  7. Testing normal and abnormal communication conditions.

6.3 GOOSE Communication Parameters

Important parameters include:

  • APPID.
  • Destination multicast MAC address.
  • VLAN ID.
  • VLAN priority.
  • Dataset reference.
  • GOOSE control block reference.
  • Configuration revision.
  • Minimum and maximum retransmission intervals.

These values must be consistent with the approved network and system configuration.

7. SCL Engineering for GE IED Integration

Substation Configuration Language (SCL) provides a standardized way of describing IEC 61850 IEDs and system configurations.

The common SCL file types include:

FilePurpose
ICDDescribes IED capabilities
IIDDescribes an instantiated IED
CIDContains a configured IED description
SCDDescribes the complete substation configuration
SSDDescribes the system specification

7.1 ICD Files

The ICD file describes the capabilities and supported IEC 61850 data model of an IED.

For GE relay engineering, obtain the correct ICD file for the actual product, firmware and IEC 61850 implementation.

7.2 IID Files

An IID file can describe an instantiated IED configuration and is used in supported system engineering workflows.

7.3 CID Files

A CID file contains the configured description intended for a particular IED.

The engineering environment may generate or use CID files when transferring configuration to a device.

7.4 SCD Files

An SCD file describes the complete substation configuration, including relevant IED descriptions and communication information.

It is commonly used in system-level engineering and multi-vendor integration.

7.5 Practical SCL Workflow

A typical workflow is:

  1. Collect IED capability files.
  2. Import the files into the system engineering tool.
  3. Define the substation structure.
  4. Configure IED names and communication access points.
  5. Configure datasets.
  6. Configure report control blocks.
  7. Configure GOOSE publishers.
  8. Configure GOOSE subscribers.
  9. Validate references.
  10. Export the required configured IED files.
  11. Transfer the configuration using the supported manufacturer tools.
  12. Perform communication and functional testing.

The exact sequence varies between engineering platforms.

8. Multi-Vendor IEC 61850 Integration

A modern substation may contain devices from multiple manufacturers.

For example:

  • GE Multilin feeder relay.
  • Siemens SIPROTEC 5 transformer relay.
  • ABB Relion busbar protection IED.
  • Schneider Electric bay controller.
  • Station-level IEC 61850 client.

IEC 61850 provides a common framework, but interoperability still requires careful engineering.

Important checks

  • Supported IEC 61850 edition.
  • Logical node implementation.
  • Data object references.
  • Functional constraints.
  • Dataset compatibility.
  • GOOSE data types.
  • Control models.
  • Report control behavior.
  • SCL compatibility.
  • Firmware limitations.

A common IEC 61850 standard does not guarantee that every feature is implemented identically by every manufacturer.

9. Practical Example: GE Relay Integration with a Station HMI

Consider a GE feeder relay connected to a station-level IEC 61850 client.

The HMI must display:

  • Circuit-breaker position.
  • Phase currents.
  • Earth-fault current.
  • Protection start.
  • Protection trip.
  • Relay health.
  • Communication status.

A typical workflow is:

  1. Confirm that the relay supports the required IEC 61850 server services.
  2. Obtain the correct SCL description.
  3. Configure the relay communication interface.
  4. Verify network connectivity.
  5. Import the IED description into the client engineering environment.
  6. Identify the required data objects.
  7. Configure datasets and reports as appropriate.
  8. Map the data to HMI points.
  9. Configure engineering units and scaling.
  10. Test each indication against the physical equipment or relay simulation.

The HMI should distinguish invalid or unavailable data from a valid zero value.

10. Practical Example: GOOSE-Based Feeder Blocking

Consider two feeder protection relays.

The downstream feeder relay detects a fault and publishes a blocking signal to the upstream relay.

An illustrative logic expression is:

UPSTREAM_BLOCK = DOWNSTREAM_OC_START

UPSTREAM_TRIP = UPSTREAM_OC_PICKUP AND NOT UPSTREAM_BLOCK

The actual logic must include the appropriate protection stages, timers, signal supervision and communication-failure philosophy.

Testing sequence

  1. Apply a test current to the downstream relay.
  2. Verify downstream overcurrent pickup.
  3. Verify that the GOOSE publisher changes state.
  4. Confirm that the upstream relay receives the signal.
  5. Confirm that the intended upstream protection stage is blocked.
  6. Remove the test current.
  7. Verify the signal returns to normal.
  8. Test communication loss according to the approved procedure.
  9. Verify that the protection system responds as designed.

This application requires particular attention to fail-safe behavior and backup protection coordination.

11. IEC 61850 Communication Network Design

IEC 61850 communication depends on an appropriately engineered Ethernet network.

Important design topics include:

Ethernet switches

Use suitable managed switches and configure the required ports, VLANs, multicast forwarding and redundancy features.

VLAN configuration

VLANs can separate different types of traffic, including protection GOOSE, station-level MMS and network management.

Quality of Service

Priority tagging may be used to prioritize time-critical communication.

Multicast management

GOOSE uses multicast Ethernet communication. Switches must forward the required messages to the intended subscribers.

Redundancy

PRP and HSR may be used in appropriate architectures, where supported by the connected IEDs and network equipment.

Network loading

The design should consider:

  • Number of IEDs.
  • Number of GOOSE publishers.
  • Dataset sizes.
  • Event traffic.
  • MMS reporting.
  • Network background traffic.
  • Redundancy overhead.

12. Testing IEC 61850 Communication

Testing should cover both protocol-level communication and the complete protection or control application.

12.1 MMS testing

Verify:

  • Server availability.
  • Client association.
  • Data-model browsing.
  • Data reading.
  • Report operation.
  • Event reception.
  • Control operation, where applicable.

12.2 GOOSE testing

Verify:

  • Publisher transmission.
  • Destination MAC address.
  • APPID.
  • VLAN configuration.
  • Dataset contents.
  • State changes.
  • Subscriber reception.
  • Internal signal mapping.
  • Communication-loss supervision.

12.3 SCL testing

Verify:

  • Correct IED descriptions.
  • Correct references.
  • Dataset membership.
  • GOOSE control blocks.
  • Subscriber configuration.
  • Configuration revisions.
  • Compatibility with the actual devices.

12.4 End-to-end testing

An end-to-end test must demonstrate that the complete function works.

For example:

Protection relay pickup → GOOSE transmission → Ethernet network → subscriber reception → internal logic → output operation.

A packet capture alone is not sufficient to prove correct protection behavior.

13. Using IEDScout and Wireshark

IEDScout

IEDScout is useful for inspecting IEC 61850 devices and data models, depending on the version and supported functions.

It can assist with:

  • Device discovery.
  • Logical device browsing.
  • Logical node inspection.
  • Data object inspection.
  • MMS communication diagnostics.
  • Monitoring supported data attributes.

Wireshark

Wireshark provides packet-level network diagnostics.

For GOOSE analysis, engineers can examine:

  • Source MAC address.
  • Destination MAC address.
  • APPID.
  • VLAN information.
  • GOOSE control block reference.
  • Dataset reference.
  • stNum.
  • sqNum.
  • confRev.
  • timeAllowedToLive.
  • Dataset values and quality.

For MMS troubleshooting, engineers can inspect the relevant Ethernet and transport-layer traffic and, where supported and appropriately configured, application-layer communication.

Packet captures should be taken from a suitable network location, such as a configured switch mirror port or network TAP.

14. Common IEC 61850 Configuration Problems

ProblemPossible causeInvestigation
MMS association failsIncorrect server configuration or network settingsVerify IP connectivity and server availability
Client cannot browse expected dataIncorrect data model or unsupported objectCheck the actual IED model and SCL description
Reports are not receivedIncorrect RCB configurationCheck dataset, trigger options and client association
GOOSE subscriber does not receive messagesMulticast, VLAN or control block configuration errorInspect switch configuration and packet captures
GOOSE signal has incorrect valueIncorrect dataset member mappingCompare publisher dataset and subscriber mapping
SCL import failsUnsupported file features or invalid referencesValidate the SCL file and tool compatibility
Events have incorrect timestampsTime synchronization problemCheck NTP, SNTP, PTP or other configured time source
Control command is rejectedIncorrect control model or authorityReview device control configuration and permissions
Communication fails after configuration changesInconsistent configuration revisionsCompare approved and downloaded configurations

15. Practical IEC 61850 Commissioning Checklist

IED preparation

  • Confirm device model and firmware.
  • Confirm IEC 61850 capability.
  • Obtain correct SCL files.
  • Configure communication interfaces.
  • Verify IP addressing.

MMS engineering

  • Verify server availability.
  • Establish client association.
  • Browse data models.
  • Configure datasets.
  • Configure reports.
  • Test required control services.

GOOSE engineering

  • Configure publisher datasets.
  • Configure GOOSE control blocks.
  • Verify APPID and multicast MAC.
  • Verify VLAN settings.
  • Configure subscribers.
  • Verify internal signal mapping.
  • Test communication failure.

SCL engineering

  • Validate IED descriptions.
  • Verify logical device and logical node references.
  • Check datasets and external references.
  • Verify GOOSE subscriptions.
  • Archive final configuration files.

Commissioning

  • Test MMS communication.
  • Test GOOSE communication.
  • Test HMI indications.
  • Test SCADA mapping.
  • Test protection logic.
  • Test control and interlocking.
  • Verify time synchronization.
  • Complete end-to-end testing.

16. Training on GE SAS IEC 61850 Engineering by Elec-Engg

IEC 61850 engineering is a practical discipline requiring a combination of protection knowledge, communication understanding and configuration experience.

Elec-Engg provides practical technical training by Dr Saeed Roostaee (Electrical Engineering).

Relevant subjects include:

  • GE Multilin protection relay configuration.
  • IEC 61850 architecture and data modelling.
  • MMS client-server communication.
  • GOOSE publisher and subscriber configuration.
  • SCL engineering.
  • Multi-vendor IED integration.
  • Siemens SIPROTEC 5 and DIGSI 5.
  • SICAM PAS integration.
  • IEDScout and Wireshark diagnostics.
  • IEC 61850 testing and commissioning.

Training is available through pre-recorded video courses, structured self-paced training, live online training, face-to-face delivery and customized in-house programs.

Explore courses and technical resources at https://elec-engg.com/ or contact us through https://elec-engg.com/contact/.

Conclusion

IEC 61850 is a fundamental technology for modern substation automation engineering.

In GE-based SAS applications, it can provide standardized communication between compatible protection relays, bay controllers, station-level systems and other manufacturers’ equipment.

The most important engineering activities include understanding the data model, configuring MMS and GOOSE, managing SCL files, designing the Ethernet network and performing complete functional testing.

The successful implementation of IEC 61850 depends on verifying the actual capabilities of each IED and ensuring that communication signals are correctly integrated into the protection and control application.

Frequently Asked Questions

1. What is IEC 61850 used for in GE SAS?

It provides standardized communication, data modelling and engineering between compatible protection relays, bay controllers and station-level automation systems.

2. Can GE Multilin relays support MMS?

Selected GE Multilin models provide IEC 61850 MMS server functionality. The exact services must be verified for the specific model, firmware and communication hardware.

3. Can GE Multilin relays publish and subscribe to GOOSE?

This depends on the specific product implementation. Confirm the required GOOSE publisher and subscriber capabilities in the applicable manufacturer documentation.

4. What is an IEC 61850 dataset?

A dataset is a defined collection of data attributes used by communication services such as reporting and GOOSE.

5. What is the difference between BRCB and URCB?

BRCB is a buffered report control block, while URCB is an unbuffered report control block. Their behavior and availability depend on the IED implementation.

6. Why are SCL files important?

They provide standardized descriptions of IED capabilities and configured substation communication systems.

7. Can IEDScout be used for GE relay troubleshooting?

IEDScout can help inspect IEC 61850 devices and supported data models. Its usefulness depends on the device’s services and the tool version.

8. What is the role of Wireshark?

Wireshark is used to inspect communication packets and troubleshoot network-level problems, including GOOSE transmission.

9. Does IEC 61850 eliminate hardwired connections?

No. IEC 61850 can reduce selected signal wiring, but conventional hardwired interfaces remain necessary in many protection, control and safety applications.

10. What should be tested before commissioning an IEC 61850 system?

MMS, GOOSE, SCL configuration, signal mapping, time synchronization, protection logic, interlocking, HMI, SCADA and communication-failure behavior should all be verified.



GE SAS, GE Multilin, IEC 61850, MMS, GOOSE, SCL, ICD, IID, CID, SCD, Report Control Block, Dataset, IEDScout, Wireshark, Substation Automation, Relay Communication, Elec-Engg

Image

  1. IEC 61850 data model hierarchy showing server, logical device, logical node and data object.
  2. MMS client-server communication architecture in a substation.
  3. GOOSE publisher and subscriber communication diagram.
  4. IEC 61850 SCL file engineering workflow.
  5. Wireshark GOOSE packet analysis.
  6. Multi-vendor IEC 61850 station bus architecture.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top