- Introduction
- 1. What Is Process Bus Engineering?
- 2. Process Bus Versus Conventional Secondary Wiring
- 3. Main Components of a Process Bus System
- 4. Understanding the Process Bus Communication Architecture
- 5. Sampled Values Publisher and Subscriber Configuration
- 6. Engineering Sampled Values Using SCL
- 7. External References and Sampled Values Subscription
- 8. GOOSE Communication in the Process Bus
- 9. Process Bus Network Design
- 10. Time Synchronization and Sample Alignment
- 11. Process Bus Applications in Protection Systems
- 12. Practical Example: Integrating a Merging Unit with a Feeder Protection System
- 13. Process Bus Testing with Omicron Test Equipment
- 14. Wireshark Analysis for Process Bus Communication
- 15. Loss of Sampled Values and Protection Response
- 16. Common Process Bus Problems and Troubleshooting
- 17. Cybersecurity Considerations
- 18. Process Bus Commissioning Checklist
- 19. Conclusion
- Practical IEC 61850 and MiCOM Training by Dr Saeed Roostaee – Elec-Engg
Introduction
The process bus is one of the most important components of a digital substation. It provides the communication infrastructure through which protection and control IEDs exchange information with primary-process equipment.
In a conventional substation, protection relays receive current and voltage signals through dedicated CT and VT secondary circuits. Binary signals, such as circuit-breaker status and interlocking signals, are also commonly transmitted through hardwired connections.
In a digital substation, some of these functions can be implemented through Ethernet communication.
Merging Units convert analogue current and voltage signals into digital Sampled Values (SV), while GOOSE communication can distribute status, interlocking and protection signals between compatible IEDs.
For engineers working with MiCOM protection systems, understanding process bus engineering is essential when integrating protection relays into modern IEC 61850 substations.
One important distinction must be made from the beginning: not every MiCOM relay that supports IEC 61850 MMS or GOOSE also supports Sampled Values reception. The exact relay model, hardware, firmware and supported communication services must be verified before designing a process bus application.
1. What Is Process Bus Engineering?
Process bus engineering involves designing, configuring, integrating and testing the communication interface between primary-process equipment and protection and control systems.
Its main objective is to replace or reduce selected conventional secondary wiring with standardized digital communication.
A typical process bus system includes:
- Current transformers.
- Voltage transformers.
- Merging Units.
- Protection relays.
- Bay control units.
- Ethernet switches.
- Time synchronization equipment.
- Engineering workstations.
- Station-level communication systems.
The process bus can carry different types of information, including:
| Information | Typical communication |
|---|---|
| Current measurements | Sampled Values |
| Voltage measurements | Sampled Values |
| Circuit-breaker status | GOOSE or hardwired signals |
| Protection interlocking | GOOSE or hardwired signals |
| Trip signals | GOOSE or hardwired signals |
| SCADA measurements | MMS |
| Alarms and events | MMS reporting |
The communication method selected for each signal depends on the protection philosophy, equipment capabilities and project requirements.
2. Process Bus Versus Conventional Secondary Wiring
A conventional protection system uses dedicated copper connections between instrument transformers and protection relays.
For example, a feeder protection relay may receive:
- Three phase currents.
- Residual current.
- Three phase voltages.
- Circuit-breaker position.
- Disconnector position.
- Trip circuit status.
In a process bus architecture, some of these signals can be transmitted digitally.
Conventional architecture
Digital process bus architecture
Main differences
| Feature | Conventional system | Process bus system |
|---|---|---|
| CT/VT interface | Direct secondary wiring | Merging Unit |
| Measurement transmission | Analogue electrical signals | Digital Sampled Values |
| Binary signals | Hardwired contacts | GOOSE or hardwired |
| Signal distribution | Dedicated copper circuits | Ethernet communication |
| Engineering | Wiring and terminal drawings | SCL and network configuration |
| Testing | Secondary injection and wiring checks | Process bus testing and digital validation |
| Fault investigation | Electrical measurements and wiring checks | Device diagnostics and network analysis |
A process bus does not eliminate all copper wiring. Instrument transformer connections to the Merging Unit, power supplies, some trip circuits and other interfaces may remain hardwired.
3. Main Components of a Process Bus System
3.1 Instrument Transformers
Current transformers and voltage transformers provide the electrical measurements required by the protection system.
Their signals are connected to the Merging Unit or another approved digital instrument transformer interface.
Engineers must verify:
- CT ratio.
- VT ratio.
- Accuracy class.
- Polarity.
- Phase identification.
- Secondary earthing.
- Burden and wiring requirements.
- Instrument transformer performance.
Incorrect CT or VT configuration can cause incorrect protection measurements even when the Ethernet communication is operating correctly.
3.2 Merging Unit
The Merging Unit converts analogue measurements into digital sampled data.
Its main functions may include:
- Analogue input acquisition.
- Sampling.
- Analogue-to-digital conversion.
- SV publication.
- Time synchronization.
- Measurement quality supervision.
- Communication diagnostics.
The Merging Unit configuration must match the receiving protection IED’s supported SV profile.
3.3 Protection Relay
The protection relay processes measurement information and performs protection functions.
In a digital process bus application, the relay must have the required Sampled Values receiving capability.
Some MiCOM devices may support IEC 61850 MMS and GOOSE without supporting SV reception. These capabilities must be assessed separately.
3.4 Ethernet Switches
Ethernet switches connect Merging Units, protection relays and other process bus devices.
They must be suitable for the communication requirements of the project.
Important characteristics include:
- Managed Ethernet functionality.
- VLAN support.
- Multicast forwarding.
- Traffic prioritization.
- Suitable bandwidth.
- Redundancy support, where required.
- Network diagnostics.
- Industrial environmental suitability.
3.5 Time Synchronization Equipment
The time synchronization system provides a common time reference for devices that require coordinated sampling.
PTP is commonly used in digital substation process bus designs.
The synchronization profile and performance must be compatible with the Merging Units and receiving IEDs.
4. Understanding the Process Bus Communication Architecture
A typical digital feeder protection architecture may contain one Merging Unit publishing current and voltage samples to one or more compatible protection IEDs.
The communication path is:
- CTs and VTs produce secondary analogue signals.
- The Merging Unit receives the signals.
- The Merging Unit samples and digitizes them.
- The Merging Unit publishes Sampled Values.
- The process bus distributes the Ethernet frames.
- Compatible protection IEDs receive the SV streams.
- Protection functions process the measurements.
- Trip and interlocking signals are exchanged through GOOSE or other approved interfaces.
The architecture must also consider what happens when communication is interrupted.
For example, the protection system may need to detect loss of SV, issue an alarm, block selected functions or transfer to an alternative measurement source, depending on the approved protection design.
5. Sampled Values Publisher and Subscriber Configuration
The Merging Unit normally acts as the publisher of the SV stream.
A compatible protection relay acts as the subscriber.
The configuration must ensure that the receiving relay subscribes to the correct data stream.
Important parameters
| Parameter | Description |
|---|---|
| IED name | Unique identifier of the device |
| svID | Identifier of the Sampled Values stream |
| APPID | Application identifier |
| Dataset | Set of sampled measurement values |
| confRev | Configuration revision of the SV control block |
| Multicast MAC | Destination Ethernet multicast address |
| VLAN ID | Logical network identification |
| VLAN priority | Traffic priority |
| Sampling profile | Required sampling characteristics |
These parameters must match the device implementation and system configuration.
Example configuration
The following values are illustrative only:
| Parameter | Example |
|---|---|
| Publisher | MU_FEEDER01 |
| Subscriber | PROT_FEEDER01 |
| svID | MU_FEEDER01_SV |
| APPID | 4001 |
| VLAN ID | 100 |
| VLAN priority | 4 |
| Sampling profile | 80 samples per 50 Hz cycle |
Do not copy these values directly into a live project. Use the approved engineering design and device documentation.
6. Engineering Sampled Values Using SCL
SCL is the standardized XML-based configuration language used in IEC 61850 system engineering.
It allows the exchange of configuration information between engineering tools and IEDs.
Important SCL file types include:
- ICD – IED Capability Description.
- CID – Configured IED Description.
- IID – Instantiated IED Description.
- SCD – Substation Configuration Description.
- SSD – System Specification Description.
Typical engineering workflow
Step 1 – Obtain device descriptions
Collect the appropriate SCL files from the Merging Unit and protection IED manufacturers.
Check the supported IEC 61850 edition and device capabilities.
Step 2 – Create the system configuration
Import the available IED descriptions into the system engineering environment.
Create the required IED instances and communication architecture.
Step 3 – Define the Sampled Values dataset
Select the required measurement data objects and attributes.
The dataset must match the receiving IED’s requirements.
Step 4 – Configure the SV control block
Define the SV stream parameters, including the required identifiers and communication settings.
Step 5 – Configure the subscriber
Assign the appropriate external references to the receiving IED.
Verify that the subscriber’s measurement inputs correspond to the intended publisher dataset.
Step 6 – Validate the SCL configuration
Check references, communication parameters and device compatibility.
Step 7 – Deploy the configuration
Download or apply the configuration using the supported engineering procedure for each device.
Important distinction
SCL configuration is not the same as relay protection setting configuration.
For example, selecting a current measurement source through an IEC 61850 process bus does not automatically configure the overcurrent protection pickup and time delay.
Both the communication engineering and protection settings must be completed and verified.
7. External References and Sampled Values Subscription
External references describe relationships between data published by one IED and information required by another IED.
In IEC 61850 SCL, ExtRef elements can be used to describe external signal references, including relevant communication subscriptions.
For a process bus system, the engineering task is to map the correct published measurement stream to the receiving protection application’s expected inputs.
Example
A feeder protection IED requires three phase current measurements.
The Merging Unit publishes a dataset containing:
- Phase A current.
- Phase B current.
- Phase C current.
- Other required measurement information.
The subscriber configuration must associate the correct published data with the receiving device’s expected inputs.
An incorrect mapping may result in:
- Wrong phase measurements.
- Missing current channels.
- Incorrect scaling.
- Protection function malfunction.
- Incorrect disturbance records.
Always verify the actual data model and subscription implementation supported by the devices.
8. GOOSE Communication in the Process Bus
GOOSE is commonly used alongside Sampled Values.
While SV carries sampled current and voltage measurements, GOOSE can carry event-driven signals such as:
- Circuit-breaker position.
- Disconnector position.
- Protection trip.
- Interlocking status.
- Blocking signals.
- Breaker failure initiation.
- Other binary or application data.
Example: Feeder trip application
Consider a feeder protection IED receiving current measurements through SV.
If the protection detects a fault, it can issue a trip command.
Depending on the project design, the trip command may be:
- Sent through a GOOSE message to a compatible bay control or output device.
- Sent through a conventional binary output to the trip coil.
- Implemented through another approved protection interface.
The trip path must be carefully engineered and tested.
SV and GOOSE comparison
| Feature | Sampled Values | GOOSE |
|---|---|---|
| Purpose | Measurement transmission | Event and status transmission |
| Typical information | Current and voltage samples | Trip, block and status signals |
| Transmission | Periodic | Event-driven with retransmissions |
| Publisher | Merging Unit or other supported source | Protection or control IED |
| Subscriber | Compatible measurement-processing IED | Compatible protection or control IED |
| Ethernet communication | Yes | Yes |
9. Process Bus Network Design
The Ethernet network must be designed to carry real-time process bus traffic reliably.
Important design considerations include:
9.1 Network bandwidth
The designer must calculate the expected traffic from all Sampled Values streams and other Ethernet communication.
Consider:
- Number of Merging Units.
- Number of SV streams.
- Sampling rate.
- Number of ASDUs per frame.
- Ethernet frame overhead.
- GOOSE traffic.
- MMS traffic.
- Engineering and management traffic.
Do not estimate network capacity based only on the number of devices.
9.2 Multicast configuration
Sampled Values and GOOSE commonly use multicast Ethernet transmission.
Switches must be configured to forward the required traffic correctly.
Incorrect multicast handling can result in missing data or unnecessary network loading.
9.3 VLAN configuration
VLANs can separate different types of traffic.
For example:
| VLAN | Purpose |
|---|---|
| 100 | Sampled Values |
| 110 | GOOSE |
| 120 | Station-level communication |
| 130 | Engineering and management |
These are example values only.
The actual arrangement must follow the project network design.
9.4 Quality of Service
QoS allows network traffic to be prioritized.
The project should define how SV and GOOSE traffic are handled by the switches.
The selected priority values must be consistent with the network design and equipment capabilities.
9.5 Redundancy
A process bus may use PRP or HSR where supported.
The design must account for:
- Merging Unit compatibility.
- Protection IED compatibility.
- Switch support.
- RedBox requirements.
- Network topology.
- Failure behavior.
- Redundancy supervision.
Do not assume that all MiCOM relays or Merging Units support native PRP or HSR.
10. Time Synchronization and Sample Alignment
Accurate synchronization is fundamental to process bus engineering.
A typical arrangement uses a grandmaster clock distributing PTP synchronization to the relevant devices.
Main synchronization checks
- Confirm the selected PTP profile.
- Verify the grandmaster clock.
- Check network synchronization configuration.
- Verify Merging Unit synchronization.
- Confirm sample synchronization quality.
- Monitor synchronization alarms.
- Test loss and recovery of synchronization.
Why sample alignment matters
Some protection functions compare electrical measurements from different locations.
For example, differential protection compares currents entering and leaving a protected zone.
The measurements must have the required timing relationship.
A synchronization error can affect the accuracy of the protection calculation.
The acceptable synchronization performance must be established from the relevant equipment specifications and protection application requirements.
11. Process Bus Applications in Protection Systems
Process bus technology can support several protection applications, provided all participating devices support the required communication and processing functions.
11.1 Feeder protection
A compatible feeder relay can receive current and voltage measurements through SV.
Potential protection functions include:
- Phase overcurrent.
- Earth-fault protection.
- Directional overcurrent.
- Undervoltage.
- Overvoltage.
- Frequency protection.
The actual supported functions depend on the relay model and configuration.
11.2 Transformer differential protection
Transformer differential protection may use current measurements from Merging Units at different transformer terminals.
The protection system compares the currents after applying the required ratio and vector-group compensation.
Correct synchronization, scaling and channel mapping are essential.
11.3 Busbar protection
Busbar protection requires current measurements from multiple bays.
A digital process bus can provide these measurements through multiple Merging Units.
The protection system must ensure correct measurement assignment, current direction, synchronization and zone selection.
11.4 Line differential protection
Line differential protection compares current measurements at different line terminals.
Where a process bus is used, the architecture must account for both local process bus communication and the communication channel between line terminals.
The complete protection design must consider channel latency, synchronization and communication failure behavior.
Important: These are process bus application examples, not claims that every MiCOM relay supports SV-based versions of these functions.
12. Practical Example: Integrating a Merging Unit with a Feeder Protection System
Consider a 33 kV feeder with:
- One set of three-phase CTs.
- One set of three-phase VTs.
- One Merging Unit.
- One compatible protection IED.
- One Ethernet switch.
- One PTP grandmaster clock.
The objective is to provide digital current and voltage measurements to the protection system.
Step 1 – Review the protection design
Identify:
- CT ratios.
- VT ratios.
- Required protection functions.
- Required measurement channels.
- Sampling profile.
- Communication availability requirements.
Step 2 – Review device capabilities
Check the Merging Unit and protection IED documentation.
Confirm that the devices support compatible SV profiles.
Step 3 – Configure the Merging Unit
Configure the analogue channels and verify the measurement scaling.
Set the required sampling and synchronization parameters.
Step 4 – Configure the Ethernet network
Configure the switch ports, VLANs, multicast forwarding and QoS according to the approved design.
Step 5 – Configure the SV stream
Define the publisher dataset and SV control block.
Verify the APPID, svID, multicast address and other required parameters.
Step 6 – Configure the protection IED
Configure the receiving IED using its supported engineering procedure.
Map the incoming SV data to the correct measurement inputs.
Step 7 – Test the measurements
Use suitable test equipment to verify:
- Phase A current.
- Phase B current.
- Phase C current.
- Voltage measurements.
- Phase sequence.
- Scaling.
- Sample counter.
- Synchronization status.
Step 8 – Test the protection functions
Perform the relevant protection tests using an approved process bus testing arrangement.
Verify the complete trip chain, including any GOOSE or hardwired output interface.
13. Process Bus Testing with Omicron Test Equipment
Process bus testing requires equipment capable of working with the relevant digital communication standards and test architecture.
For example, suitable Omicron CMC configurations and compatible process bus testing options can be used to support digital testing workflows.
The exact hardware, software options and test configuration depend on the equipment and application.
Typical test activities
- SV stream verification.
- Measurement injection.
- Phase sequence verification.
- Current and voltage scaling checks.
- Protection pickup testing.
- Protection timing tests.
- GOOSE input and output testing.
- Communication failure simulation.
- Synchronization testing.
- End-to-end protection verification.
Important commissioning principle
A successful Sampled Values packet capture is not sufficient proof of correct protection operation.
The engineer must also confirm that:
- The correct SV stream is received.
- The measurements are interpreted correctly.
- The protection functions operate correctly.
- The intended trip output is produced.
- The system responds correctly to communication failure.
14. Wireshark Analysis for Process Bus Communication
Wireshark is an important tool for analyzing IEC 61850 Ethernet traffic.
It can be used to investigate Sampled Values, GOOSE and other network communication.
Useful display filters
Sampled Values:
sv
GOOSE:
goose
GOOSE EtherType:
eth.type == 0x88b8
VLAN traffic:
vlan
MMS communication:
tcp.port == 102
What should be checked?
For Sampled Values:
- svID.
- APPID.
- Sample counter.
- Multicast address.
- Dataset information.
- VLAN configuration.
- Missing or irregular frames.
For GOOSE:
- gocbRef.
- datSet.
- stNum.
- sqNum.
- timeAllowedToLive.
- confRev.
- Dataset values.
For MMS:
- TCP connection.
- Client-server association.
- Reports.
- Data access.
- Controls.
The capture method must be suitable for the network architecture. A capture on one switch port may not reveal all multicast traffic or both paths of a redundant network.
15. Loss of Sampled Values and Protection Response
One of the most important process bus engineering tasks is defining the protection system’s response to communication failure.
Consider a protection relay that receives current measurements through SV.
If the stream disappears, the relay may no longer have valid measurement information for the associated protection functions.
Possible system responses include:
- SV communication alarm.
- Measurement quality alarm.
- Blocking selected protection functions.
- Transfer to an alternative measurement source.
- Initiation of an engineered fallback strategy.
The correct response depends on the protection design and equipment capabilities.
Important questions for the protection engineer
- How quickly is loss of SV detected?
- Which protection functions are affected?
- Does the relay block affected functions?
- Is an alternative measurement source available?
- Is there an alarm to SCADA?
- How does the system recover after communication restoration?
- Is the response documented and tested?
These questions must be answered before the system is placed into service.
16. Common Process Bus Problems and Troubleshooting
| Problem | Possible cause | Recommended action |
|---|---|---|
| No SV reception | Incorrect stream configuration | Verify APPID, svID and multicast parameters |
| Protection relay does not support SV | Hardware or firmware limitation | Verify exact relay capability |
| Incorrect current values | CT ratio or scaling error | Check CT and Merging Unit configuration |
| Incorrect phase sequence | Channel mapping or wiring error | Verify phase identification |
| Missing SV frames | Network or multicast problem | Check switch configuration and packet capture |
| Synchronization alarm | PTP configuration or clock failure | Verify grandmaster and device synchronization |
| GOOSE signals unavailable | Incorrect dataset or subscription | Check publisher and subscriber configuration |
| Protection operates incorrectly | Measurement mapping or settings problem | Check the complete protection signal chain |
| Excessive network traffic | Incorrect multicast forwarding or capacity planning | Analyze switch statistics and network traffic |
| Communication fails after restart | Configuration or startup issue | Check device initialization and recovery sequence |
17. Cybersecurity Considerations
The process bus carries real-time information used by protection and control systems.
Cybersecurity must therefore be incorporated into the design.
Recommended practices include:
- Restrict access to process bus switches.
- Separate engineering access from protection communication where appropriate.
- Use managed switches.
- Disable unused ports.
- Maintain configuration backups.
- Control engineering workstation access.
- Monitor unexpected network traffic.
- Protect SCL files and device configuration.
- Control remote access.
- Apply approved firmware management procedures.
Security controls must be validated to ensure that they do not compromise the real-time performance or interoperability of the process bus.
18. Process Bus Commissioning Checklist
System engineering
- Review the approved process bus architecture.
- Confirm the Merging Unit model and firmware.
- Confirm protection IED SV compatibility.
- Verify the supported IEC 61850 edition.
- Review ICD and other relevant SCL files.
- Confirm datasets and control blocks.
- Validate external references.
Merging Unit
- Check CT and VT wiring.
- Verify ratios and scaling.
- Confirm phase identification.
- Check sampling profile.
- Verify SV publication.
- Check synchronization.
Ethernet network
- Verify switch configuration.
- Check VLAN membership.
- Confirm multicast forwarding.
- Verify QoS.
- Check network bandwidth.
- Test redundancy, where applicable.
- Save switch configuration backups.
Protection IED
- Verify SV subscription.
- Check incoming measurements.
- Confirm phase sequence.
- Verify sample counter behavior.
- Test loss-of-SV supervision.
- Verify recovery after restoration.
- Check relevant protection functions.
Complete system
- Test GOOSE communication.
- Verify trip logic.
- Test circuit-breaker interface.
- Verify SCADA indications.
- Check event and disturbance records.
- Complete communication failure tests.
- Record all commissioning results.
19. Conclusion
Process bus engineering is a major part of modern IEC 61850 digital substations.
By integrating Merging Units, Sampled Values, GOOSE communication, Ethernet networks and time synchronization, engineers can implement digital interfaces between primary equipment and protection systems.
However, a successful process bus installation requires much more than establishing Ethernet connectivity.
The complete system must be engineered around compatible devices, correct SCL configuration, accurate measurement scaling, reliable synchronization, suitable network design and carefully tested protection responses.
For MiCOM protection systems, the first step is always to verify the exact model’s support for the required IEC 61850 services. MMS and GOOSE support must not be confused with Sampled Values reception capability.
Practical IEC 61850 and MiCOM Training by Dr Saeed Roostaee – Elec-Engg
Elec-Engg provides practical training for protection, commissioning and substation automation engineers.
Relevant training subjects include:
- MiCOM protection relay configuration.
- IEC 61850 MMS and GOOSE.
- Sampled Values and process bus engineering.
- Merging Unit integration.
- SCL configuration and system engineering.
- Ethernet switches and VLAN configuration.
- Wireshark communication analysis.
- Omicron testing and commissioning.
- Digital substation protection applications.
- Communication troubleshooting.
Training is available through video courses, structured self-paced training, face-to-face courses and customized in-house programs.
Visit Elec-Engg for practical power system protection and substation automation training.
