WG10 Future Work #5965: Schedules - allow updates to single values while schedules are running - IEC TC57 WG10 Future Work - UCAIug Issue Tracking System

WG10 Future Work #5965

Schedules - allow updates to single values while schedules are running

Added by Vladan Cvejic about 2 years ago. Updated 10 months ago.

Status:

New

Priority:

Normal

Assignee:

Start date:

03/02/2022

Due date:

09/02/2022 (over 2 years late)

% Done:

Estimated time:

Source:

TF Unique ID:

WG10 Proposal:

Discuss in Upcoming Meeting:

Short Proposal:

Standard(s):

IEC 61850-7-4

Needs More Information:

Assigned TF:

61850-7-4

Target edition:

Description

Context: how to use IEC 61850 for DER and microgrids (IEC 61850-90-23 CD1).

IEC 61850-7-4 prescribes that schedules may only be updated whilst they are offline. This is a conservative approach that allows for validation of all the settings to ensure consistency before re-starting i.e. evaluating the schedule output.
There are two approaches:
1. Stop the running schedule; change it, restart
2. Write to another schedule with a higher priority and start that; stop the original schedule; change it, restart it; stop the second schedule.

This approach is unnecessarily complex for some cases. A common use case is to update a schedule for one or more periods in the future. In these cases, updating individual schedule values will not affect the current schedule output, so there is no need to require the schedule to be deactivated and reactivated.

Updated by Vladan Cvejic about 2 years ago

Copied from Improvement #5323: Schedules - allow updates to single values while schedules are running added

Updated by Carlos Rodriguez del Castillo about 2 years ago

Discuss in Upcoming Meeting changed from Yes to No

Updated by Tom Berry about 2 years ago

Discussed in WG10 Meeting September 2022

The key issue is to clarify the consistency checks made when updating a FSCH.
The FSCH state machine is used to ensure that a schedule is consistent before it is enabled, but part 7-4 Annex K does not provide details of the checks that must / should be performed.

Tom Berry to write a proposal to describe expected checks for each data object.
For example, changing the number of points needs a full consistency check, changing a single ASG value does not.