857 Function/SubFunction for ConductingEquipment
- Created
- 24 Jun 2012
- Status
- In Force (green)Closed: the solution is part of the standard. No further comments are taken. Show the workflow
- Part
- Part 6 (2009-12; Edition 2)
- Links
- None
- Page
- 49
- Clause
- 9.2.4
- Paragraph
- Category
- Issue may impact interoperability of implementations of Edition 2
Issue
Functional naming implies that there are no two logical node references (LNode) of the same LN class at any level within the Substation section. This was one of the reasons for introducing the Function/SubFunction elements.
However, these are not available for ConductingEquipment (nor for GeneralEquipment). This makes it impossible, for instance, to model redundant controlers (e.g., CSWI).
(Topic discussed during the WG10 meeting in Berlin.)
Proposal
Add a Function to tConductingEquipment ant tGeneralEquipment similar to Bay, VoltageLevel or Substation. However, the Function of a ConductingEquipment (or GeneralEquipment) shall differ from the Bay/Function in that it shall not allow to include other ConductingEquipments in order to avoid nested ConductingEquipments (or ConductingEquipments in GeneralEquipments).
| Discussion | Created |
|---|---|
| In Force (green) | 24 Sep 12 |
| Discussion (red) Accepted. This special Function element shall also be allowed at PowerTransformer, TransformerWinding and TapChanger elements | 25 Jun 12 |
|
Triage
Note: the "special" Function for tConductingEquipment ant tGeneralEquipment also requires a "special" SubFunction containing no child ConductingEquipment. This tissue also applies to tSubEquipment. |
24 Jun 12 |