> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/examples/protection/iec-61850-substation-automation-system-sas.md).

# IEC 61850 Substation Automation System (SAS)

## Description

The **IEC 61850 SAS** example, located in **File > Open an Example File > Protection**, demonstrates how to model an IEC 61850 Substation Automation System in HYPERSIM.

The objectives are to represent IEC 61850-compliant substation hierarchy and IED roles, configure GOOSE and sampled values (SV) communications from an SCD file, and implement and assess two protection applications: breaker failure and reverse blocking. Finally, by simulating the model, the protection applications are analyzed and the logic is corrected if needed.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-122d3c52f514e0e2739e92db8a40042dcca15e20%2Fimage%20(201).png?alt=media" alt=""><figcaption></figcaption></figure>

## Requirements

This example model does not require any additional hardware or licenses.

## Detailed explanation

The protection applications are breaker failure and reverse blocking which are explained in further sections. The communication between devices is based on **GOOSE** and **SV**. An SCD file is used to import GOOSE communication and SV is IEC 61850-9-2 SV LE which is configured in HYPERSIM I/O configuration interface. The model follows IEC 61850 naming conventions for devices and IEDs and enables validation of the protection logic through simulation.

<details>

<summary><strong>Substation structure</strong></summary>

* Two voltage levels: 230 kV, 14.4 kV
* Two power transformers
* Three busbars: 230 kV BUS at 230 kV voltage level, Transfer BUS XF, 14.4 kV BUS A, and 14.4 kV BUS B.
* Twelve bays:
  * At 230 kV:
    * L1, L2 (Line)
    * BP (Busbar Protection)
    * TXA, TXB (Transformer Protection)
  * At 14.4 kV:
    * IncA, IncB (Incomer)
    * BT (Tie Breaker)
    * XF (Busbar XF Protection)
    * A1, A2, B1, B2 (Feeder at busbars 14.4 kV BUS A and BUS B)
* Multiple IEDs per bay perform protection (PU), control (BCU), or both (PUBCU). Merging units (MU) in the process level digitize instrument transformer signals and publish SV to bay units.

</details>

The HYPERSIM model includes all bays listed above, with protection applications implemented using the IncA, IncB, and BT bays. Three-phase Breakers represent circuit breakers, and three-phase Current Probes represent current transformers.

Equipment names reflect their associated bays (for example, CB\_BT for the BT bay breaker). The 14.4 kV busbars are BUS\_A, BUS\_B, and TRANSFER\_XF.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b9636c6a4bf23c7efeda1478b2d12e2eb3aa8c75%2Fimage%20(202).png?alt=media" alt=""><figcaption></figcaption></figure>

Each bay has a protection unit modeled as a HYPERSIM subcircuit (for example, BT\_PU, IncA\_PUBCU, IncB\_PUBCU).

| <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3883394357d296437b8b1a42fd3cbe448b0d66b6%2Fimage%20(161).png?alt=media" alt="" data-size="original"> | <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-dd60de329c437d7155afa81f3c92bbdd3f1edc05%2Fimage%20(203).png?alt=media" alt="" data-size="original"> |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-e97b8c0582bda674c33e79e3ab5b81d210d1448e%2Fimage%20(204).png?alt=media" alt="" data-size="original"> | <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-82b945c8642887cdb6275432f3bb6ba755c6be2e%2Fimage%20(205).png?alt=media" alt="" data-size="original"> |
| <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2cb9fc0c7e89ada8202e1a339b41e1ae1808e03f%2Fimage%20(206).png?alt=media" alt="" data-size="original"> | <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5aeded0f7f94b9e184a711821f6a05d3c293cc68%2Fimage%20(207).png?alt=media" alt="" data-size="original"> |

### **I/O interface configuration**

HYPERSIM I/O Interface Configuration is used to create an IEC 61850 Interface. GOOSE communication from the SCD file is imported via IEC 61850 interface and IEC 61850-9-2 LE was used to configured SV streams.

The current IEC 61850 interface does not import or configure MMS report control blocks.

## GOOSE

The following pictures show the I/O interface for GOOSE publisher and subscribers.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a755cd5fe91cd34e375b85f44a24d89222d46355%2Fimage%20(155).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7ee4d7397c8778eada95ce626e9b1dcac083a5f5%2Fimage%20(156).png?alt=media" alt=""><figcaption></figcaption></figure>

Two GOOSE control blocks are imported from the SCD file for the BT bay protection unit (BT\_PU): **BreakerFailureBT** and **ProtectionBT**.

* BreakerFailureBT publishes **RBRF.OpEx.general** (breaker failure logical node).
* ProtectionBT publishes **PTOC.Str.general** (overcurrent logical node).

The protection unit IEDs at bays IncA and IncB (InaA\_PUBCU and IncB\_PUBCU) are subscribers to the GOOSE messages from BT\_PU.

{% hint style="info" %}
For **more information about logical nodes**, data attributes for different functions, refer to the standard IEC 61850-7-4, IEC 61850-7-3.

For **more information about GOOSE communication**, refer to the standard IEC 61850-8-1.
{% endhint %}

## Sampled values

IEC 61850-9-2 LE publisher and subscriber streams are configured for the BT bay. The stream ID (LD Name) is **IOP\_K\_BT\_MU**, reflecting the merging unit at BT publishing SV to the BT protection unit.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-4e6ebcc4ffac14f13589f6e5c4b6e35b375efb0c%2Fimage%20(157).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c3506316e9ca111da22f98aa4ae84e30f3501d55%2Fimage%20(158).png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
For IEC 61850-9-2 LE, see IEC 61850-9-2 and the IEC 61850-9-2 LE Implementation Guideline.
{% endhint %}

## Protection applications

The SCD file defines two functions implemented between BT, IncA, and IncB: breaker failure and reverse blocking. In HYPERSIM, these use breaker and fault statuses, GOOSE publish/subscribe, and bay IED logic. IED outputs are breaker commands to IncB or IncA.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7e43b25dce08705a38a43a0bdac17ea1d6d4814a%2Fimage%20(159).png?alt=media" alt=""><figcaption></figcaption></figure>

## Simulation and results

### Scenario selection

The **Scenario\_Selector** subcircuit directs the breaker command to either CB\_INCB or CB\_INCA:

* **Scen\_Sel = 1**: Breaker failure (affects **CB\_INCB**)
* **Scen\_Sel = 2**: Reverse blocking (affects **CB\_INCA**)
*

```
<figure><img src="../../.gitbook/assets/image (122).png" alt=""><figcaption></figcaption></figure>
```

## Breaker failure (Scen\_Sel = 1)

According to the SCD file and IEC 61850 engineering, the breaker failure GOOSE control block "BreakerFailureBT" publishes the signal "**RBRF.OpEx.ST.general**" which is the external operating signal from the breaker failure logical node from the protection unit at BT to units from IncA and IncB to inform them of the circuit breaker failure at BT.

{% hint style="info" %}
For the **IEC 61850 data model**, see IEC 61850-7-4 and IEC 61850-7-2.
{% endhint %}

In HYPERSIM, for the sake of simplicity, the **breaker failure** implementation is done between the bays **BT** and **IncB**. When Scen\_Sel = 1, if CB\_BT fails to open within time when a fault occurs, CB\_INCB should operate. If CB\_BT opens in time, CB\_INCB has to stay closed.

## Reverse blocking (Scen\_Sel = 2)

According to the SCD file and IEC 61850 engineering, the reverse blocking GOOSE control block "ProtectionBT" publishes the signal "**PTOC.Str.ST.general**" from the protection unit at the bay BT to protection units from IncA and IncB to block their protection operation.

{% hint style="info" %}
For the IEC 61850 data model, see IEC 61850-7-4 and IEC 61850-7-2.
{% endhint %}

In HYPERSIM, as with Breaker Failure, to make the application easier to analyze, the **reverse blocking** implementation is done between the bays **BT** and **IncA**. So, when Scen\_Sel = 2, if CB\_BT opens within a time limit after fault occurs and tripping signal by the overcurrent relay is sent, CB\_INCA is blocked from opening and stays closed. However, if CB\_BT fails to open after a delay, CB\_INCA will operate and open.

### Workflow

There are two main protection function scenarios in this model and the workflow is the following:

{% stepper %}
{% step %}
The **fault Flt1 at the bay BT operates at 0.2 seconds** and lasts until 0.4 seconds.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3883394357d296437b8b1a42fd3cbe448b0d66b6%2Fimage%20(161).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**CT1\_BT publishes IEC 61850-9-2 SV LE streams** to the BT\_PU IED.
{% endstep %}

{% step %}
The **IED BT\_PU is assigned to the bay** and contains an overcurrent relay which subscribes to the SV streams from CT1\_BT.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6ba0eb8718b5a125aec7ce0a328d37ea4b103c2c%2Fimage%20(162).png?alt=media" alt=""><figcaption></figcaption></figure>

It then detects the fault through instantaneous overcurrent element (50P) and sends a tripping signal which means the output (Q) becomes 1 after the relay time delay which is 0.05 seconds. Based on the CB\_BT operation mode (Op\_Mod), CB\_BT either opens at 0.25 seconds or it fails to open. The following pictures show the BT\_PU IED and elements inside the subcircuit and the relay settings. Notice how the CB\_BT\_Cmd is the output of the subcircuit and is linked to the input of CB\_BT.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a8717347e6c286c1856e865af7dcd5e4e25fb51d%2Fimage%20(163).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3a635a3b05ae7e964c4db39b05c8de2d31b782dc%2Fimage%20(164).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
The **GOOSE message for breaker failure application is being published** and transmits RBRF.OpEx.general.

The other GOOSE message for reverse blocking application transmits PTOC.Str.general.
{% endstep %}

{% step %}
The **status of the breaker CB\_BT is transmitted** to the IEDs at IncA and IncB bays.
{% endstep %}

{% step %}
The **IEDs, IncA\_PUBCU and IncB\_PUBCU receive the GOOSE message** from BT\_PU along with the CB\_BT status. Depending on their internal logic, they send a command to their respective breakers to either open or stay closed.
{% endstep %}

{% step %}
**IncA\_PUBCU is assigned to the bay IncA** and is connected to the reverse blocking protection application.
{% endstep %}
{% endstepper %}

### Load flow

The simulation should be run in steady state so make sure the network is initialized by the load flow.

Open Network → Load Flow, make sure the frequency is at 60 Hz and then press "Execute load flow".

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-e386a89fd4a4f949f5dad562e3b33f1dc4d26809%2Fiec61850-example-loadflow-1.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d0327da23817b625d14fac6f29b54b8c603aa277%2Fiec61850-example-loadflow-2.png?alt=media" alt=""><figcaption></figcaption></figure>

You can also enable performing load flow when simulation starts in the "Simulation Settings".

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6af58b202f7d6cff922e17917ee845e6d524e90a%2Fiec61850-example-loadflow-3.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ac3d9445a9a21e629b77d27ea1f8a2231ff147d6%2Fiec61850-example-loadflow-4.png?alt=media" alt=""><figcaption></figcaption></figure>

### Scenario 1: Breaker failure (Scen\_Sel = 1, Op\_Mod = 2)

Flt1 is activated at 0.2 seconds. The overcurrent relay 5051OC from BT\_PU IED detects the overcurrent and sends a tripping signal at 0.25 seconds. CB\_BT fails to open at that time and so CB\_INCB opens at 0.25 seconds.

{% stepper %}
{% step %}
Set **Scen\_Sel = 1**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5b347540b89e6377d303555437522b71c7c595d8%2Fimage%20(1577).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Set **Op\_Mod = 2** so CB\_BT fails to open.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-40c6922c9a85aff461263e028dfeeef0e850255f%2Fimage%20(1578).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Run the simulation on a target** and again, make sure load flow is executed.

The relay BT\_PU.5051OC will detect the overcurrent after 0.05 seconds delay and Q =1. The signal "**RBRF.OpEx.general**" is published via the GOOSE control block "**BreakerFailureBT**" to **IncB\_PUBCU**. The IED also receives the status for CB\_BT (CB\_BT\_Stat).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2b6584ccb69195450faa6d2937b32456a878bb2a%2Fimage%20(1579).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a13f3b4229efc88c9107bfa6a62d354a97175b95%2Fimage%20(1580).png?alt=media" alt=""><figcaption><p>the logic inside IncB_PUBCU</p></figcaption></figure>

The RBRF\_OpEx\_general block subscribes to the the signal from the overcurrent relay (RBRF.OpEx.general). It is compared with the status of CB\_BT (CB\_BT\_Stat).

If CB\_BT is closed while relay has operated, it means CB\_BT has failed to open and so the command is sent to CB\_INCB to open via CB\_INCB\_Cmd.
{% endstep %}

{% step %}
**Open the ScopView** template "**IEC61850\_SAS.svt**".

The tab "BT\_Relay\_Fault" shows the BT\_PU overcurrent relay input current which are SV subscribes to the CT1\_PU current transformer, the fault status, the relay output (Q), and the CB\_BT input command from BT\_PU IED.

Notice how the CB\_BT input command does not drop to zero to make sure CB\_BT opens during fault. This means CB\_BT has failed to open even though there is a fault and is detected by the BT\_PU overcurrent relay (Q).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3e6831691464722284f441c99eb930745051f4a1%2Fimage%20(1581).png?alt=media" alt=""><figcaption></figcaption></figure>

The following figure is from the tab "Breaker Failure (CB\_INCB)" which shows the status of breakers CB\_BT and CB\_INCB. It is clear how CB\_BT failed to open at 0.25 seconds but CB\_INCB operates at that time and opens its contacts for all phases. This isolates the fault and protects the busbar.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ea35f4e99a547670d4150607a42d0b16b8ddf5a9%2Fimage%20(1582).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Set **Op\_Mod = 1** and view the same tab in ScopeView.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-bcd8d4040cb8363e4609d8cd369dfda42d9cfd0f%2Fimage%20(1583).png?alt=media" alt=""><figcaption><p>CB_BT opens at 0.25 seconds, so CB_INCB stays closed as intended.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

### Scenario 2: Reverse blocking (Scen\_Sel = 2, Op\_Mod = 1)

Flt1 is activated at 0.2 seconds. The overcurrent relay 5051OC from BT\_PU IED detects the overcurrent and sends a tripping signal at 0.25 seconds. If CB\_BT opens at that time, CB\_INCA is blocked from operating. However, if CB\_BT fails to open at 0.25 seconds plus an additional 0.05 seconds, then CB\_INCA has to open.

{% stepper %}
{% step %}
Set **Scen\_Sel = 2**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5b347540b89e6377d303555437522b71c7c595d8%2Fimage%20(1577).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Set **Op\_Mod = 1**

The relay BT\_PU.5051OC will detect the overcurrent after 0.05 seconds delay and Q =1. The signal "**PTOC.Str.general**" is published via the GOOSE control block "**ProtectionBT**" to **IncA\_PUBCU**. The IED also receives the status for CB\_BT (CB\_BT\_Stat).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3a83259d634f38ede6b2553032f7397ef9be1a1d%2Fimage%20(1584).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8cbede0e3d43224ddf246dd9966031d396249d74%2Fimage%20(1585).png?alt=media" alt=""><figcaption><p>the logic inside IncA_PUBCU IED</p></figcaption></figure>

The PTOC\_Str\_general block subscribes to the signal from the overcurrent relay (PTOC.Str.general) and is delayed an additional 0.05 seconds so there is more time for CB\_BT to operate. It is compared with CB\_BT\_Stat and if CB\_BT is open, the blocking signal is sent to CB\_INCA to ensure it stays closed.
{% endstep %}

{% step %}
**Open ScopeView** and the template "IEC61850\_SAS.svt".

The first tab shows the BT\_PU overcurrent relay input current, its output, fault status and the CB\_BT input command. Notice how it has turned to zero meaning CB\_BT has to open at 0.25 seconds.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-582ead717c27a94255b6f6f1da6d4e550a2abcf2%2Fimage%20(1586).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-432abd15c3adf311aebb02ac3a400a064d0ae1d5%2Fimage%20(1587).png?alt=media" alt=""><figcaption><p>The operation of CB_BT and CB_INCA. As expected, CB_BT is open at 0.25 seconds and CB_INCA is blocked and has stayed closed</p></figcaption></figure>
{% endstep %}

{% step %}
Change **Op\_Mod = 2** and view the same tab in ScopeView template.

It is clear how CB\_BT has failed to open and CB\_INCA operates at 0.3 seconds which is 0.25 + 0.05 seconds as intended.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-98c4e36a8fe88b90372cf11bd72cc0f738f08090%2Fimage%20(154).png?alt=media" alt=""><figcaption><p>CB_INCA is blocked from operating as long as CB_BT is performing as expected.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

### GOOSE and SV Monitoring

## GOOSE Status

The tabs "BF GOOSE Data" and "RB GOOSE Data" shows the monitoring data for the GOOSE control blocks "BreakerFailureBT" and "ProtectionBT" respectively for breaker failure and reverse blocking applications.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8a3c92298c0dcbbf60a0bd0aaed9aac91c87172a%2Fimage%20(150).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5e498718a7f438dee7dc9a1ecb34cb5ecd250916%2Fimage%20(151).png?alt=media" alt=""><figcaption></figcaption></figure>

The status data attribute which being monitored to determine the health of the connection between the publisher and subscriber.

* **stNum (Status Number) for publisher and subscriber:** This data attribute increments whenever the status of the GOOSE message changes. So, in the case of the protection functions in this model, whenever the output of the relay BT\_PU.5051OC (Q) changes its status, this number increments by 1. If a connection between publisher and subscriber is maintained, stNum for both publisher and subscriber should be the same value.
* **sqNum (Sequence Number) for publisher and subscriber:** This data attribute increments whenever the GOOSE message is retransmitted which differs for each GOOSE control block. It rests to 0 or 1 (depending on the GOOSE control block parameters). So, in this model, whenever the fault is reinitialized and the relay output changes its status, sqNum resets to 0. sqNum should be the same for both publisher and subscriber as long as their connection is established and maintained.
* **State for subscriber:** This data attribute has the value of 1 when the connection between publisher and subscriber is established. If they lose connection, the value drops to 0. If subscriber falls behind the publisher and so is not un synchronization with it anymore, the value changes to -5.

As shown in the picture, the values for stNum, sqNum for both publisher and subscriber are the same and also State = 1 so a connection has been successfully established between GOOSE publisher and subscriber.

## SV Data

The following figure shows the status for SV from the tab "SV Data" from the ScopeView template.

The data here contains the SV publisher and subscriber current waveforms. The SV Publisher streams are from the output sensors of CT1\_BT and the SV Subscribers are the input sensors of the 5051OC relay from BT\_PU. Each stream is being sampled and the higher the current, the smoother the subscriber waveform will be.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-05d2b79e3f3bfd37bcc00d03b8620e507437f62f%2Fimage%20(152).png?alt=media" alt=""><figcaption></figcaption></figure>

The SV Publisher and Subscriber Quality waveforms are from the constant blocks SVPub\_Q which are publishing the quality value for current SV streams. If the subscriber values are the same as the publisher, as shown in the figure, it means the connection between the publisher and subscriber is valid.

SV Sample Count shows the smpCnt value of the SV stream. This data attribute is typically used for synchronization validation. According to the standard, an IEC 61850-9-2 LE compliant merging unit can publish analog data at a fixed rate which is 80 samples per power cycles. The number of samples per second is 4800 for a 60 Hz system (like this model) and 4000 for a 50 Hz system. The figure shows how smpCnt reaches 4800 in one second.

## Additional Information

### Substation Origins

The model is based on the substation designed by the IEC 61850 User Group under the UCA International User Group (UCAIUG) during the IOP conferences of 2017 and 2019 \[1]. The single line diagram of the model can be seen in the figure below.

Helinks STS, a vendor-independent system configuration tool was used to design the SAS based on the IOP substation \[2]. The design focuses on three bays at the 14.4 kV voltage level: **IncA, IncB, BT**. The result of the SAS design in Helinks STS is an SCD file which contains all information from the substation including communication.

### GOOSE and SV Sensor Mapping

This segment shows the mapping sensors of HYPERSIM library parts to IEC 61850 data from GOOSE and sampled values. The information is given for each bay.

<details>

<summary><strong>BT</strong></summary>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-69ef45f20842e89b12f6039220461fdced762dad%2Fimage%20(1590).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b7dd678a665214c5c28a22af8fab714d38241b95%2Fimage%20(1591).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>BT_PU IED</strong></summary>

5051OC Relay for SV Current Input and PTOC.Str.general publishing

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-df187fdeb09ca95d0e450db787df357d44d877a9%2Fimage%20(1592).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5ff354bd66e5d3c72b5bcc149004a8176480148b%2Fimage%20(1593).png?alt=media" alt=""><figcaption></figcaption></figure>

Gain "RBRF\_OpEx\_general" for RBRF.OpEx.general publishing

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7225a40852b83f72a7d75473b431df3cfb128ef8%2Fimage%20(1594).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d2643d0bfc9700ad66351b3bc9373dd204055ee4%2Fimage%20(1595).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>IncB</strong></summary>

IncB\_PUBCU - Target Analog Input "RBRF\_OpEx\_general" for RBRF.OpEx.general subscription

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a13f3b4229efc88c9107bfa6a62d354a97175b95%2Fimage%20(1580).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-440b497bf7263ad63000013b98d462666439f8a5%2Fimage%20(1596).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>IncA</strong></summary>

InA\_PUBCU - Target Analog Input "PTOC\_Str\_general" for PTOC.Str.general subscription

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8cbede0e3d43224ddf246dd9966031d396249d74%2Fimage%20(1585).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d4c3255f2926eaa529dc0e0f92669ee3d957eca8%2Fimage%20(1597).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

### GOOSE and SV Monitoring Data

<details>

<summary><strong>GOOSE monitoring data for Breaker Failure Application</strong></summary>

Target Analog Input Pub\_BF, Sub\_BF for stNum, sqNum, State

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2b8eed3446a9160dd52faa9ab663b7efd9b90cc1%2Fiec61850-sas-target-ai.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3c7e3bbb8a2d8e0ac48bc472bbe889bc59dbfa51%2Fiec61850-sas-target-ai-2.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-68a9ee4c8f7927adad4a02d5d64f19822aa8d856%2Fiec61850-sas-target-ai-3.png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>GOOSE monitoring data for Reverse Blocking Application</strong></summary>

Target Analog Input Pub\_RB, Sub\_RB for stNum, sqNum, State

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-e09f790125686cf40526f118138551fb552127c9%2Fiec61850-sas-target-ai-4.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5208aa4fb0c407fd39eb98dd661eb609304f5e74%2Fiec61850-sas-target-ai-5.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-e59b4cdd2c15642f68a1d80cac2285358287fff9%2Fiec61850-sas-target-ai-6.png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

### SV IEC 61850-9-2 LE Data

<details>

<summary><strong>Constants SVPub_QA, SVPub_QB, SVPb_QC for Current Quality publishing</strong></summary>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-89bd684b221109e3b4d90209111db0eaa1b9992b%2Fiec61850-sas-target-ai-7.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-cbf307dd263abb193d1c3784c2653bc48e80e5c2%2Fiec61850-sas-target-ai-8.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1eab3a4d5b98cde2f53a07531366153b1f204318%2Fiec61850-sas-target-ai-9.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-61c37dcba34f5c977552f39e12972baba5439092%2Fiec61850-sas-target-ai-10.png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Target Analog Input "Sub_SVQ" for Current Quality subscription</strong></summary>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2a4fb6b60b1f3a29e266371fa927d4751e337307%2Fiec61850-sas-target-ai-11.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f0323b9585deddede5d9108a180e0d2318ed45c0%2Fiec61850-sas-target-ai-12.png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Target Analog Input "Sub_SV" for smpCnt</strong></summary>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f67e6275a1d7254dfa7d3b689fb6ce6a1104decd%2Fiec61850-sas-target-ai-13.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1a89064363d6d6c3f91379131774c6aaa906fb31%2Fiec61850-sas-target-ai-14.png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

## References

\[1] <https://www.ucaiug.org>

\[2] <https://www.helinks.com/>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/hypersim/examples/protection/iec-61850-substation-automation-system-sas.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
