2028 No way to express Numerical Scaling Factor (Matching Factor) for PDIF
- Created
- 04 Feb 2026
- Status
- Approval (Future Improvement)Show the workflow
- Part
- Part 7-4 (2020; Edition 2.1)
- Links
- None
- Page
- 168
- Clause
- 6.11.2
- Paragraph
- Table 103
Issue
Missing data to express the Numerical Matching/Scaling Factor used by PDIF when protecting a power transformer.
Current editions do not provide a standard DO that reveals how PDIF performs magnitude matching of currents from different windings. While YPTR includes nameplate voltages (e.g., HiVRtg, LoVRtg), it does not indicate the effective factor applied by the PDIF function.
This limits interoperability and hinders verification and testing of protection settings.
Proposal
Add an optional Data Object to PDIF.
Suggested Name: IMtc (Current Matching Factor)
CDC: ASG (Analogue Setting)
Semantics: Scalar multiplier applied by the PDIF instance to one side’s input current(s) to achieve magnitude matching across windings when the protected zone includes a power transformer.
Presence condition: C; present only when PDIF is applied to a power transformer zone.
| Discussion | Created |
|---|---|
| Approval (Future Improvement) set state to "future improvement" | 28 May 26 |
|
Discussion (red)
I agree. I would propose to change the state to "approval (future improvement)".
Additionally, I would like to review PDIF and its use cases in general. Currently, PDIF is implemented and applied in a rather generic manner. This should be discussed within WG10 and addressed accordingly in my opinion. |
21 Apr 26 |
|
Discussion (red)
To my knowledge, there is no mechanism implemented in an existing product that would currently cause an interoperability issue.
My wording in the original tissue might be confusing in that respect. I meant to say that due to lack of being able to express this inside the SCL file in a standardised way, it may hinder future interoperability, as it leaves room for ambiguity on how to define or configure it in different products Therefore I would classify it as a future improvement (i.e. new feature) |
05 Apr 26 |
| Discussion (red) Is this an interop tissue of a future improvement tissue? | 02 Apr 26 |
| Discussion (red) open for discussion | 04 Feb 26 |
| Accepted changed state to accepted | 04 Feb 26 |