SEL-5032 Architect Tutorial: IEC 61850, GOOSE and SCL Configuration

SEL-5032 acSELerator Architect Software: Complete Guide to IEC 61850 Engineering, GOOSE Configuration, SCL Files and Digital Substation Design

Table Of Contents
  1. Introduction
  2. 1. What Is SEL-5032 acSELerator Architect?
  3. 2. Understanding the Relationship Between Architect and QuickSet
  4. 3. Understanding IEC 61850 Before Using Architect
  5. 4. Understanding SCL Files in SEL Architect
  6. 5. Creating an IEC 61850 Project in Architect
  7. 6. Configuring GOOSE Publications
  8. 7. Understanding GOOSE Datasets
  9. 8. Understanding GOOSE Control Blocks
  10. 9. Configuring GOOSE Subscriptions
  11. 10. Configuring MMS Communication
  12. 11. Sampled Values Engineering in Architect
  13. 12. Editing the SEL IED Server Model
  14. 13. Working with Multiple Manufacturers
  15. 14. Comparing SCL Files and Detecting Changes
  16. 15. Configuration Deployment and IED Upgrade
  17. 16. Practical Example: SEL-451 GOOSE Publisher and SEL-487B Subscriber
  18. 17. Testing IEC 61850 Communication After Architect Configuration
  19. 18. Common SEL Architect Engineering Mistakes
  20. 19. Best Practices for SEL Architect Projects
  21. 20. Frequently Asked Questions About SEL Architect
  22. Conclusion
  23. Learn IEC 61850 and SEL Protection Engineering with Elec-Engg
  24. Official SEL References and Learning Resources

Introduction

IEC 61850 has become one of the most important communication standards in modern substation automation. It allows protection relays, bay controllers, merging units, SCADA systems and other intelligent electronic devices (IEDs) to exchange information using standardized data models and communication services.

However, implementing IEC 61850 in a real substation requires more than connecting Ethernet cables and assigning IP addresses. Engineers must configure logical nodes, data objects, datasets, GOOSE control blocks, MMS reports, Sampled Values and SCL files.

Schweitzer Engineering Laboratories (SEL) provides acSELerator Architect SEL-5032 Software to support IEC 61850 system engineering and configuration.

Architect allows engineers to configure and document IEC 61850 communication systems involving SEL devices and devices from other manufacturers. It supports GOOSE, Sampled Values (SV) and Manufacturing Message Specification (MMS) for station-bus, process-bus and SCADA applications.

This guide explains how SEL-5032 Architect works, its relationship with QuickSet, the role of SCL files, GOOSE publisher and subscriber configuration, dataset engineering, MMS reporting, Sampled Values and practical commissioning.

Whether you are working with SEL-751, SEL-451, SEL-421, SEL-487E, SEL-411L or other supported SEL devices, understanding Architect is an important skill for modern protection and substation automation engineers.

1. What Is SEL-5032 acSELerator Architect?

SEL-5032 acSELerator Architect is an engineering software application developed by SEL for configuring and documenting IEC 61850 systems.

It provides an environment for creating IEC 61850 projects, adding IEDs, managing SCL files and configuring communication relationships between devices.

The software supports three major IEC 61850 communication services:

IEC 61850 serviceMain purposeTypical application
GOOSEFast event-based communicationInterlocking, trips, blocking and status exchange
MMSClient-server communicationSCADA, monitoring, reporting and control
Sampled Values (SV)Transmission of digitized analog measurementsProcess-bus protection systems

Architect also supports engineering and documentation of IEC 61850 system configurations through standardized SCL files.

Main features of SEL Architect

  • Create and organize IEC 61850 projects.
  • Add SEL IEDs to an engineering project.
  • Import and export SCL files.
  • Configure GOOSE publications and subscriptions.
  • Create and edit datasets.
  • Configure MMS buffered and unbuffered reports.
  • Configure supported Sampled Values publications and subscriptions.
  • View and customize supported SEL IED server models.
  • Compare SCL files and identify configuration changes.
  • Validate SCL files against IEC 61850 requirements.
  • Upgrade existing IED CID files.
  • Deploy multiple CID files in a single operation.
  • Rebuild an SCD from multiple SCL files.

The available functions depend on the selected device, its firmware, the supported IEC 61850 edition and the installed Architect and ICD package versions.

2. Understanding the Relationship Between Architect and QuickSet

One of the most common questions among SEL engineers is:

What is the difference between SEL QuickSet and SEL Architect?

Both are important engineering tools, but they have different purposes.

2.1 SEL-5030 acSELerator QuickSet

QuickSet is primarily used for configuring and managing supported SEL protection and control devices.

Typical activities include:

  • Relay settings.
  • Protection element configuration.
  • Protection logic.
  • Device-specific configuration.
  • Communication settings supported by the relay.
  • Commissioning and device management.

2.2 SEL-5032 acSELerator Architect

Architect is primarily used for IEC 61850 system engineering.

Typical activities include:

  • IEC 61850 data modelling.
  • Logical device and logical node management.
  • Dataset configuration.
  • GOOSE publication.
  • GOOSE subscription.
  • MMS reporting.
  • Sampled Values configuration.
  • SCL file management.
  • IEC 61850 communication documentation.

2.3 QuickSet versus Architect

Engineering activityQuickSetArchitect
Protection settingsYesNot its primary purpose
Protection logicSupported device-dependent functionsIEC 61850 communication engineering
Relay configurationYesIEC 61850-related configuration
GOOSE publisher engineeringDevice-dependent settingsYes
GOOSE subscriber engineeringDevice-dependent settingsYes
Dataset engineeringNot its primary purposeYes
MMS report configurationDevice-dependentYes
SCL import/exportNot its primary purposeYes
Logical node modellingDevice-dependentYes
IEC 61850 system documentationLimitedYes

Important: Architect and QuickSet complement each other. Architect does not replace the device-specific protection settings workflow.

For an SEL relay, an engineer may use Architect to develop the IEC 61850 communication configuration and QuickSet to configure the supported relay settings and application logic.

3. Understanding IEC 61850 Before Using Architect

To use Architect effectively, engineers should understand the basic IEC 61850 data model.

IEC 61850 organizes information into a structured hierarchy.

The main elements are:

  1. Physical Device.
  2. Logical Device.
  3. Logical Node.
  4. Data Object.
  5. Data Attribute.

3.1 Physical device

A physical device is the actual IED installed in the substation.

Examples:

  • SEL-751 feeder protection relay.
  • SEL-451 bay controller.
  • SEL-487E transformer protection relay.
  • SEL-421 transmission protection relay.

3.2 Logical device

A logical device is a logical grouping of related functions within an IED.

For example, a protection relay may contain logical devices for protection, measurement, control and other functions.

3.3 Logical node

A logical node represents a particular function or information group.

Examples include:

Logical nodeFunction
PTOCTime-overcurrent protection
PDISDistance protection
PDIFDifferential protection
XCBRCircuit breaker
XSWISwitch or disconnector
MMXUMeasurement
GGIOGeneric input/output
CSWISwitch control
PTRCProtection trip conditioning
RBRFBreaker failure

The availability and exact implementation of logical nodes depend on the IED and its IEC 61850 server model.

3.4 Data object

A data object represents a particular item of information within a logical node.

For example, the XCBR logical node may contain circuit-breaker-related information.

A circuit-breaker position object is commonly represented by Pos.

3.5 Data attribute

A data attribute represents a specific value or property of a data object.

For example, the position information may include:

  • stVal: Status value.
  • q: Quality.
  • t: Timestamp.

A complete IEC 61850 reference may look like:

IED1/PROT/XCBR1.Pos.stVal

This example identifies a circuit-breaker position status value within a logical device and logical node.

Understanding this hierarchy is essential when building datasets and configuring GOOSE or MMS communication.

4. Understanding SCL Files in SEL Architect

One of the most important features of Architect is its ability to import and export Substation Configuration Language (SCL) files.

SCL is an XML-based engineering language defined by IEC 61850-6.

It describes the structure of an IEC 61850 system, including IEDs, communication configuration and relationships between devices.

SEL Architect supports several important SCL file types.

4.1 ICD – IED Capability Description

The ICD file describes the IEC 61850 capabilities of an IED.

It normally contains information about:

  • Logical devices.
  • Logical nodes.
  • Data objects.
  • Data attributes.
  • Communication capabilities.
  • Supported services.
  • Available datasets or configuration capabilities, as defined by the device description.

The ICD is generally supplied by the IED manufacturer.

In an SEL project, the appropriate SEL ICD description is used to introduce the supported device model into the IEC 61850 engineering project.

4.2 IID – Instantiated IED Description

The IID file describes an instantiated IED configuration.

It can be used to represent an IED instance and its associated configuration information within an IEC 61850 engineering workflow.

IID is particularly relevant to engineering processes using the later SCL editions.

4.3 SCD – Substation Configuration Description

The SCD file describes the overall IEC 61850 substation configuration.

It can contain information about:

  • Multiple IEDs.
  • IED communication capabilities.
  • Communication networks.
  • Datasets.
  • GOOSE control blocks.
  • MMS-related configuration.
  • Substation structure.
  • Relationships between publishers and subscribers.

An SCD file is especially important in a multi-vendor substation because it provides a common engineering description of the system.

4.4 CID – Configured IED Description

The CID file contains the configuration intended for a particular IED.

It represents the device-specific configuration extracted or generated from the overall system engineering process.

A CID file is commonly used when transferring an IEC 61850 configuration to an individual IED.

4.5 Comparing the SCL files

File typeFull nameMain purpose
ICDIED Capability DescriptionDescribes an IED’s capabilities
IIDInstantiated IED DescriptionDescribes an instantiated IED
SCDSubstation Configuration DescriptionDescribes the overall substation configuration
CIDConfigured IED DescriptionContains an individual IED configuration

Typical engineering workflow

A simplified workflow is:

  1. Obtain the ICD files from the IED manufacturers.
  2. Import the IED descriptions into the engineering project.
  3. Create the substation configuration.
  4. Configure datasets, GOOSE and MMS communication.
  5. Establish publisher and subscriber relationships.
  6. Validate the project.
  7. Export the SCD.
  8. Generate the appropriate CID files for individual IEDs.
  9. Transfer the configurations to the devices using the supported procedure.
  10. Test the communication and application logic.

The precise file exchange workflow depends on the SCL edition, engineering tools and device capabilities.

5. Creating an IEC 61850 Project in Architect

The first practical step is creating an engineering project.

Architect provides a project editor and IED palette to organize the devices included in the system.

The software supports drag-and-drop device addition and project organization.

Typical project preparation

Before creating the project, collect:

  • IED list.
  • Relay model and ordering codes.
  • Firmware information.
  • ICD files.
  • Network architecture.
  • IP address plan.
  • VLAN plan, where applicable.
  • GOOSE signal list.
  • Dataset requirements.
  • MMS reporting requirements.
  • Sampled Values requirements, if applicable.

Example substation

Consider a 132 kV substation with:

  • One SEL-451 feeder protection relay.
  • One SEL-421 line protection relay.
  • One SEL-487E transformer protection relay.
  • One SEL-487B bus differential relay.
  • One SEL RTAC for automation and data concentration.
  • One station SCADA system.

Architect can be used to develop and document the supported IEC 61850 communication configuration between the devices.

The actual communication services must be checked against the capabilities of each selected IED.

6. Configuring GOOSE Publications

GOOSE is one of the most important IEC 61850 communication services used in protection and substation automation.

GOOSE stands for Generic Object Oriented Substation Event.

It allows an IED to publish event-based information over Ethernet to one or more subscribing IEDs.

Typical applications include:

  • Circuit-breaker interlocking.
  • Busbar protection signals.
  • Breaker-failure initiation.
  • Protection blocking.
  • Direct transfer trip.
  • Trip signals.
  • Disconnector status.
  • Protection scheme coordination.

6.1 What is a GOOSE publisher?

The publisher is the IED that generates and transmits the GOOSE message.

For example, an SEL-451 relay may publish a circuit-breaker status signal.

The information is placed into a dataset and transmitted using a GOOSE control block.

6.2 What is a GOOSE subscriber?

The subscriber is the IED that receives the GOOSE message.

For example, an SEL-487B bus differential relay may subscribe to circuit-breaker status information published by a feeder relay.

The received information can be used by the relay’s supported logic and application functions.

6.3 GOOSE configuration workflow

A simplified GOOSE engineering process includes:

  1. Add the publisher IED to the project.
  2. Select the required data objects.
  3. Create a dataset.
  4. Create or configure a GOOSE control block.
  5. Configure the required communication parameters.
  6. Add the subscriber IED.
  7. Import or access the publisher’s communication description.
  8. Select the required published dataset.
  9. Configure the subscription.
  10. Map received information to the appropriate subscriber application signals.
  11. Validate the project.
  12. Export the required device configuration files.

The exact interface and available settings depend on the installed software version and device capabilities.

7. Understanding GOOSE Datasets

A dataset is a collection of data objects or data attributes grouped together for communication.

For example, a feeder relay may publish the following information:

Dataset memberDescription
Breaker positionOpen/closed status
Feeder tripProtection trip indication
Breaker failureBreaker-failure initiation or status
Protection pickupSelected protection pickup indication
Interlocking statusSelected interlocking signal

The dataset is associated with a GOOSE control block.

When the value of a dataset member changes, the publisher can transmit a new GOOSE message.

Why is dataset engineering important?

A poorly designed dataset can create unnecessary network traffic and make engineering difficult.

A good dataset should:

  • Include only the required signals.
  • Use meaningful data references.
  • Follow the project naming convention.
  • Match the subscriber requirements.
  • Be documented clearly.
  • Be validated before deployment.

Architect provides tools to create and clone datasets, which can simplify configuration when similar communication structures are required across multiple IEDs.

8. Understanding GOOSE Control Blocks

A GOOSE control block defines how an IED publishes a particular dataset.

Important GOOSE parameters include:

ParameterDescription
GoCBGOOSE control block
GoIDGOOSE identifier
APPIDApplication identifier
MAC addressMulticast destination address
VLAN IDVirtual LAN identifier
VLAN priorityEthernet priority
DatasetPublished data collection
MinTimeMinimum retransmission interval
MaxTimeMaximum retransmission interval
ConfRevConfiguration revision

These parameters must be engineered consistently between the publisher and subscriber.

A subscriber must be configured to recognize the correct GOOSE publication.

GOOSE communication example

Consider an SEL-451 publishing the breaker status signal to an SEL-487B.

The publisher dataset contains the required breaker position information.

The SEL-487B subscribes to this information and uses it in its bus protection logic.

The GOOSE communication configuration must be verified at both ends.

Important: Successful GOOSE communication does not automatically mean that the protection application is correct. The received signal must also be mapped to the correct relay logic and tested.

9. Configuring GOOSE Subscriptions

A GOOSE subscription allows an IED to receive information published by another IED.

In Architect, the engineering process involves identifying the required publisher dataset and establishing the subscription relationship.

A typical workflow includes:

  1. Identify the source IED.
  2. Select the required GOOSE publication.
  3. Identify the dataset members.
  4. Add the destination IED.
  5. Configure the subscription.
  6. Map the received signals to the supported destination signals.
  7. Check communication parameters.
  8. Validate the configuration.
  9. Generate the appropriate IED configuration.

Example: Breaker status subscription

Assume:

  • SEL-451 publishes breaker position.
  • SEL-487B receives breaker position.

The bus differential relay uses the received information for the appropriate bus protection application.

The complete system must verify:

  • Correct source IED.
  • Correct dataset.
  • Correct published signal.
  • Correct destination mapping.
  • Correct signal polarity and interpretation.
  • Correct protection logic.
  • Correct response to communication failure.

10. Configuring MMS Communication

MMS stands for Manufacturing Message Specification.

In IEC 61850, MMS is commonly used for client-server communication between IEDs, RTACs and SCADA systems.

Typical applications include:

  • Reading measurements.
  • Reading breaker status.
  • Reading protection indications.
  • Reporting alarms.
  • Event reporting.
  • Remote control.
  • Device monitoring.

10.1 MMS client and server

The MMS server is the IED that makes its data available.

The MMS client connects to the server and reads or receives the information.

For example:

  • SEL-451: MMS server.
  • SEL RTAC: MMS client.
  • SCADA system: Connected through the station automation architecture.

The exact architecture depends on the selected equipment and project requirements.

10.2 Buffered and unbuffered reports

Architect supports the creation and editing of custom buffered and unbuffered MMS reports.

Buffered reports (BRCB):

Buffered reports can retain event information during a temporary communication interruption, subject to the IED’s buffer capacity and configuration.

They are useful when event delivery and recovery are important.

Unbuffered reports (URCB):

Unbuffered reports are generally used for reporting current information without the same event-buffering behavior.

They are useful for applications where temporary interruption and lost event delivery are acceptable according to the system design.

10.3 Report configuration considerations

When configuring MMS reports, engineers should consider:

  • Report control block.
  • Dataset.
  • Trigger options.
  • Integrity period.
  • Buffering requirements.
  • Client association.
  • Report enable/disable behavior.
  • Data quality.
  • Timestamp requirements.

The supported report features depend on the server IED.

11. Sampled Values Engineering in Architect

Architect also supports configuration of Sampled Values publications and subscriptions for supported devices.

Sampled Values are used in IEC 61850 process-bus architectures to transfer digitized current and voltage measurements.

They are particularly important in digital substations where merging units acquire analog signals and publish them over Ethernet.

Typical SV architecture

  1. CTs and VTs provide analog secondary measurements.
  2. A merging unit acquires the measurements.
  3. The merging unit digitizes the measurements.
  4. Sampled Values messages are published over Ethernet.
  5. A compatible protection relay subscribes to the SV stream.
  6. The relay uses the received measurements in its protection algorithms.

Architect and SV

Architect can be used to configure supported SV publications and subscriptions, including IEC 61850-9-2LE and IEC 61869-9 implementations.

However, not every SEL relay supports SV.

Engineers must check the exact relay model, ordering suffix, hardware and firmware before designing the process-bus architecture.

Important SV engineering parameters

  • Sampled Values dataset.
  • SV control block.
  • APPID.
  • Multicast MAC address.
  • VLAN ID.
  • VLAN priority.
  • Sampling profile.
  • Sample count.
  • Synchronization method.
  • Quality information.
  • Subscriber configuration.

A correct SV design must also consider PTP synchronization, network architecture, redundancy and the required performance of the protection application.

12. Editing the SEL IED Server Model

One of Architect’s important features is its ability to view and edit the SEL IED server model for supported devices.

The server model is the IEC 61850 representation of the information and functions available from an IED.

It includes:

  • Logical devices.
  • Logical nodes.
  • Data objects.
  • Data attributes.

For supported SEL devices, Architect allows engineers to customize the server model.

Why is server-model customization useful?

A project may require specific logical nodes or data objects that are not included in the default model.

For example, an automation project may require additional information to be exposed through IEC 61850 MMS or used in other supported communication applications.

Customizing the server model can help align the IED’s information structure with project requirements.

Important considerations

Before modifying a server model:

  • Check the device’s supported functionality.
  • Confirm that the required logical node is supported.
  • Review the applicable SEL documentation.
  • Confirm compatibility with the device firmware.
  • Check the impact on existing SCL files.
  • Validate the resulting configuration.
  • Test the actual IED after deployment.

Do not assume that adding a logical node in the engineering model automatically creates a physical protection function in the relay.

An IEC 61850 data model represents information and functionality exposed by the IED; it does not replace the device’s actual hardware and application capabilities.

13. Working with Multiple Manufacturers

A major benefit of IEC 61850 is that it supports communication between IEDs from different manufacturers.

For example, a substation may contain:

  • SEL protection relays.
  • Siemens SIPROTEC relays.
  • ABB protection relays.
  • Schneider Electric IEDs.
  • Different manufacturers’ merging units.
  • An RTAC or SCADA gateway.

Architect provides tools to configure and document IEC 61850 communication settings between SEL devices and devices from multiple manufacturers.

Example multi-vendor application

Consider a substation where:

  • An SEL-451 publishes feeder breaker status.
  • A Siemens SIPROTEC relay subscribes to the required GOOSE signal.
  • An SEL RTAC collects data through MMS.
  • The SCADA system receives information from the RTAC.

The engineering team can use the appropriate SCL descriptions to establish the communication relationships.

Interoperability does not mean automatic compatibility

Even though IEC 61850 provides standardized communication, engineers must verify:

  • Supported IEC 61850 edition.
  • Logical node implementation.
  • Data object availability.
  • GOOSE dataset compatibility.
  • Communication profile.
  • Quality and timestamp behavior.
  • Control model.
  • Firmware limitations.
  • Vendor-specific implementation details.

The IEDs must be engineered and tested as a complete system.

14. Comparing SCL Files and Detecting Changes

Architect includes tools to compare SCL files and identify changes.

One useful feature is semantic XML comparison.

This helps engineers identify differences between two SCL configurations without relying only on a basic text comparison.

For example, suppose an engineering team receives a revised SCD file.

The new version may include:

  • A changed GOOSE dataset.
  • A new subscriber.
  • Modified network parameters.
  • An updated logical node.
  • A revised communication control block.

A comparison can help identify the changes and assess their impact.

Why is this important?

In large substation projects, several engineering revisions may be produced during design, testing and commissioning.

A controlled SCL revision process helps prevent configuration errors caused by using outdated files.

Recommended practices:

  1. Keep a copy of the original SCL files.
  2. Maintain version numbers.
  3. Record the engineering changes.
  4. Compare revised files before deployment.
  5. Validate the new configuration.
  6. Archive the approved project.
  7. Keep the final CID files with the associated device records.

15. Configuration Deployment and IED Upgrade

Architect provides features for upgrading an existing IED CID file to a new version and deploying multiple CID files in a single operation.

These capabilities can reduce engineering effort when managing several IEDs.

However, deploying a new CID must be controlled carefully.

Before deployment:

  • Verify the target IED.
  • Confirm the correct device configuration.
  • Check the firmware compatibility.
  • Review the configuration differences.
  • Back up the existing configuration.
  • Confirm the approved project revision.
  • Follow the device manufacturer’s transfer procedure.

After deployment:

  • Verify the configuration status.
  • Check the communication relationships.
  • Confirm GOOSE publications and subscriptions.
  • Confirm MMS reporting.
  • Verify the protection application.
  • Perform the required commissioning tests.

16. Practical Example: SEL-451 GOOSE Publisher and SEL-487B Subscriber

Consider a 132 kV busbar protection application.

The substation contains:

  • SEL-451 feeder protection relay.
  • SEL-487B bus differential relay.
  • Ethernet station-bus network.

The requirement is to transmit feeder circuit-breaker status from the SEL-451 to the SEL-487B using GOOSE.

Step 1: Define the signal

The required signal is the feeder circuit-breaker closed status.

Step 2: Identify the source

The source is the SEL-451.

The breaker status is acquired from its assigned input or supported internal signal.

Step 3: Create a dataset

The required breaker status data object is included in a dataset.

Step 4: Configure the GOOSE control block

Configure the GOOSE publication according to the project communication requirements.

Step 5: Configure the subscriber

The SEL-487B is configured to subscribe to the published GOOSE information.

Step 6: Map the received signal

The received information is assigned to the appropriate supported relay logic signal.

Step 7: Validate the configuration

Check the GOOSE configuration and associated SCL files.

Step 8: Test the communication

Use suitable tools to verify that the publisher is transmitting and the subscriber is receiving the correct information.

Step 9: Test the application

Operate the breaker status input and verify the resulting indication and logic response at the SEL-487B.

The complete scheme must also be tested for communication failure and restoration.

This example demonstrates why GOOSE engineering involves more than creating a publisher and subscriber. The physical signal, data model, dataset, communication parameters, subscriber mapping and application logic must all be correct.

17. Testing IEC 61850 Communication After Architect Configuration

Architect supports configuration and documentation, but successful engineering requires independent testing.

The following tools and methods can be useful.

17.1 Wireshark

Wireshark can be used to analyze Ethernet communication.

For GOOSE, engineers can inspect:

  • Publisher MAC address.
  • Destination multicast MAC address.
  • APPID.
  • VLAN information.
  • Dataset references.
  • GoID.
  • stNum.
  • sqNum.
  • ConfRev.
  • GOOSE retransmission behavior.

For MMS, engineers can inspect client-server communication and report traffic.

For SV, engineers can inspect the sampled measurement stream and relevant communication parameters.

17.2 IEDScout

IEDScout can be used to inspect supported IEC 61850 IED data models and communication services.

It is useful for:

  • Browsing logical devices.
  • Browsing logical nodes.
  • Reading data objects.
  • Checking data attributes.
  • Testing supported MMS interactions.
  • Examining IED communication behavior.

17.3 Relay testing equipment

A protection test set, such as an OMICRON CMC, can be used to verify the protection application.

For example:

  1. Inject current and voltage signals.
  2. Verify relay measurements.
  3. Test protection elements.
  4. Verify the required GOOSE signal.
  5. Check subscriber logic.
  6. Verify trip output operation.
  7. Record the results.

The exact test procedure depends on the protection function and system design.

18. Common SEL Architect Engineering Mistakes

ProblemPossible causeRecommended action
GOOSE subscriber does not receive dataIncorrect publisher/subscriber configurationCheck the dataset, control block and subscription
Incorrect GOOSE signalWrong data object or mappingCompare the dataset with the approved signal list
GOOSE configuration rejectedIncompatible parameters or device capabilityCheck the IED ICD and supported features
MMS client cannot access dataServer or report configuration issueVerify server model, association and report settings
Incorrect logical nodeDevice capability or modelling mismatchCheck the supported server model
CID cannot be loadedWrong device version or incompatible configurationVerify firmware and configuration compatibility
SCD contains inconsistent informationIncorrect or outdated engineering filesCompare SCL versions and rebuild the project
SV subscriber receives no measurementsIncorrect SV mapping or profileVerify publisher, subscriber and sampling profile
Unexpected behavior after an updateIncorrect CID deployment or application mappingRestore or compare against the approved configuration
GOOSE communication works but protection does not operateSubscriber signal not correctly assigned to protection logicVerify the complete application and test end to end

19. Best Practices for SEL Architect Projects

For professional IEC 61850 engineering, follow these recommendations:

1. Use the correct ICD package.

SEL provides an ICD package required to configure SEL devices in Architect. Use the version compatible with the installed Architect release and target relay.

2. Maintain consistent naming.

Use clear IED names, logical device names, datasets and signal references.

3. Keep SCL files under revision control.

Maintain original, intermediate and approved files.

4. Separate communication engineering from protection settings.

Understand the roles of Architect and QuickSet.

5. Avoid unnecessary GOOSE data.

Publish only the information required by the receiving IEDs.

6. Verify multi-vendor compatibility.

Check supported logical nodes, data objects, communication services and control models.

7. Validate before deployment.

Use the software validation features and perform an independent engineering review.

8. Test the complete application.

Verify not only that messages are exchanged but also that the receiving IED performs the correct protection or control action.

9. Maintain backups.

Keep approved SCD and CID files together with the corresponding relay settings and documentation.

10. Document every change.

Record revisions, device versions, test results and approved changes.

20. Frequently Asked Questions About SEL Architect

What is SEL-5032 Architect?

SEL-5032 acSELerator Architect is SEL’s engineering software for configuring and documenting IEC 61850 systems, including GOOSE, MMS and Sampled Values.

Is Architect free?

SEL provides Architect software through its official product support page. Check the current licensing and supported-product terms directly with SEL.

What is the difference between SEL Architect and QuickSet?

QuickSet is primarily used for SEL device settings and supported device configuration. Architect is used for IEC 61850 system engineering, including SCL files, GOOSE, MMS and SV communication.

Can Architect configure GOOSE communication?

Yes. Architect supports configuring GOOSE publications and subscriptions for supported devices.

Can Architect configure Sampled Values?

Yes. Architect supports publication and subscription configuration for supported IEC 61850-9-2LE and IEC 61869-9 implementations.

Can Architect create SCD and CID files?

Architect supports importing and exporting SCL files, including SCD and CID configurations. The exact file workflow depends on the project and supported SCL edition.

What is an ICD file?

An ICD file describes the IEC 61850 capabilities and data model of an IED. It is generally supplied by the device manufacturer.

What is an SCD file?

An SCD file describes the overall IEC 61850 substation configuration, including IEDs and their communication relationships.

Can Architect work with other manufacturers’ IEDs?

Yes. Architect provides a way to configure and document IEC 61850 communication between SEL devices and devices from multiple manufacturers. Actual interoperability depends on supported IEC 61850 services and device implementations.

Does Architect replace Wireshark?

No. Architect is an engineering and configuration application. Wireshark is a packet-analysis tool that can be used to inspect actual network communication.

Does Architect replace IEDScout?

No. Architect is used for IEC 61850 engineering and configuration, while IEDScout is useful for inspecting and testing supported IEC 61850 IED communication and data models.

Which Windows versions are supported?

Consult the current SEL-5032 support page for the latest supported operating systems and software requirements. The current published support information should be checked before installation.

Conclusion

SEL-5032 acSELerator Architect is an important engineering tool for protection and substation automation engineers working with IEC 61850 systems.

It provides a common environment for configuring and documenting GOOSE, MMS and Sampled Values communication, managing SCL files, engineering datasets and working with supported SEL IED server models.

For practical substation engineering, the most important skills are understanding the IEC 61850 data model, managing ICD/SCD/CID files, configuring GOOSE publications and subscriptions, and validating the complete communication and protection application.

Architect becomes particularly valuable in multi-vendor substations where engineers must coordinate communication between different protection relays, merging units, bay controllers and automation systems.


Learn IEC 61850 and SEL Protection Engineering with Elec-Engg

Elec-Engg provides practical training and technical education in power system protection, protection relays, IEC 61850 and substation automation.

Our training subjects include:

  • IEC 61850 fundamentals and engineering.
  • SEL-5032 acSELerator Architect.
  • GOOSE publisher and subscriber configuration.
  • SCL files: ICD, IID, SCD and CID.
  • MMS client/server communication.
  • Sampled Values and digital process bus.
  • SEL protection relays and QuickSet.
  • IEDScout and Wireshark.
  • Relay testing and commissioning using OMICRON CMC.

Online training can be arranged based on the required subject and participants’ experience.

For practical training and customized company courses, visit https://elec-engg.com/ or contact us directly.


Official SEL References and Learning Resources

  1. SEL-5032 Architect Software: https://selinc.com/products/5032/
  2. SEL-5032 Software Support and Downloads: https://selinc.com/products/5032/support/
  3. SEL-5032 Documentation: https://selinc.com/products/5032/docs/
  4. SEL-5032 Supported Products: https://selinc.com/products/software/5032-supported-products/
  5. SEL Grid and IEC 61850 engineering resources: https://selinc.com/

Recommended official video lessons

  • acSELerator Architect – Part 1: Creating a Project.
  • acSELerator Architect – Part 2: Creating IEC 61850 GOOSE Publications.
  • acSELerator Architect – Part 3: Creating IEC 61850 GOOSE Subscriptions.
  • acSELerator Architect – Part 4: Creating Data Sets.
  • acSELerator Architect – Using the IED Upgrade Tool.

These lessons are available through SEL’s official product page and video portal.


Leave a Comment

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

Scroll to Top