- Introduction
- 1. Understanding Bay Control in a Substation Automation System
- 2. Bay Control Architecture: Who Performs What?
- 3. Control Authority and Operating Modes
- 4. Circuit Breaker Control Engineering
- 5. Disconnector and Earthing Switch Control
- 6. Interlocking Principles in GE SAS
- 7. IEC 61850 Logical Nodes for Bay Control
- 8. GOOSE-Based Interlocking
- 9. Select-Before-Operate and Direct Control
- 10. Practical Feeder Bay Example
- 11. HMI Engineering for Bay Control
- 12. FAT and SAT Testing of Bay Control
- 13. Common Bay Control Problems and Troubleshooting
- 14. Documentation Required for Bay Control Engineering
- 15. Bay Control Commissioning Checklist
- 16. Safety Considerations
- 17. Frequently Asked Questions
- What is bay control in a GE SAS?
- What is the difference between a bay controller and a protection relay?
- What is the purpose of CILO in IEC 61850?
- Can GOOSE be used for interlocking?
- What is the difference between SBO and direct operate?
- Why is breaker position feedback important?
- Can software interlocking replace mechanical interlocking?
- Which software is used for GE SAS bay control engineering?
- 18. Practical Training by Elec-Engg
Introduction
Bay control is one of the most important functions of a Substation Automation System (SAS). It provides the operational interface between protection and control IEDs, circuit breakers, disconnectors, earthing switches, station HMI systems and remote SCADA control centres.
In a GE-based substation automation project, bay control engineering must ensure that switching commands are executed only when the required operating conditions are satisfied. It must also provide reliable position feedback, control authority management, event recording and communication between bay-level equipment and the station-level automation system.
A properly engineered bay control system helps prevent incorrect switching operations, supports safe maintenance activities and improves operational visibility.
This article explains the practical engineering principles behind bay control and interlocking in GE SAS projects, including IEC 61850 integration, switching sequences, testing and troubleshooting.
Important: GE SAS installations can use different combinations of GE Multilin protection relays, bay controllers, gateways, HMI platforms and third-party IEDs. Exact control capabilities, logical nodes, configuration tools and operating procedures depend on the installed device, firmware, project architecture and approved manufacturer documentation.
1. Understanding Bay Control in a Substation Automation System
A bay is a functional part of a substation associated with a particular circuit or equipment arrangement. Examples include:
- Transformer bay
- Transmission line bay
- Bus coupler bay
- Bus section bay
- Feeder bay
- Reactor or capacitor bank bay
- Generator bay
Bay control is responsible for monitoring and operating the switching equipment assigned to that bay.
Typical controlled equipment includes:
- Circuit breakers
- Disconnectors and isolators
- Earthing switches
- Motor-operated switches
- Other auxiliary switching devices
The bay control function generally performs several tasks:
- Receives switching commands from authorized control locations.
- Checks the control authority and operating mode.
- Evaluates applicable interlocking conditions.
- Issues an operation command to the relevant device.
- Monitors the equipment response.
- Updates equipment status and alarms.
- Reports events and indications to the station HMI and SCADA gateway.
The exact distribution of these functions varies between projects. In some installations, the bay controller performs most of the control logic. In others, protection relays, dedicated control IEDs or distributed automation devices provide part of the functionality.
2. Bay Control Architecture: Who Performs What?
A common source of engineering errors is misunderstanding the responsibilities of different SAS components.
2.1 Bay controller
The bay controller coordinates control and monitoring functions for the bay.
Depending on the installed equipment, it may provide:
- Circuit breaker control
- Disconnector and earthing switch control
- Interlocking logic
- Local and remote control selection
- Position monitoring
- Alarm generation
- Measurement acquisition
- IEC 61850 communication
A bay controller may be a dedicated device or a multifunctional protection and control IED.
2.2 Protection relay
The protection relay primarily detects abnormal power system conditions and initiates protection actions.
Typical functions include:
- Overcurrent protection
- Earth-fault protection
- Distance protection
- Differential protection
- Breaker failure protection
- Auto-reclosing
- Trip circuit supervision
A protection relay may also provide breaker control and interlocking functions, but these capabilities must be confirmed for the specific device and application.
Protection trip logic and operator switching logic should be engineered as distinct functions, even when they share the same physical IED.
2.3 Station HMI
The station HMI provides the operator interface for monitoring and controlling the substation.
It typically displays:
- Single-line diagrams
- Breaker and disconnector positions
- Measurements
- Alarms
- Events
- Control authority
- Communication status
The HMI sends commands to the appropriate bay-level control device. It should not be assumed that displaying a switching device on the HMI means that the HMI itself performs the interlocking.
2.4 SCADA gateway
The gateway provides communication between the SAS and remote control centres.
Typical functions include:
- IEC 60870-5-104 communication
- DNP3 communication
- IEC 61850 MMS client functions
- Point mapping
- Remote control forwarding
- Event and alarm transmission
The gateway must preserve control authorization, command status and equipment feedback according to the approved project design.
3. Control Authority and Operating Modes
A switching device should not accept commands indiscriminately from every control location.
A typical control hierarchy may include:
- Local control at the equipment or mechanism
- Bay-level control
- Station-level HMI control
- Remote control centre operation
The actual hierarchy is project-specific.
3.1 Local control
Local control is normally selected at the switchgear or equipment mechanism.
Depending on the design, local operation may bypass some remote command paths while retaining essential electrical and mechanical safety interlocks.
Local control does not mean that all interlocks can be ignored.
3.2 Bay-level control
Bay-level control is normally performed from a bay control panel or an associated local interface.
It allows an operator or commissioning engineer to operate equipment within the bay, subject to the configured authority and interlocking conditions.
3.3 Station-level control
Station-level control is performed from the station HMI.
The operator selects equipment on the single-line diagram and issues an open or close command.
The command must be transferred to the appropriate bay-level control function and accepted only if the required conditions are satisfied.
3.4 Remote control
Remote control originates from a control centre.
It is normally transmitted through a SCADA gateway using a protocol such as IEC 60870-5-104 or DNP3.
Remote commands should be subject to:
- Remote control authorization
- Correct control mode
- Communication availability
- Interlocking conditions
- Equipment availability
- Command timeout and response supervision
3.5 Control authority engineering
The engineering team should define:
- Which control locations are permitted
- How authority is selected
- Whether authority is transferred automatically or manually
- How conflicting commands are handled
- What happens after communication failure
- How local operation affects remote control
- How authority status is indicated to the operator
The control authority design must be consistent across the HMI, bay IEDs and gateway.
4. Circuit Breaker Control Engineering
Circuit breaker control is a central function of bay automation.
A typical circuit breaker has:
- Closing coil
- Trip coil or coils
- Spring-charging mechanism
- Auxiliary contacts
- Mechanism supervision
- Local/remote selector
- Anti-pumping functionality
- Trip circuit supervision
The SAS must correctly integrate the electrical control circuits with the IED logic and HMI indications.
4.1 Circuit breaker position feedback
Two commonly used auxiliary contacts are:
- 52a: generally closed when the circuit breaker is closed.
- 52b: generally closed when the circuit breaker is open.
The exact wiring and contact behavior must be confirmed against the breaker manufacturer’s documentation.
A typical interpretation is:
| 52a | 52b | Interpreted condition |
|---|---|---|
| 1 | 0 | Breaker closed |
| 0 | 1 | Breaker open |
| 0 | 0 | Intermediate, invalid or discrepant state |
| 1 | 1 | Contradictory or faulty indication |
The SAS should not automatically interpret every contradictory combination as a normal open or closed state.
A suitable alarm should be generated when the feedback is inconsistent or remains in an intermediate state beyond the configured time.
4.2 Breaker closing command
A typical closing sequence is:
- The operator selects the circuit breaker.
- The control system checks the active control authority.
- The system checks the configured interlocking conditions.
- The command is issued to the closing output.
- The breaker mechanism receives the closing signal.
- The breaker closes.
- Auxiliary contacts change state.
- The bay controller confirms the new position.
- The HMI and SCADA system update the indication.
- The operation is recorded as an event.
The command being accepted does not necessarily mean that the breaker has physically closed.
The control system must distinguish between command acceptance and successful equipment operation.
4.3 Breaker opening command
A normal operator opening sequence typically involves:
- Operator selection.
- Control authority verification.
- Command validation.
- Opening output activation.
- Breaker mechanism operation.
- Position feedback change.
- HMI and gateway status update.
- Event recording.
Protection trips are different from normal operator switching commands.
A protection trip must follow the approved protection design and should not be blocked by ordinary operator closing interlocks.
4.4 Trip circuit supervision
Trip circuit supervision monitors the availability and integrity of the breaker trip circuit.
Depending on the design, it can detect:
- Loss of DC supply
- Open trip circuit wiring
- Blown fuse
- Trip coil circuit interruption
- Auxiliary contact problems
Trip circuit supervision is important because a breaker may appear healthy in the SAS while its trip circuit is unavailable.
5. Disconnector and Earthing Switch Control
Disconnectors and earthing switches are particularly important for safe isolation and maintenance.
Their operation must follow the substation’s approved switching philosophy.
5.1 Disconnector operation
A disconnector is generally intended to establish an isolation gap under the operating conditions for which it is rated.
It is not normally used to interrupt load current unless specifically designed and rated for that duty.
A typical disconnector control scheme may check:
- Circuit breaker position
- Relevant busbar conditions
- Associated disconnector positions
- Earthing switch position
- Local/remote authority
- Mechanism availability
- Applicable interlocking signals
5.2 Earthing switch operation
An earthing switch connects an isolated part of the installation to earth.
Before operation, the control system may require confirmation that the associated circuit is isolated and that the required safe conditions are met.
Depending on the switchgear and utility philosophy, additional checks may include:
- Associated circuit breaker open
- Relevant disconnectors open
- No conflicting switching state
- Voltage absence established through the approved procedure
- Permit-to-work and safety conditions satisfied
The SAS should not replace approved voltage-testing procedures, isolation practices or safety permits.
5.3 Mechanical and electrical interlocking
Mechanical interlocking is implemented through the equipment mechanism or associated mechanical devices.
Electrical interlocking is implemented through electrical circuits, control relays, IED logic or automation functions.
Both may be required.
A software interlock should not be treated as a substitute for mechanical or electrical safety arrangements unless the complete design has been formally assessed and approved for that application.
6. Interlocking Principles in GE SAS
Interlocking prevents switching operations that would create an unsafe or prohibited equipment configuration.
It is usually based on the status of other switching devices and predefined operational conditions.
6.1 Basic interlocking example
Consider a feeder bay containing:
- Circuit breaker CB1
- Line disconnector DS1
- Busbar disconnector DS2
- Earthing switch ES1
An example of a simplified switching philosophy may be:
Closing the circuit breaker:
- Required disconnectors are confirmed in their permitted operating positions.
- Earthing switch is confirmed open.
- Control authority is valid.
- No applicable blocking condition is active.
- The breaker is available for operation.
Closing the earthing switch:
- The associated circuit breaker is open.
- Required disconnectors are open.
- Other applicable isolation conditions are satisfied.
- The approved safety procedure permits earthing.
These are illustrative conditions only. The actual logic must be derived from the approved single-line diagram, switchgear arrangement, utility switching rules and equipment manufacturer’s requirements.
6.2 Interlocking matrix
An interlocking matrix documents the conditions required for each operation.
A simplified example is shown below.
| Command | Example permissive conditions |
|---|---|
| Close CB1 | Required disconnectors in permitted positions; ES1 open; authority valid |
| Open CB1 | Valid control authority; breaker available for normal operation |
| Close DS1 | CB1 open; applicable bus and line conditions satisfied |
| Close DS2 | CB1 open; applicable busbar arrangement satisfied |
| Close ES1 | CB1 open; required disconnectors open; safety conditions satisfied |
The matrix must be expanded to cover all relevant switching configurations, including bus coupler and bus section arrangements where applicable.
6.3 Permissive and blocking signals
A permissive signal indicates that a required condition has been satisfied.
A blocking signal indicates that an operation must not proceed.
For example:
CB_OPEN: breaker is confirmed open.DS1_OPEN: disconnector is confirmed open.ES1_OPEN: earthing switch is confirmed open.INTERLOCK_OK: all required conditions are satisfied.CLOSE_BLOCK: breaker closing is inhibited.
Signal names are illustrative and should be replaced with project-specific naming conventions.
6.4 Fail-safe design
Interlocking must be designed to respond safely to uncertain conditions.
Examples include:
- Loss of communication
- Invalid position indication
- IED restart
- Failed auxiliary supply
- Contradictory auxiliary contacts
- Stale status information
- Internal IED diagnostic alarm
For safety-critical operations, an unknown or invalid condition should not be interpreted as a confirmed safe condition.
The response must be defined in the approved design and validated during testing.
7. IEC 61850 Logical Nodes for Bay Control
IEC 61850 provides standardized data models that can support control and monitoring functions.
Common logical nodes relevant to switching equipment include:
| Logical node | Typical purpose |
|---|---|
| CSWI | Switch controller |
| XCBR | Circuit breaker |
| XSWI | Switch or disconnector |
| CILO | Interlocking function |
| GGIO | Generic process I/O |
| LLN0 | Logical device and common functions |
| LPHD | Physical device information |
The actual availability and implementation of these logical nodes depend on the IED and its IEC 61850 conformance.
7.1 CSWI – Switch controller
CSWI is commonly associated with the control of switching devices.
It may represent control-related information such as:
- Control requests
- Operating mode
- Command status
- Position-related control information
- Interlocking-related status
The precise data objects and supported services depend on the device implementation.
7.2 XCBR – Circuit breaker
XCBR represents circuit breaker information.
Typical engineering interests include:
- Position
- Operating status
- Device health
- Associated measurements or counters where supported
7.3 XSWI – Disconnector and switch
XSWI is commonly used for switchgear devices such as disconnectors and earthing switches.
The engineering team must correctly distinguish between different physical switching devices, even when similar logical node classes are used.
7.4 CILO – Interlocking
CILO is associated with interlocking information.
It can be used to represent whether an operation is permitted or blocked, according to the implemented data model.
The engineering team must verify how the actual IED implements interlocking and whether the control function evaluates the interlocking locally or receives it through communication.
7.5 IEC 61850 control models
IEC 61850 supports different control models, depending on the device implementation.
Common models include:
- Direct control
- Select-before-operate (SBO)
- Enhanced security control procedures where supported
The selected control model must be consistent with the client, server and project requirements.
An HMI or gateway should not assume that every IED supports every control model.
8. GOOSE-Based Interlocking
GOOSE communication can be used to exchange fast interlocking signals between IEDs.
For example, a bus coupler IED may publish a status signal that is consumed by a feeder bay IED.
A simplified engineering process is:
- Identify the interlocking signal.
- Determine the publisher IED.
- Determine the subscriber IED.
- Define the required dataset.
- Configure the GOOSE control block.
- Configure the subscriber mapping.
- Verify communication parameters.
- Test the received signal.
- Test the interlocking response.
- Verify behavior during communication failure.
8.1 GOOSE engineering considerations
The engineering team should check:
- Dataset contents
- GOOSE control block
- Application identifier
- VLAN configuration
- Priority tagging
- Multicast addressing
- Network path
- Subscriber mapping
- Communication supervision
- Time and state-related parameters
The GOOSE configuration must be validated against the actual IED capabilities and project SCL files.
8.2 Communication failure response
A GOOSE-based interlocking design must define how the receiving IED responds when communication is lost or the received information becomes invalid.
The receiver should not treat an expired or invalid signal as a permanently valid permissive.
The required fail-safe behavior must be documented and tested.
9. Select-Before-Operate and Direct Control
The control model affects how an operator command is processed.
9.1 Select-before-operate
In an SBO arrangement, the operator first selects the device and then issues the operation.
A simplified sequence is:
- Select the switching device.
- The IED validates the selection.
- The control system returns the selection response.
- The operator confirms the intended operation.
- The operate command is sent.
- The IED checks the command and applicable conditions.
- The command is executed or rejected.
- The final status is monitored.
SBO can help reduce accidental operations, but it does not replace interlocking or control authority checks.
9.2 Direct operate
In direct operate, the control command is issued without the separate selection stage.
This model must be used only where permitted by the project control philosophy and supported by the IED.
9.3 Command response monitoring
The HMI should distinguish between:
- Command initiated
- Command selected
- Command accepted
- Command rejected
- Command completed
- Operation failed
- Feedback timeout
A command acknowledgement must not be displayed as proof of successful physical operation.
10. Practical Feeder Bay Example
Consider a feeder bay with:
- CB1: circuit breaker
- DS1: line disconnector
- DS2: busbar disconnector
- ES1: line earthing switch
Assume the approved operating philosophy requires the circuit breaker to be open before the relevant disconnectors can be operated.
10.1 Closing the feeder breaker
A simplified control process could be:
- Confirm the selected control location has authority.
- Confirm CB1 is in the open position.
- Confirm DS1 and DS2 are in their required positions.
- Confirm ES1 is open.
- Confirm no applicable interlocking or equipment block is active.
- Issue the close command.
- Monitor the closing output and breaker response.
- Confirm 52a and 52b feedback.
- Update the HMI and SCADA status.
- Record the event.
10.2 Isolating the feeder
An illustrative sequence could be:
- Open CB1 using the approved switching order.
- Confirm CB1 open through reliable position feedback.
- Operate the required disconnectors according to the switching procedure.
- Confirm the required isolation state.
- Establish absence of voltage using the approved safety procedure.
- Close ES1 only when all required conditions are satisfied.
- Verify ES1 position.
- Apply the required safety locks and permit-to-work arrangements.
The sequence must never be used as a substitute for an approved switching order.
10.3 Example logic
The following is conceptual pseudocode, not executable GE relay logic:
CB_CLOSE_PERMISSIVE =
CONTROL_AUTHORITY_VALID
AND DS1_IN_REQUIRED_POSITION
AND DS2_IN_REQUIRED_POSITION
AND ES1_OPEN
AND BREAKER_AVAILABLE
AND NO_CLOSE_BLOCK
IF CB_CLOSE_COMMAND AND CB_CLOSE_PERMISSIVE:
ISSUE_CLOSE_OUTPUT
ELSE:
REJECT_COMMAND
DISPLAY_BLOCKING_REASON
For an earthing switch:
ES1_CLOSE_PERMISSIVE =
CB1_CONFIRMED_OPEN
AND DS1_CONFIRMED_OPEN
AND REQUIRED_ISOLATION_CONFIRMED
AND NO_CONFLICTING_INTERLOCK
AND CONTROL_AUTHORITY_VALID
Actual logic must include appropriate signal quality, timeout, equipment-specific conditions and the utility’s approved interlocking philosophy.
11. HMI Engineering for Bay Control
The HMI must clearly communicate the status of switching equipment.
11.1 Single-line diagram representation
A typical bay single-line diagram should display:
- Circuit breaker position
- Disconnector positions
- Earthing switch positions
- Voltage and current measurements
- Control authority
- Equipment alarms
- Communication quality
The display should differentiate between open, closed, intermediate and invalid states.
Color conventions must follow the project’s approved HMI design standard.
11.2 Command interface
The operator interface should provide:
- Clear equipment identification
- Open and close commands
- Selection and confirmation where required
- Command status
- Interlocking status
- Blocking reason
- Final position feedback
Commands should not be enabled merely because the operator can see the equipment symbol.
11.3 Interlocking indication
A useful HMI design provides meaningful information about why an operation is blocked.
For example:
- Earthing switch is not open.
- Breaker position is invalid.
- Remote authority is not selected.
- Required disconnector position is not confirmed.
- Interlocking signal is unavailable.
A clear blocking message reduces operator confusion and commissioning time.
12. FAT and SAT Testing of Bay Control
Bay control testing should be performed systematically before the system is placed into service.
12.1 Factory Acceptance Test
The FAT should include:
Control authority
- Test local control.
- Test bay-level control.
- Test station-level control.
- Test remote control.
- Verify conflicting command handling.
Circuit breaker
- Test close command.
- Test open command.
- Verify 52a and 52b feedback.
- Test intermediate position indication.
- Verify command timeout.
- Test trip circuit supervision indications where applicable.
Disconnector and earthing switch
- Test permitted operations.
- Test prohibited operations.
- Verify mechanical and electrical interlocking interfaces.
- Confirm correct position feedback.
Interlocking
- Test every required permissive.
- Test every blocking condition.
- Simulate invalid status.
- Simulate communication failure where relevant.
- Verify fail-safe behavior.
IEC 61850
- Verify control data models.
- Test MMS reporting.
- Test control procedures.
- Test GOOSE publisher and subscriber functions where used.
- Verify quality and communication supervision.
12.2 Site Acceptance Test
The SAT should verify the installed system, including:
- Wiring and terminal checks
- Auxiliary DC supply
- Actual equipment feedback
- Control circuit operation
- IED-to-HMI communication
- Gateway integration
- GOOSE communication
- Time synchronization
- Alarm and event reporting
- End-to-end remote control
Live switching tests must only be carried out under approved operational procedures, with the necessary permits, isolations, clearances and responsible personnel.
13. Common Bay Control Problems and Troubleshooting
Problem 1: Breaker close command is rejected
Possible causes:
- Incorrect control authority
- Active closing interlock
- Earthing switch not confirmed open
- Disconnector position incorrect
- Invalid breaker status
- Equipment not ready
- Control communication failure
Recommended checks:
- Review the HMI blocking message.
- Check the bay IED control mode.
- Verify all required position feedback.
- Check interlocking inputs.
- Review IED event records.
- Confirm communication and signal quality.
Problem 2: Breaker closes physically, but HMI shows open
Possible causes:
- Incorrect 52a/52b wiring
- Incorrect input mapping
- Wrong IEC 61850 data mapping
- Stale report information
- HMI tag configuration error
- Incorrect status inversion
Recommended checks:
- Inspect the physical auxiliary contacts.
- Verify binary input status at the IED.
- Check the logical node data.
- Inspect MMS reports or gateway mapping.
- Verify HMI tag and display logic.
Problem 3: Disconnector operation is blocked
Possible causes:
- Breaker not confirmed open
- Incorrect busbar configuration
- Earthing switch status incorrect
- Interlocking signal missing
- Local/remote selector in the wrong position
Recommended checks:
- Review the approved interlocking matrix.
- Check all relevant switching device statuses.
- Verify the source of each permissive.
- Check GOOSE or hardwired interlocking signals where applicable.
Problem 4: Interlocking does not release
Possible causes:
- Stale signal
- Incorrect GOOSE subscription
- Wrong signal polarity
- Incorrect logical mapping
- Failed auxiliary contact
- Invalid quality attribute
- Logic configuration error
Recommended checks:
- Identify the interlocking input.
- Trace the signal from source to destination.
- Check the physical or IEC 61850 source.
- Inspect quality and communication status.
- Verify the logic equation.
- Test the complete signal path under an approved test condition.
Problem 5: Remote control is unavailable
Possible causes:
- Local mode selected
- Remote authority not enabled
- Gateway communication failure
- Incorrect control mapping
- Command security restrictions
- IED control model mismatch
Recommended checks:
- Check the control authority indication.
- Verify gateway communication.
- Inspect the command path.
- Check the IED control model.
- Review event and diagnostic logs.
14. Documentation Required for Bay Control Engineering
A complete engineering package should include:
- Approved single-line diagrams
- Bay control architecture
- Control philosophy
- Switching sequence documents
- Interlocking matrix
- AC and DC schematics
- Circuit breaker control drawings
- Disconnector and earthing switch wiring
- IED signal list
- IEC 61850 data model documentation
- SCL configuration files
- GOOSE signal list
- HMI graphics and tag database
- Gateway point list
- FAT and SAT procedures
- As-built drawings
- Configuration backup and revision history
The documentation must remain consistent with the final installed configuration.
15. Bay Control Commissioning Checklist
Before commissioning, verify the following:
- Correct bay architecture and IED allocation
- Correct circuit breaker and switchgear identification
- Correct auxiliary contact wiring
- Correct 52a/52b interpretation
- Correct control authority selection
- Correct local and remote operating modes
- Correct open and close command mapping
- Correct interlocking matrix implementation
- Correct permissive and blocking signals
- Correct invalid-status handling
- Correct IEC 61850 data mapping
- Correct GOOSE configuration, if applicable
- Correct HMI status and alarm indication
- Correct SCADA gateway point mapping
- Correct time synchronization
- Successful FAT and SAT documentation
- Approved switching and safety procedures available
- Final configuration backed up
16. Safety Considerations
Bay control engineering directly affects the safe operation of high-voltage equipment.
The following principles are essential:
- Never bypass an interlock simply to complete a test or switching operation.
- Do not assume that an HMI indication proves physical isolation.
- Verify equipment position using the approved procedures and reliable indications.
- Follow the approved switching order.
- Apply isolation, lockout/tagout and permit-to-work requirements.
- Confirm absence of voltage using approved equipment and procedures.
- Use qualified personnel for control circuit and switchgear testing.
- Document temporary test links and remove them before returning equipment to service.
- Ensure that protection trip paths remain correctly engineered and available.
- Obtain the required operational authorization before any live switching test.
17. Frequently Asked Questions
What is bay control in a GE SAS?
Bay control is the set of monitoring, switching, control authority and interlocking functions associated with a substation bay. It connects the switching equipment with the bay-level IEDs, station HMI and remote SCADA system.
What is the difference between a bay controller and a protection relay?
A bay controller primarily manages equipment control and monitoring. A protection relay detects faults and initiates protection actions. Some devices combine both functions, but their responsibilities should remain clearly defined in the engineering design.
What is the purpose of CILO in IEC 61850?
CILO is a logical node associated with interlocking information. Its actual behavior and available data objects depend on the IED implementation and the engineering configuration.
Can GOOSE be used for interlocking?
Yes. GOOSE can exchange fast interlocking signals between compatible IEDs. The design must include correct publisher/subscriber configuration, communication supervision and a defined response to communication failure.
What is the difference between SBO and direct operate?
Select-before-operate requires a selection stage before the operation command. Direct operate sends the operation command without that separate selection stage. The supported control model depends on the IED and project requirements.
Why is breaker position feedback important?
Breaker position feedback confirms whether the physical equipment has reached the requested position. Command acceptance alone does not prove that the breaker has opened or closed.
Can software interlocking replace mechanical interlocking?
Not automatically. The complete protection and control design must consider equipment-specific requirements, risk, applicable standards and the utility’s approved safety philosophy.
Which software is used for GE SAS bay control engineering?
The software depends on the installed GE equipment and system architecture. Applicable GE EnerVista tools may be used for supported GE Multilin IEDs, while IEC 61850 engineering tools, system configuration applications and HMI engineering environments may be required for the wider SAS. Always confirm compatibility with the exact device and firmware.
18. Practical Training by Elec-Engg
Understanding bay control requires more than knowing the meaning of IEC 61850 logical nodes or drawing an interlocking matrix. Engineers must understand the complete signal path from the operator command to the physical switching device and back to the HMI and SCADA system.
Elec-Engg provides practical technical training by Dr Saeed Roostaee (Electrical Engineering).
Relevant training subjects include:
- Power system protection and control
- Substation Automation Systems (SAS)
- GE protection relays and applicable engineering software
- IEC 61850 engineering and configuration
- MMS reporting and GOOSE communication
- Bay control and interlocking engineering
- SCADA gateway integration
- HMI engineering and operational troubleshooting
- Relay testing and commissioning
Training is available through:
- Pre-recorded video courses
- Structured self-paced training
- Live online training
- Face-to-face training
- Customized in-house training for utilities and industrial organizations
The practical approach focuses on real engineering tasks, configuration workflows, communication testing, troubleshooting and commissioning.
Explore technical training at:
For customized training and technical support:
GE SAS, GE Substation Automation, Bay Control, Interlocking, IEC 61850, GOOSE, Circuit Breaker Control, Disconnector Control, Earthing Switch, CSWI, XCBR, XSWI, CILO, Substation Commissioning, SCADA Engineering
