Project

General

Profile

WG10 Future Work #6265

track changes in SCL to know when a device needs to be updated based on new SCD version

Added by Camille Bloch over 1 year ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
02/14/2023
Due date:
% Done:

0%

Estimated time:
Source:
TF Unique ID:
WG10 Proposal:
Discuss in Upcoming Meeting:
No
Short Proposal:
Standard(s):

IEC 61850-6

Needs More Information:
No
Assigned TF:
61850-6
Target edition:
Next

Description

Following discussion in Kansas City about the usage of ConfRev for gooses, it has been clearly identified that ConfRev is an indicator for runtime about change which may have an impact on the runtime but without other way to identify it. This is way today, ConfRev is limited to Dataset update tracking.

Regarding the engineering of the system, this is not enough to identify when a device needs to be updated after a new version of the SCD.

We need for example to know each time a communication parameter of a goose has change imply the reconfiguration of the subscribers of the goose message.

As ConfRev is related to runtime, we need an additional mechanism.

A proposal has been done in 2017 which was never implemented in SCL. We need to review it and integrate the link with the new SCL version tracking bring with Ed2 AMD 2

Files

ChangeTrackingInSclV4.pptx ChangeTrackingInSclV4.pptx 324 KB Proposal for SCL changes tracking done in 2017 Camille Bloch, 02/14/2023 09:03 AM

Also available in: Atom PDF