1450 originalSclXxx computation rules
- Created
- 13 Oct 2015
- 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
- #1485 Need to supercede Tissue 1398 to clarify SCT behavior, #1398 originalSclVersion management in SCT
- Page
- 61
- Clause
- 9.3.2
- Paragraph
- Category
- Issue may impact interoperability of implementations of Edition 2
Issue
Tissue #1398 give the possibility for an SCT to manage originalSclVersion, originalSclRevision and originalSclRelease.
To enhance usage of these attributes and to manage mixity with edition 1, we have to enforce their usage during SCL exchanges.
Proposal
1/ ICT (Ed. 2 or later) SHALL set originalSclXxx attributes
2/ SCT SHALL set originalSclXxx attributes on importing an IxD file without originalSclXxx attributes according to the version of the SCL file
3/ Add rule that for an IxD file, the originalSclXxx values shall match the SCL version/revision/release
| Discussion | Created |
|---|---|
|
In Force (green)
Principally accepted.
Text modified as follows: These attributes shall be set by the IED tool when creating the ICD / IID file according to the SCL version / revision of the created file, and exported by the system configuration tool within an SCD file for each IED created from the appropriate ICD/IID file as imported. Syntactically both attributes stay optional but get the default values "2003" for the version and "A" for the revision. |
08 Dec 15 |
| Ballot Period | 24 Nov 15 |
|
Ballot Period
In principle accepted. Text modified as follows:
These attributes shall be set by the IED tool when creating the ICD / IID file according to the SCL version / revision of the created file, and exported by the system configuration tool within an SCD file for each IED created from the appropriate ICD/IID file. Syntactically both attributes stay optional but get the default values "2003" for the version and "A" for the revision. |
11 Nov 15 |