865   Version, Revision and configVersion

Created: 11 Jul 2012

Status: Not Applicable

Part: Part 6 (2009-12; Edition 2)





Category: No impact on this part


I can´t see the real scope of the following attributes in IEC61850-6:
- Header section, “version” and “revision” attributes.
- IED section, “configVersion” attribute.

I can´t see in which cases these attributes should be changed. It´s not very clear for me.

For example, if an LN is added or removed, or if a CDC of a data is changed (from ORG to VSG), or if range of a parameter is changed, or if DataSets, RCBs or GCBs are changed... what of these values should be changed?

Every time “configVersion” changes, “version” and/or “revision” should be changed? This seems to be logical, because “version”/”revision” is the only tool to document a change in the History section, and that change can be just a change scoped by the “configVersion”.

Does “configVersion” only apply to changes within IED section? If so, what happens with changes in DataTypeTemplates section, which doesn´t affect to IED section because attributes which has changed are not instantiated in IED section? In that case, “version” and/or ”revision” should be changed, but no “configVersion”?

Could you please clarify this a little bit more?

Kind regards:



Discussion Created Status
configVersion refers to the version of an IED type. Its value and meaning is defined by the IED tool. One possible purpose could be to identify different preengineered versions of the same base IED type. If you have no preengineering, it might be superfluous, as all IED version information is covered by the LPHD.PhyNam and LLN0.NamPlt.
The Header identifes an SCL file as a document with a document identification (Header id), which in the context of an SCD file is additionally used as a project identification (see part 6 clause 10). Its version / revision must be used to identify different versions of the same SCL document, and is therefore managed by the tool producing the SCL (document) file. It is up to the tool (or the engineer using the tool) to decide what it considers to be a version, and what a revision. In general, adding or removing objects should lead to new versions, modifying data values or data flow to a new revision.
12 Jul 12 Not Applicable


Privacy | Contact | Disclaimer

Tissue DB v.