GE SAS Alarm and Event Management: Alarm Priorities, Sequence of Events, Time Synchronization, Disturbance Analysis and Operational Troubleshooting

Table Of Contents
  1. Introduction
  2. 1. Understanding Alarms, Events, Indications and SOE
  3. 2. Typical GE SAS Alarm and Event Architecture
  4. 3. Alarm Classification and Priority Engineering
  5. 4. Alarm Lifecycle and Acknowledgement
  6. 5. Alarm Flooding and Suppression
  7. 6. Sequence of Events Engineering
  8. 7. Time Synchronization in GE SAS
  9. 8. Practical SOE Analysis: Feeder Fault
  10. 9. Correlating SOE with Oscillography
  11. 10. IEC 61850 Alarm and Event Integration
  12. 11. Alarm and Event Integration with IEC 60870-5-104
  13. 12. Alarm and Event Troubleshooting
  14. 13. Practical Testing Procedure for Alarm and SOE Systems
  15. 14. Alarm and Event Management Design Checklist
  16. 15. Recommended Engineering Documents
  17. 16. Conclusion
  18. 17. Practical Training by Elec-Engg
  19. Frequently Asked Questions

Introduction

Alarm and event management is one of the most important functions of a Substation Automation System (SAS). A modern substation may contain dozens of protection relays, bay controllers, meters, circuit breakers, communication devices and station-level servers. Each device can generate operational indications, warnings, alarms and event records.

When a disturbance occurs, operators and protection engineers need to identify what happened, which protection function operated, which circuit breaker received a trip command, whether the breaker opened successfully and whether the entire sequence followed the expected protection philosophy.

A poorly engineered alarm system can make this investigation difficult. Duplicate alarms, incorrect priorities, missing timestamps, communication delays and unsynchronized IED clocks can create confusion during critical operating conditions.

In a GE-based Substation Automation System, alarm and event engineering must coordinate information from GE Multilin protection relays, bay controllers, station-level applications and SCADA gateways. The actual functions and configuration procedures depend on the installed equipment, software platform, firmware and communication architecture.

This article explains how to engineer alarm and event management in GE SAS, including alarm classification, event collection, time synchronization, sequence-of-events analysis, disturbance investigation, testing and troubleshooting.

1. Understanding Alarms, Events, Indications and SOE

These terms are related but have different operational meanings.

1.1 Indications

An indication represents a status or measured condition.

Examples include:

  • Circuit breaker open.
  • Circuit breaker closed.
  • Disconnector open.
  • Local control selected.
  • Remote control selected.
  • Protection relay healthy.
  • DC supply healthy.
  • Transformer temperature.

Indications are generally used to show the present state of equipment or a measured quantity.

1.2 Alarms

An alarm informs the operator that an abnormal condition requires attention.

Examples include:

  • Transformer differential protection operated.
  • Circuit breaker trip circuit supervision alarm.
  • Relay self-supervision failure.
  • DC supply failure.
  • Low transformer oil level.
  • IED communication failure.

An alarm may remain active until the underlying condition is cleared.

1.3 Events

An event records that a particular occurrence happened at a specific time.

Examples include:

  • Protection element started.
  • Protection trip output operated.
  • Circuit breaker changed from closed to open.
  • Operator issued a switching command.
  • Communication association was lost.
  • Gateway changed operating state.

An event is generally historical information. It does not necessarily represent an active abnormal condition.

1.4 Sequence of Events

Sequence of Events (SOE) is a time-ordered record of events from multiple devices.

SOE is especially important when several protection and control devices operate during a disturbance.

For example, a feeder fault may produce the following sequence:

  1. Protection relay detects the fault.
  2. Overcurrent protection starts.
  3. Trip output operates.
  4. Circuit breaker trip coil is energized.
  5. Breaker auxiliary contact changes state.
  6. HMI receives the breaker-open indication.
  7. Remote SCADA receives the updated status.

SOE allows engineers to reconstruct this sequence and compare it with the approved protection and control design.

2. Typical GE SAS Alarm and Event Architecture

Alarm and event information may originate from different levels of the substation automation system.

2.1 Protection relays

Protection relays generate events associated with:

  • Protection element pickup.
  • Protection element dropout.
  • Protection trip.
  • Breaker failure initiation.
  • Auto-reclosing operation.
  • Teleprotection signals.
  • Relay self-supervision.
  • Setting group changes.
  • Disturbance recording.

GE Multilin relay families may provide event records, fault records, oscillography and communication data, depending on the particular model and configuration.

2.2 Bay control devices

Bay controllers may generate events associated with:

  • Circuit breaker status.
  • Disconnector operation.
  • Interlocking conditions.
  • Local/remote control.
  • Switching commands.
  • Command rejection.
  • Control authority changes.

2.3 Station-level systems

Station-level HMI and servers may record:

  • Alarm acknowledgement.
  • Operator login and logout.
  • Control requests.
  • Communication status changes.
  • Application failures.
  • Database errors.
  • Server redundancy transitions.

2.4 SCADA gateway

The gateway may record:

  • Remote communication failure.
  • Protocol connection establishment.
  • Connection loss and recovery.
  • Remote command reception.
  • Point quality changes.
  • Gateway failover.
  • Data processing or mapping errors.

A clear architecture should identify which device is the original source of each event and which systems store, display or forward it.

3. Alarm Classification and Priority Engineering

Alarm classification should be defined before HMI and gateway configuration begins.

The purpose is to help operators distinguish urgent protection or equipment conditions from routine maintenance information.

3.1 Typical alarm categories

Protection alarms

  • Transformer differential protection operated.
  • Busbar differential protection operated.
  • Distance protection operated.
  • Overcurrent protection operated.
  • Earth-fault protection operated.
  • Restricted earth-fault protection operated.
  • Breaker failure protection operated.

Circuit breaker alarms

  • Trip circuit supervision failure.
  • Spring charging failure.
  • Pole discrepancy.
  • Breaker mechanism abnormality.
  • Low gas pressure, where applicable.
  • Breaker operating time abnormality.

Transformer alarms

  • Buchholz alarm.
  • Oil temperature high.
  • Winding temperature high.
  • Cooling system failure.
  • Oil level abnormal.
  • Pressure relief device operated.

Communication alarms

  • IED communication failure.
  • Ethernet link failure.
  • Station bus communication failure.
  • Gateway communication failure.
  • Remote control centre communication failure.
  • Time synchronization failure.

Auxiliary system alarms

  • DC supply failure.
  • Battery charger failure.
  • AC auxiliary supply failure.
  • UPS failure.
  • Station service transformer alarm.

The actual alarm list must be developed from the project signal list, equipment design and utility operating philosophy.

3.2 Defining alarm priorities

A practical priority structure may include:

PriorityGeneral meaningExample
CriticalImmediate operational response may be requiredBusbar protection operated
HighSerious equipment or system abnormalityTransformer protection alarm
MediumAbnormal condition requiring investigationProtection relay communication failure
LowMaintenance or advisory informationTime synchronization warning

This classification is illustrative. The final alarm priorities must be approved by the operating utility.

3.3 Alarm priority is not the same as alarm state

An alarm has several attributes:

  • Priority.
  • Active or cleared state.
  • Acknowledged or unacknowledged state.
  • Source device.
  • Timestamp.
  • Description.
  • Quality.
  • Associated bay or equipment.

An alarm may be critical but already cleared. It may also be active but acknowledged.

The HMI should display these attributes clearly rather than combining them into a single status.

4. Alarm Lifecycle and Acknowledgement

A typical alarm lifecycle includes the following stages:

  1. Normal condition.
  2. Abnormal condition detected.
  3. Alarm becomes active.
  4. Operator receives the alarm.
  5. Operator acknowledges the alarm.
  6. Underlying abnormal condition is investigated.
  7. Condition returns to normal.
  8. Alarm clears or is reset according to the configured logic.
  9. Historical record remains available.

4.1 Acknowledgement

Acknowledgement means that an operator has recognized the alarm.

It does not prove that the equipment is healthy or that the problem has been corrected.

For example, when a transformer cooling system failure alarm appears:

  • The operator acknowledges the alarm.
  • The alarm remains active while the cooling system is unavailable.
  • Maintenance personnel investigate the cooling system.
  • The alarm clears when the underlying condition is restored.

4.2 Alarm reset

Reset behavior depends on the source device and alarm logic.

Some alarms clear automatically when the condition disappears. Others require a manual reset or a separate acknowledgement and reset sequence.

The HMI must not clear a protection alarm merely because the operator acknowledges it.

4.3 Alarm latching

Certain important protection and equipment alarms may be latched.

For example, a protection trip indication may remain active after the physical fault has disappeared, until the required reset condition is satisfied.

The project should document:

  • Which alarms are latched.
  • Which device performs the latching.
  • Which reset conditions are required.
  • Whether reset is local or remote.
  • Whether operator authorization is required.

5. Alarm Flooding and Suppression

Alarm flooding occurs when a large number of alarms are generated in a short period.

This frequently happens during major disturbances.

For example, a busbar fault may produce:

  • Busbar protection operation.
  • Multiple feeder trip indications.
  • Circuit breaker open indications.
  • Protection relay start and trip events.
  • Communication changes.
  • Transformer or feeder alarms.
  • Gateway status changes.

The operator may receive dozens of messages even though they originate from one initiating fault.

5.1 Causes of alarm flooding

Common causes include:

  • Poor alarm classification.
  • Excessive reporting of internal signals.
  • Duplicate alarm mapping.
  • Incorrect alarm thresholds.
  • Chattering binary inputs.
  • Unstable communication.
  • Repeated alarm generation without deadband or filtering.
  • Incorrect alarm latching and reset behavior.

5.2 Alarm rationalization

Alarm rationalization is the process of reviewing every alarm to determine whether it is useful and how it should be presented.

For each alarm, engineers should define:

  • Alarm name.
  • Source device.
  • Operational meaning.
  • Priority.
  • Required operator response.
  • Activation condition.
  • Clearing condition.
  • Latching behavior.
  • Suppression rules, if permitted.

An alarm without a clear operational meaning or required response should be reviewed.

5.3 Alarm suppression

Suppression may be required during approved maintenance or testing activities.

However, suppression should be controlled and recorded.

A proper design should define:

  • Authorized users.
  • Permitted alarm categories.
  • Suppression duration.
  • Operator indication of suppressed alarms.
  • Audit records.
  • Automatic restoration rules.
  • Restrictions for critical alarms.

Protection trips and other critical indications should not be casually suppressed.

6. Sequence of Events Engineering

SOE engineering ensures that important events from different IEDs can be placed in a reliable chronological sequence.

The quality of SOE depends on several factors:

  1. Timestamp accuracy.
  2. Time synchronization.
  3. Event resolution.
  4. Source identification.
  5. Communication handling.
  6. HMI sorting and display.
  7. Data storage and retrieval.

6.1 Event source identification

Every event should have an identifiable source.

For example:

EventPossible source
Overcurrent pickupProtection relay
Protection tripProtection relay
Breaker open indicationBay controller or relay
Breaker failure startProtection relay
Operator commandHMI or gateway
IED communication lossHMI, gateway or network monitoring system
Gateway failoverGateway application

Engineers should avoid creating duplicate events from the same physical condition unless the duplication has a defined operational purpose.

6.2 Event timestamp versus reception timestamp

A critical distinction exists between:

  • Source timestamp: when the event was detected or recorded by the originating device.
  • Reception timestamp: when another system received the event.

These timestamps may differ because of network delay, processing time or communication buffering.

For fault analysis, the original source timestamp is generally more useful when it is valid and sufficiently accurate.

6.3 Event resolution

The event resolution determines how precisely the system can distinguish the timing of events.

If a protection relay records events with millisecond resolution, but the HMI only displays whole seconds, important timing information may be lost.

The project should define the required timestamp resolution and confirm that all devices and applications support it.

7. Time Synchronization in GE SAS

Time synchronization is fundamental to reliable SOE analysis.

If different IEDs have different clock offsets, the event sequence displayed by the HMI may not represent the actual order of operations.

7.1 Common synchronization methods

Depending on the installed equipment, synchronization may use:

  • SNTP.
  • NTP.
  • PTP.
  • IRIG-B.
  • GPS-based clocks.

The selected method must be compatible with the equipment and the required timing accuracy.

7.2 SNTP and NTP

SNTP and NTP distribute time information over IP networks.

They are commonly used for station-level synchronization and general event timestamp coordination.

However, their achieved accuracy depends on:

  • Network topology.
  • Network congestion.
  • Server quality.
  • Device implementation.
  • Synchronization interval.
  • Network asymmetry.
  • Device clock behavior.

They should not automatically be assumed to provide the same timing performance as precision time synchronization methods.

7.3 PTP

Precision Time Protocol (PTP), defined in IEEE 1588, can provide more accurate synchronization in appropriately engineered networks.

Its performance depends on the supported PTP profile, device implementation, network components and configuration.

Not every protection relay or switch supports the same PTP profile.

7.4 IRIG-B

IRIG-B is a time distribution method used in many substation and protection applications.

It may be distributed through dedicated wiring from a GPS clock or another time source.

The actual interface and format must be checked against the device specifications.

7.5 Time synchronization architecture

A typical architecture may include:

  1. GPS antenna and receiver.
  2. Station master clock.
  3. Time distribution network.
  4. Ethernet switches or dedicated time wiring.
  5. Protection relays.
  6. Bay controllers.
  7. HMI and gateway systems.

The project should identify the primary time source and define behavior when it becomes unavailable.

7.6 Time synchronization alarms

The system should provide clear indications for:

  • Time synchronization lost.
  • Time source unavailable.
  • Clock offset outside the permitted range.
  • PTP grandmaster change, where applicable.
  • Time server communication failure.
  • Device clock not synchronized.

The exact alarms depend on device capabilities.

8. Practical SOE Analysis: Feeder Fault

Consider a medium-voltage feeder protected by a GE Multilin relay.

The feeder experiences a phase-to-earth fault.

An illustrative event sequence is:

TimeDeviceEvent
14:32:10.100Protection relayEarth-fault element starts
14:32:10.250Protection relayTrip condition satisfied
14:32:10.255Protection relayTrip output operates
14:32:10.270Bay controllerBreaker trip command indication
14:32:10.330Circuit breakerOpen auxiliary contact changes
14:32:10.350HMIBreaker-open indication received
14:32:10.380SCADA gatewayUpdated status transmitted

These values are illustrative and must not be treated as expected operating times for a specific relay or breaker.

8.1 Engineering interpretation

The protection engineer should investigate:

  • Did the correct protection element start?
  • Was the pickup value appropriate?
  • Was the configured operating delay correct?
  • Did the relay issue a trip command?
  • Did the circuit breaker open?
  • Was the breaker operating time within specification?
  • Did the HMI receive the correct status?
  • Did the remote SCADA receive the correct indication?

8.2 Correlation with disturbance records

SOE should be correlated with:

  • Relay event records.
  • Oscillography.
  • Fault records.
  • Circuit breaker operation records.
  • HMI alarm history.
  • Gateway event logs.
  • Network captures, where necessary.

An event list alone may not provide enough information to determine the cause of a protection operation.

9. Correlating SOE with Oscillography

Oscillography records electrical waveforms during a disturbance.

It is especially useful for analyzing:

  • Phase-to-earth faults.
  • Phase-to-phase faults.
  • Three-phase faults.
  • Transformer differential operation.
  • CT saturation.
  • Power swings.
  • Breaker failure.
  • Incorrect protection operation.

9.1 Why event records and oscillography are complementary

SOE answers questions such as:

  • When did protection start?
  • When did the trip output operate?
  • When did the breaker open?

Oscillography helps answer:

  • What were the current and voltage waveforms?
  • Which phase was involved?
  • What was the fault current?
  • Was there CT saturation?
  • Did the measured quantities support the protection decision?

9.2 Practical investigation

For a suspected incorrect overcurrent trip:

  1. Retrieve the relay event record.
  2. Identify the protection element that operated.
  3. Retrieve the corresponding disturbance record.
  4. Inspect phase currents and voltages.
  5. Verify the pickup threshold and operating time.
  6. Check CT ratio and polarity.
  7. Compare the measured fault conditions with the protection settings.
  8. Review the breaker operation.
  9. Document the cause and corrective action.

The specific GE Multilin software and file formats depend on the relay family and firmware. Use the appropriate manufacturer-supported tools for the installed device.

10. IEC 61850 Alarm and Event Integration

IEC 61850 provides standardized data models and communication services that can be used to integrate IED events and status information into an SAS.

10.1 Logical nodes

Common logical nodes associated with equipment and protection include:

  • PTOC: time overcurrent protection.
  • PIOC: instantaneous overcurrent protection.
  • PDIF: differential protection.
  • PDIS: distance protection.
  • XCBR: circuit breaker.
  • XSWI: switch or disconnector.
  • CSWI: switch controller.
  • MMXU: measurement.
  • LLN0: logical node zero.
  • LPHD: physical device information.

The actual logical nodes and data objects available depend on the IED implementation.

10.2 Data attributes and quality

An IEC 61850 data object may contain several attributes.

For example, a status value may include:

  • Value.
  • Quality.
  • Timestamp.

The HMI should use the relevant attributes rather than relying only on the numerical or Boolean state.

Quality information can indicate that a value is invalid, questionable, substituted or otherwise affected.

10.3 Reporting

IEC 61850 reporting can be used to deliver changes in configured data to clients.

Important engineering parameters include:

  • Dataset membership.
  • Report Control Block configuration.
  • Buffered or unbuffered reporting.
  • Trigger options.
  • Integrity period.
  • Buffer time.
  • Client association.
  • Report enablement.

Buffered and unbuffered report behavior differs. The design must consider what happens when the client connection is lost and restored.

10.4 GOOSE event information

GOOSE messages can distribute fast event and status information between compatible IEDs.

For example, a protection or interlocking signal may be published by one IED and subscribed to by another.

GOOSE is not simply a replacement for the station HMI event database. The HMI must receive and process the required information through a supported integration method.

The actual GOOSE capabilities must be verified for the installed relay and software versions.

11. Alarm and Event Integration with IEC 60870-5-104

IEC 60870-5-104 is widely used for communication between a substation gateway and a remote control centre.

A gateway may map selected station events to IEC 60870-5-104 information objects.

11.1 Important engineering parameters

Typical parameters include:

  • Common address of ASDU.
  • Information object address.
  • Type identification.
  • Cause of transmission.
  • Time-tagged or non-time-tagged information.
  • Quality descriptors.
  • Spontaneous reporting.
  • General interrogation behavior.
  • Time synchronization.

11.2 Time-tagged information

Depending on the configured type identification and implementation, time-tagged events can be transmitted to the remote control centre.

The engineering team must verify:

  • Whether the source timestamp is preserved.
  • Whether the gateway adds its own timestamp.
  • How invalid time quality is handled.
  • Whether the control centre accepts the selected event format.
  • Whether events are correctly ordered after communication recovery.

11.3 End-to-end verification

A point should be tested through the entire path:

Physical equipment or IED → station communication network → gateway → remote communication channel → control centre.

Testing only the gateway database does not prove that the control centre receives the correct event and timestamp.

12. Alarm and Event Troubleshooting

Problem 1: Alarm appears but the equipment is normal

Possible causes:

  • Incorrect signal polarity.
  • Incorrect alarm mapping.
  • Stale data.
  • Incorrect latching logic.
  • Faulty auxiliary contact.
  • Incorrect reset configuration.

Recommended checks:

  1. Verify the physical signal.
  2. Check the IED indication.
  3. Inspect the communication data reference.
  4. Compare the HMI database with the approved signal list.
  5. Verify latching and reset logic.

Problem 2: Alarm does not appear on the HMI

Possible causes:

  • Incorrect dataset configuration.
  • Report not enabled.
  • Wrong report client configuration.
  • Incorrect alarm database mapping.
  • Communication association failure.
  • HMI filtering or suppression.
  • Invalid quality handling.

Recommended checks:

  1. Confirm that the source IED generates the signal.
  2. Verify the data model.
  3. Check the reporting configuration.
  4. Inspect communication status.
  5. Verify the HMI database and alarm filters.

Problem 3: Duplicate alarms appear

Possible causes:

  • The same signal is mapped from multiple sources.
  • Both relay and gateway generate similar alarm points.
  • Alarm state changes are processed more than once.
  • Communication recovery causes duplicate processing.

Recommended checks:

  • Identify the original source.
  • Review all mappings.
  • Define which system owns the alarm.
  • Check event identifiers and processing rules.

Problem 4: SOE timestamps are inconsistent

Possible causes:

  • IED clocks are not synchronized.
  • Different time zones are configured.
  • The HMI uses reception timestamps.
  • The source event timestamp is missing.
  • Time synchronization has failed.
  • The gateway changes timestamp handling.

Recommended checks:

  • Compare device clocks with the station master clock.
  • Inspect source and reception timestamps.
  • Verify time quality.
  • Review time zone and daylight-saving configuration.
  • Test synchronization failure and recovery.

Problem 5: Events are missing after network recovery

Possible causes:

  • Unbuffered reporting.
  • Incorrect buffered report configuration.
  • Event buffer overflow.
  • Gateway database limitations.
  • Client association recovery problems.
  • Application processing failure.

Recommended checks:

  • Verify the IED’s reporting mode.
  • Inspect report buffer status where available.
  • Check gateway logs.
  • Verify client reconnection behavior.
  • Test the system under controlled communication interruption.

Problem 6: Remote control centre receives an alarm late

Possible causes:

  • Gateway processing delay.
  • Network congestion.
  • Protocol reporting configuration.
  • Remote communication problems.
  • Incorrect event forwarding.
  • Control centre processing delay.

Recommended checks:

  • Compare source timestamp and reception timestamp.
  • Inspect gateway logs.
  • Capture communication traffic.
  • Review protocol reporting behavior.
  • Check network performance.

13. Practical Testing Procedure for Alarm and SOE Systems

A structured test should be performed during FAT and repeated where necessary during SAT.

Step 1: Prepare the test list

Identify:

  • Alarm source.
  • Event source.
  • Expected HMI description.
  • Expected priority.
  • Expected timestamp behavior.
  • Expected clearing behavior.
  • Expected remote SCADA point.

Step 2: Test binary indications

Change each relevant input and verify that the HMI displays the correct state.

Examples include:

  • Breaker open.
  • Breaker closed.
  • Protection healthy.
  • Protection trip.
  • Local control.
  • Remote control.

Step 3: Test alarm generation

Simulate or safely operate the relevant alarm source.

Verify:

  • Alarm activation.
  • Correct description.
  • Correct priority.
  • Correct source.
  • Correct timestamp.

Step 4: Test acknowledgement

Acknowledge the alarm and verify that the alarm remains active if the physical condition has not cleared.

Step 5: Test clearing and reset

Restore the normal condition and verify the configured clearing or reset behavior.

Step 6: Test SOE ordering

Generate multiple events with known timing and verify their order and timestamps.

Step 7: Test time synchronization failure

Where permitted by the test procedure, simulate loss of synchronization and verify the expected alarm and quality behavior.

Step 8: Test communication interruption

Interrupt the relevant communication path under controlled conditions.

Verify:

  • Communication failure alarm.
  • Data quality indication.
  • Recovery behavior.
  • Event buffering or loss behavior.
  • Duplicate event handling.

Step 9: Test remote SCADA integration

Verify that selected alarms and events reach the control centre with the correct addresses, descriptions, quality and timestamps.

Step 10: Document the results

Record:

  • Test reference.
  • Source device.
  • Expected result.
  • Actual result.
  • Pass or fail.
  • Defect reference.
  • Corrective action.
  • Final approval.

14. Alarm and Event Management Design Checklist

Before project handover, verify:

  • Alarm philosophy is approved.
  • Alarm categories are defined.
  • Alarm priorities are assigned.
  • Every alarm has an operational description.
  • Alarm activation and clearing conditions are documented.
  • Latching and reset behavior are defined.
  • Alarm acknowledgement works correctly.
  • Alarm suppression is controlled.
  • Duplicate alarms are reviewed.
  • Event sources are identified.
  • Source timestamps are preserved where required.
  • Time synchronization is verified.
  • Time quality is handled correctly.
  • SOE ordering is tested.
  • Relay events are correlated with disturbance records.
  • IEC 61850 reporting is verified where used.
  • Gateway event mapping is verified.
  • Remote SCADA event reception is tested.
  • Communication recovery behavior is tested.
  • Event storage and retrieval are verified.
  • FAT and SAT records are approved.

15. Recommended Engineering Documents

The following documents should be maintained throughout the project:

  1. Alarm philosophy document.
  2. Alarm list and priority matrix.
  3. IED event list.
  4. SOE signal list.
  5. Time synchronization architecture.
  6. Network architecture.
  7. IEC 61850 dataset and report configuration.
  8. SCADA gateway event mapping.
  9. IEC 60870-5-104 point list, where applicable.
  10. HMI alarm database.
  11. Alarm and SOE FAT procedure.
  12. Alarm and SOE SAT procedure.
  13. Event retention and backup policy.
  14. Troubleshooting and maintenance records.

These documents support operational reliability and future investigation of substation disturbances.

16. Conclusion

Alarm and event management is fundamental to the reliable operation of a GE-based Substation Automation System. A well-designed system must present meaningful alarms, preserve important events, maintain accurate timestamps and provide engineers with the information required to reconstruct a disturbance.

The most important engineering challenge is ensuring consistency between the source IED, station communication network, HMI, gateway and remote control centre.

For protection engineers, SOE should be analyzed together with relay event records, fault records and oscillography. For commissioning engineers, every important alarm and event should be tested from its source to the final operator display.

Accurate alarm management does not simply reduce the number of messages. It helps operators identify the real problem, understand the system response and make appropriate operational decisions.

17. Practical Training by Elec-Engg

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

Our practical training covers power system protection, relay engineering, substation automation, IEC 61850 communication, SCADA integration, testing and commissioning.

Relevant subjects include:

  • GE Multilin protection relay configuration and event analysis.
  • Protection relay event records and disturbance analysis.
  • IEC 61850 MMS reporting and GOOSE communication.
  • IEDScout for IEC 61850 data inspection.
  • Wireshark for Ethernet and protocol troubleshooting.
  • Substation HMI and alarm engineering.
  • SCADA gateway integration.
  • IEC 60870-5-104 and DNP3 communication.
  • Time synchronization and SOE analysis.
  • Protection relay testing and commissioning.

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

Explore our training resources:

Website: https://elec-engg.com/

Contact and training enquiries: https://elec-engg.com/contact/

Frequently Asked Questions

1. What is SOE in a Substation Automation System?

SOE means Sequence of Events. It is a chronological record of events generated by protection relays, bay controllers and other substation devices. It is used to investigate protection operations and equipment behavior.

2. What is the difference between an alarm and an event?

An alarm indicates an abnormal condition that may require operator attention. An event records that something happened at a particular time. An alarm can also generate an event record.

3. Why is time synchronization important in GE SAS?

Time synchronization ensures that events from different IEDs can be compared in a meaningful chronological sequence. Incorrect clock synchronization can lead to misleading fault analysis.

4. Which time synchronization protocols are used in substations?

Common methods include SNTP, NTP, PTP and IRIG-B. The appropriate method depends on equipment capabilities and project timing requirements.

5. What is alarm flooding?

Alarm flooding occurs when a large number of alarms appear within a short period, often during a major disturbance. Alarm rationalization, appropriate priorities and careful signal design help reduce unnecessary messages.

6. Does alarm acknowledgement clear an alarm?

No. Acknowledgement confirms that the operator has recognized the alarm. The alarm may remain active until the underlying condition has been cleared.

7. What is the difference between buffered and unbuffered reporting in IEC 61850?

Buffered reporting can retain configured event information during a client communication interruption, within the limits of the device’s buffer and implementation. Unbuffered reporting does not provide the same event retention behavior during disconnection.

8. Can IEC 61850 events be forwarded to a remote control centre?

Yes. A station-level gateway can map selected information to a remote protocol such as IEC 60870-5-104 or DNP3. The gateway must be configured to preserve the required data, quality and timestamp information.

9. Why should SOE be correlated with oscillography?

SOE identifies the sequence and timing of protection and control events, while oscillography provides the electrical waveforms. Together they provide a much stronger basis for fault investigation.

10. Why are duplicate alarms generated?

Duplicate alarms can result from multiple mappings of the same signal, overlapping alarm sources or incorrect processing after communication recovery. The engineering team should identify the original source and define a consistent alarm ownership strategy.

11. How can engineers verify alarm and event performance?

Through controlled FAT and SAT procedures that test alarm activation, acknowledgement, clearing, timestamps, event ordering, communication interruption, recovery and remote SCADA integration.

12. Does every GE Multilin relay support the same event and disturbance recording functions?

No. Event capacity, disturbance recording, timestamp resolution, communication services and configuration options vary by model, hardware and firmware. The applicable device documentation must be checked.

Leave a Comment

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

Scroll to Top