- 1. Introduction
- 2. Why Data Quality Matters in Protection Systems
- 3. IEC 61850 Data Attribute Structure
- 4. Understanding the IEC 61850 Quality Attribute q
- 5. Important Quality Indicators Explained
- 6. Source Information and Quality Interpretation
- 7. Practical Example: Circuit-Breaker Position Quality
- 8. Substituted Values in IEC 61850
- 9. IEC 61850 Timestamp Attribute t
- 10. Time Quality in IEC 61850
- 11. Time Synchronization in MiCOM Relays
- 12. Sequence-of-Events Processing
- 13. IEC 61850 Reporting and Quality Changes
- 14. Mapping IEC 61850 Quality into SCADA
- 15. Practical Example: MiCOM Feeder Relay and SICAM PAS
- 16. Testing Quality and Timestamp Information
- 17. Common Quality and Timestamp Problems
- 18. Wireshark and IEC 61850 Troubleshooting
- 19. Best Practices for MiCOM Quality and Timestamp Engineering
- 20. Practical Commissioning Checklist
- 21. Conclusion
- 22. Practical MiCOM and IEC 61850 Training by Elec-Engg
1. Introduction
In an IEC 61850-based substation automation system, receiving a numerical value or status indication is not enough. Engineers must also understand whether the information is valid, whether it is current, where it originated and when the event occurred.
For example, a MiCOM protection relay may send a circuit-breaker status indicating that the breaker is closed. However, if the quality information indicates that the value is invalid, the SCADA system must not display it as a confirmed closed condition.
Similarly, a protection trip event may be received by the station controller several milliseconds after it occurred. The SCADA system should preserve the source timestamp where available rather than automatically using the message reception time.
IEC 61850 provides data attributes and quality information to support reliable monitoring and event processing.
This article explains:
- IEC 61850 data quality.
- The
qquality attribute. - The
ttimestamp attribute. - Validity and detail-quality indicators.
- Substituted and test values.
- Time synchronization in MiCOM relays.
- Sequence-of-events processing.
- SCADA quality mapping.
- Practical troubleshooting and commissioning.
Important: The availability, resolution and behavior of quality and timestamp information depend on the exact MiCOM relay model, firmware, communication implementation and configured data objects. Always verify the relevant MICS, PICS, PIXIT, ICD file and technical documentation.
2. Why Data Quality Matters in Protection Systems
Consider a feeder protection relay connected to a station SCADA system.
The relay provides:
- Circuit-breaker position.
- Protection trip status.
- Relay health.
- Phase currents.
- Voltage measurements.
- Frequency.
- Protection alarm indications.
The SCADA system receives these values through IEC 61850 MMS reporting.
If the communication system fails, the last received value may remain in the SCADA database.
For example, the last received breaker indication may be:
Breaker position = CLOSED
But if the communication connection has been lost, the SCADA system cannot necessarily confirm that the breaker is still closed.
Displaying the last value without an appropriate communication-quality indication could mislead the operator.
This is why data quality is essential.
A reliable SCADA system should distinguish between:
- A valid and current value.
- A valid value that has not recently changed.
- A questionable value.
- An invalid value.
- A substituted value.
- A value received under test conditions.
- A value that cannot currently be obtained because of communication failure.
3. IEC 61850 Data Attribute Structure
IEC 61850 data objects commonly use structured data attributes.
For example, a status data object may contain:
stVal: Status value.q: Quality.t: Timestamp.
A measurement object may contain:
mag: Magnitude.q: Quality.t: Timestamp.
The exact structure depends on the common data class (CDC) and the particular data object.
3.1 Status value
The stVal attribute represents the actual status value.
For example, a double-point status may distinguish between:
- Intermediate state.
- Off state.
- On state.
- Indeterminate state.
The interpretation depends on the CDC and data object.
3.2 Measurement value
Measurement data may be represented through attributes such as mag, depending on the common data class.
For example, a current measurement may be represented as a magnitude with an associated unit, multiplier and quality information.
3.3 Quality attribute
The q attribute describes the quality of the associated value.
It provides information that helps the receiving system determine whether the value can be trusted.
3.4 Timestamp attribute
The t attribute provides the timestamp associated with the value, where supported by the data object.
These attributes should be considered together when engineering SCADA data points.
4. Understanding the IEC 61850 Quality Attribute q
The IEC 61850 quality attribute is a structured value.
It contains information about validity and additional quality details.
The quality information is not simply a Boolean good/bad flag.
4.1 Validity
The validity field provides the main indication of data validity.
Common validity states include:
| Validity | General meaning |
|---|---|
| Good | The value is considered valid |
| Invalid | The value is not valid |
| Reserved | Reserved state |
| Questionable | The value may not be reliable |
The SCADA system should interpret these states according to the IEC 61850 quality definition and the project requirements.
4.2 Detail quality
The quality structure also contains additional indicators.
Common detail-quality indicators include:
oldDatafailureinconsistentinaccurateoverflowoutOfRangebadReferenceoscillatoryfailureoperatorBlockedsubstitutedtestsourceq.validity
These indicators provide more information about why a value may be questionable or how it was produced.
The exact interpretation must follow the IEC 61850 definition and the data object’s implementation.
5. Important Quality Indicators Explained
5.1 Good
Good indicates that the value is considered valid.
For example, a breaker position received from a healthy relay with valid status inputs may have good quality.
However, good quality does not mean that the value is necessarily correct from a physical engineering perspective. The input wiring, configuration and measurement chain must also be correct.
5.2 Invalid
Invalid indicates that the value must not be treated as valid.
Possible causes include:
- Failed input.
- Unavailable source information.
- Internal processing failure.
- Other device-specific invalidity conditions.
The SCADA system should clearly distinguish invalid information from normal operating states.
5.3 Questionable
Questionable indicates that the value may be unreliable.
It does not necessarily mean that the value is completely unusable, but the receiving application should treat it with appropriate caution.
5.4 Old data
The oldData indicator identifies information that is no longer considered current according to the applicable data-quality rules.
For example, a measurement may remain unchanged because its source has stopped updating.
The receiving system should not confuse an old value with a newly confirmed measurement.
5.5 Failure
The failure indicator provides information about a failure affecting the data.
The exact meaning depends on the associated data and device implementation.
5.6 Inconsistent
The inconsistent indicator can identify conflicting or inconsistent information.
For example, two related status signals may not agree.
In switchgear monitoring, inconsistent auxiliary contact information may require investigation.
5.7 Inaccurate
The inaccurate indicator identifies information that does not meet the required accuracy.
This is particularly relevant to measurements.
5.8 Overflow and out of range
These indicators are relevant when values exceed the expected representation or configured range.
For example, a measurement may exceed the range expected by the receiving application.
5.9 Operator blocked
The operatorBlocked indicator identifies a value or information source affected by an operator blocking condition, according to the applicable implementation.
5.10 Substituted
The substituted indicator identifies information that has been substituted rather than obtained directly from its normal source.
This is important because an operator or engineering process may temporarily replace a value for testing or operational purposes.
5.11 Test
The test indicator identifies information associated with test conditions.
Test values should not be confused with normal operational measurements or indications.
6. Source Information and Quality Interpretation
IEC 61850 quality information also includes a source indication.
The source can distinguish between information originating from a process and information originating from an internal or substituted source, depending on the applicable definition and implementation.
This is useful when investigating whether a value comes from:
- A physical input.
- An internal device calculation.
- A substituted value.
- A test arrangement.
Engineers should examine the complete quality structure rather than only checking the validity field.
7. Practical Example: Circuit-Breaker Position Quality
Consider a MiCOM relay monitoring a circuit-breaker position.
The relay receives auxiliary contact signals representing breaker open and closed states.
The data model provides a position status, together with quality and timestamp information.
A simplified conceptual example is:
| Attribute | Example |
|---|---|
| Data object | Breaker position |
| Status value | Closed |
| Quality | Good |
| Timestamp | Source event time |
The SCADA system displays:
Feeder CB: CLOSED
Now consider another situation:
| Attribute | Example |
|---|---|
| Data object | Breaker position |
| Status value | Closed |
| Quality | Invalid |
| Timestamp | Previously received event time |
In this case, the SCADA system should not present the breaker as confidently closed.
A suitable HMI presentation might show:
Feeder CB: CLOSED – INVALID QUALITY
The exact presentation depends on the SCADA design, but the principle is that the status value and quality must be interpreted together.
8. Substituted Values in IEC 61850
Substitution is used in some IEC 61850 implementations to replace a normal process value with an alternative value.
This may be useful during testing, simulation or certain maintenance activities.
For example, an engineer may need to test a SCADA application without operating the actual circuit breaker.
A substituted status may be used where the relay and its data model support this function.
8.1 Why substitution is important
Substitution can allow testing without changing the physical process.
However, it creates a potential risk if the receiving system does not recognize that the value has been substituted.
8.2 SCADA handling
The SCADA system should be designed to identify substituted information.
Operators should be able to distinguish between:
- Actual process status.
- Substituted status.
- Test information.
- Invalid information.
8.3 Engineering precautions
Before enabling substitution:
- Confirm that the relay supports the function.
- Identify the affected data objects.
- Understand how quality is updated.
- Inform relevant operational personnel.
- Apply approved maintenance and testing procedures.
- Restore the original source after testing.
- Verify the normal process value after restoration.
Substitution behavior is implementation-dependent and should not be assumed to be available for every MiCOM data object.
9. IEC 61850 Timestamp Attribute t
Timestamp information is essential for event analysis.
In IEC 61850, the timestamp is commonly represented using a structured time value.
It can include:
- Date.
- Time.
- Fractional seconds.
- Time-quality information.
The timestamp allows a receiving system to identify when a value was generated or updated.
9.1 Source timestamp versus reception timestamp
These are two different concepts.
Source timestamp
The time associated with the value at the source IED.
Reception timestamp
The time when the receiving system receives the communication message.
For event analysis, source timestamps are generally more useful because network delays can cause reception times to differ from the actual event times.
9.2 Example
Consider two MiCOM relays connected to the same station network.
Relay A records a protection trip at 10:15:30.120.
Relay B records a breaker status change at 10:15:30.145.
The SCADA system receives the two messages at:
- Relay A event: 10:15:30.180.
- Relay B event: 10:15:30.160.
If the SCADA system uses only reception timestamps, the apparent sequence may be incorrect.
If reliable source timestamps are available and correctly handled, the system can preserve the intended event chronology.
10. Time Quality in IEC 61850
IEC 61850 timestamps can contain information about the quality of the time value.
This is important because a timestamp is useful only if its accuracy and synchronization status are understood.
Time-quality information can indicate conditions such as:
- Clock failure.
- Clock not synchronized.
- Time accuracy information.
The precise interpretation follows the IEC 61850 timestamp definition.
10.1 Clock failure
A clock failure indication means the time source or clock function has experienced a failure condition.
10.2 Clock not synchronized
This indicates that the device clock is not synchronized to the required time reference.
An event timestamp may still be present, but the receiving application must consider its synchronization status.
10.3 Time accuracy
Time accuracy information describes the expected accuracy category of the timestamp.
This is important in applications where precise sequence-of-events analysis is required.
11. Time Synchronization in MiCOM Relays
A MiCOM relay may support one or more time synchronization methods, depending on the device model and communication hardware.
Common time synchronization methods in substation automation include:
- SNTP.
- PTP.
- IRIG-B.
- Other supported synchronization interfaces.
Not every MiCOM relay supports all these methods.
11.1 SNTP
Simple Network Time Protocol is commonly used to synchronize network-connected devices.
An SNTP-capable relay can obtain time information from a configured network time source.
Engineers should verify:
- Server address.
- Network connectivity.
- Synchronization status.
- Polling behavior.
- Time zone configuration.
- Firmware-specific limitations.
11.2 PTP
Precision Time Protocol can provide more precise synchronization in appropriately designed networks.
PTP support depends on the relay’s hardware and firmware.
The network switches and time source must also support the required PTP profile and architecture.
11.3 IRIG-B
IRIG-B is a time synchronization signal commonly used in protection and substation systems.
Where supported, it can provide time information through a dedicated synchronization interface.
The required signal format and electrical interface must be checked.
11.4 Selecting a time synchronization method
The correct method depends on:
- Required event timestamp accuracy.
- Relay hardware.
- Firmware capability.
- Existing substation time system.
- Network infrastructure.
- Project specification.
Do not assume that the presence of Ethernet communication means that a relay automatically supports PTP or receives synchronized time through MMS.
12. Sequence-of-Events Processing
Sequence-of-events (SOE) processing is essential for understanding protection operations and equipment behavior.
An SOE system records events with timestamps and organizes them chronologically.
Typical events include:
- Protection start.
- Protection trip.
- Circuit-breaker opening.
- Breaker failure initiation.
- Protection lockout.
- Disconnector operation.
- Alarm activation.
- Communication failure.
12.1 Example fault sequence
Consider a feeder fault.
A simplified event sequence may be:
| Time | Event |
|---|---|
| 10:15:30.100 | Overcurrent protection starts |
| 10:15:30.120 | Protection trip issued |
| 10:15:30.145 | Breaker open feedback received |
| 10:15:30.180 | SCADA alarm updated |
The actual timing depends on relay processing, protection settings, breaker operating time and communication behavior.
12.2 Why accurate SOE matters
Correct event chronology helps engineers investigate:
- Whether protection operated correctly.
- Whether the breaker opened within the expected time.
- Whether breaker failure logic was initiated correctly.
- Whether multiple protection devices operated.
- Whether communication delays affected event presentation.
12.3 SOE and disturbance records
SOE records and disturbance records provide complementary information.
SOE identifies the sequence of status and protection events.
Disturbance records provide waveform and analog information that helps engineers analyze the electrical fault.
Both are important in post-fault investigation.
13. IEC 61850 Reporting and Quality Changes
IEC 61850 reporting allows the IED to transmit data changes and other configured updates to the client.
For SCADA integration, quality changes are particularly important.
A measurement may not change numerically, but its quality may change.
For example:
- Current measurement = 120 A, quality good.
- Current measurement = 120 A, quality questionable.
The numerical value is unchanged, but the receiving system must recognize that the quality has changed.
13.1 Data-change reporting
Data-change reporting sends an update when the configured data value changes.
13.2 Quality-change reporting
Quality-change reporting allows the client to receive updates when the quality of the data changes, where supported.
13.3 Data-update reporting
Data-update reporting may be used to transmit updated information even when the value itself has not changed, according to the configured service behavior.
13.4 Integrity reporting
Integrity reporting periodically refreshes selected information.
This is useful for maintaining a consistent SCADA database.
The actual trigger options and reporting behavior must be verified for the particular MiCOM implementation.
14. Mapping IEC 61850 Quality into SCADA
A common engineering mistake is mapping only the process value and ignoring the quality attribute.
A complete SCADA point definition should consider both.
For example:
| IEC 61850 information | SCADA database purpose |
|---|---|
stVal | Breaker status |
q.validity | Main validity indication |
q.detailQuality | Additional quality details |
q.source | Source information |
t | Source timestamp |
The SCADA system may not expose every quality field separately to the operator, but it should preserve and interpret the information required by the application.
14.1 Recommended HMI presentation
A practical HMI may use the following presentation:
| Condition | Suggested HMI presentation |
|---|---|
| Valid and current | Normal status |
| Questionable | Warning or quality alarm |
| Invalid | Invalid data indication |
| Old data | Stale data indication |
| Substituted | Substituted value indication |
| Test | Test mode indication |
| Communication failure | Communication alarm |
The colors and symbols should follow the project’s HMI standards.
14.2 Communication failure versus invalid data
These conditions should not be confused.
A communication failure means the receiving system cannot currently obtain or confirm the information from the IED.
An invalid data quality indicates that the data source has identified the value as invalid.
A SCADA system may need to handle both conditions separately.
For example, a lost MMS association may cause the SCADA point to become communication-failed even though the last value received from the relay had good quality.
15. Practical Example: MiCOM Feeder Relay and SICAM PAS
Consider a medium-voltage feeder protected by a MiCOM relay and integrated into Siemens SICAM PAS.
The objective is to display breaker status, protection events and measurements with correct quality and timestamps.
15.1 Required information
The station system needs:
- Breaker position.
- Protection trip status.
- Phase currents.
- Earth-fault operation.
- Relay health.
- Measurement quality.
- Source timestamps.
15.2 Engineering steps
Step 1: Verify relay support
Check the exact relay model, firmware and supported IEC 61850 data objects.
Step 2: Identify the required attributes
For each required point, identify the value, quality and timestamp attributes where available.
Step 3: Configure reporting
Configure suitable datasets and Report Control Blocks for the required status and measurement information.
Step 4: Configure the SCADA database
Map the process value and relevant quality and timestamp information.
Step 5: Configure HMI handling
Define how the HMI presents questionable, invalid, substituted and stale information.
Step 6: Verify time synchronization
Confirm that the relay and station controller use the approved time source.
Step 7: Perform functional tests
Change selected statuses and measurements using an approved test arrangement.
Verify the value, quality and timestamp received by the SCADA system.
16. Testing Quality and Timestamp Information
Testing should cover normal operation and abnormal conditions.
16.1 Quality testing
Verify:
- Normal quality.
- Invalid quality, where testable.
- Questionable quality, where testable.
- Substituted values, where supported.
- Test indications, where supported.
- Quality-change reporting.
Not every quality state can be generated through normal relay operation. Some may require a controlled test configuration or simulation.
16.2 Timestamp testing
Verify:
- Relay date and time.
- Synchronization status.
- Timestamp updates.
- Source timestamp handling.
- SCADA timestamp interpretation.
- Event ordering.
- Time-quality information.
16.3 Communication interruption test
Under an approved test procedure:
- Establish normal MMS communication.
- Confirm the required points are updating.
- Interrupt communication.
- Observe the SCADA communication status.
- Confirm the handling of the last received values.
- Restore communication.
- Verify recovery and report behavior.
- Check whether events were buffered and recovered where supported.
16.4 Event sequence testing
Generate controlled test events and compare:
- Relay event records.
- IEC 61850 report timestamps.
- SCADA event records.
- HMI event chronology.
This helps identify time synchronization problems and event-processing delays.
17. Common Quality and Timestamp Problems
| Problem | Possible cause | Recommended investigation |
|---|---|---|
| SCADA displays stale status | Communication interruption | Check MMS association and point timeout |
| Value shown as invalid | Source quality indicates invalid | Inspect the quality structure |
| Measurement value is correct but questionable | Quality details indicate a problem | Check source and detail-quality flags |
| Event order is incorrect | Time synchronization issue | Compare relay and SCADA clocks |
| Timestamp differs from relay record | Reception time used instead of source time | Check timestamp mapping |
| Quality does not update | Report trigger or mapping problem | Check quality-change reporting |
| Substituted value not identified | Quality mapping incomplete | Check substitution indication |
| Events have inconsistent times | Different time sources or synchronization states | Review time architecture |
| Values remain after communication loss | SCADA retains last received value | Check stale-data handling |
| Event records are missing | Buffering or report recovery limitation | Check BRCB support and configuration |
18. Wireshark and IEC 61850 Troubleshooting
Wireshark can help identify communication issues associated with MMS reporting and GOOSE traffic.
Useful display filters include:
| Filter | Purpose |
|---|---|
tcp.port == 102 | MMS-related communication |
tcp.analysis.retransmission | TCP retransmissions |
tcp.flags.reset == 1 | TCP reset packets |
goose | GOOSE traffic |
eth.type == 0x88b8 | GOOSE EtherType |
For quality and timestamp investigations, engineers should inspect the decoded MMS reports using an appropriate IEC 61850 protocol decoder.
Check:
- Which data attributes are transmitted.
- Whether quality is included.
- Whether timestamps are included.
- Whether quality changes trigger reports.
- Whether the client receives the expected values.
- Whether report updates are delayed or missing.
A packet capture can confirm what was transmitted over the network, but it cannot independently prove that the source measurement or physical input is correct.
19. Best Practices for MiCOM Quality and Timestamp Engineering
The following practices help improve reliability:
- Include quality handling in the SCADA point list.
- Preserve source timestamps where supported.
- Avoid treating the last received value as automatically current.
- Distinguish communication failure from invalid source data.
- Display substituted and test values clearly.
- Verify time synchronization before commissioning SOE.
- Test quality-change reporting.
- Compare relay event records with SCADA events.
- Document time synchronization architecture.
- Verify all behavior against the actual MiCOM implementation.
20. Practical Commissioning Checklist
Data quality
- Confirm the quality attribute is available.
- Verify validity interpretation.
- Check detail-quality mapping.
- Verify source information.
- Check substituted-value handling.
- Check test-value handling.
- Confirm quality-change reporting.
Timestamp
- Verify relay date and time.
- Confirm synchronization method.
- Check synchronization status.
- Verify timestamp attributes.
- Confirm source timestamp mapping.
- Verify time-quality handling.
- Compare relay and SCADA event records.
SCADA
- Map process values.
- Map quality information.
- Map timestamps where available.
- Configure stale-data indication.
- Configure communication-failure alarms.
- Verify HMI presentation.
- Test communication interruption and recovery.
Final validation
- Test normal data updates.
- Test quality changes where possible.
- Test event chronology.
- Compare source and received timestamps.
- Record commissioning results.
- Save configuration backups.
21. Conclusion
IEC 61850 data quality and timestamp handling are essential for reliable substation automation.
For MiCOM protection relays, engineers should not consider only the numerical measurement or status value. They must also understand the quality attribute, timestamp information, source status and communication condition.
Correct handling of these elements improves:
- SCADA reliability.
- Alarm interpretation.
- Sequence-of-events analysis.
- Fault investigation.
- Protection event reconstruction.
- Operator confidence.
A properly engineered system distinguishes between a valid value, an invalid value, a substituted value and a value that is simply no longer being received.
22. Practical MiCOM and IEC 61850 Training by Elec-Engg
Elec-Engg provides practical training for protection, commissioning and substation automation engineers.
Relevant training topics include:
- MiCOM protection relay configuration.
- IEC 61850 data modeling.
- MMS communication and reporting.
- Quality attributes and timestamps.
- SNTP and time synchronization.
- GOOSE configuration and testing.
- SCADA integration with SICAM PAS.
- Sequence-of-events analysis.
- Wireshark-based communication troubleshooting.
- Practical relay testing and commissioning.
Training formats include video courses, structured self-paced training, face-to-face courses and customized in-house programs.
Practical courses by Dr Saeed Roostaee / Elec-Engg
Website: https://elec-engg.com/
