Project

General

Profile

Improvement #5322

Schedules - add optional data objects to support irregular interval schedules

Added by Tom Berry 11 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Category:
Standard clarification required
Start date:
03/02/2022
Due date:
09/02/2022 (about 5 months late)
% Done:

100%

Estimated time:
ID:
2
Source:
WG17
TF Unique ID:
2 # WG17
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:
Standard(s):

IEC 61850-7-4,7-5

Needs More Information:

Description

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

Schedules may be used as means of providing setpoint values in advance of the desired time, for example for active power limiting. In such cases, regular time intervals are not always appropriate, especially under emergency conditions.

It is possible to model an irregular schedule with a set of FSCH logical nodes, each of which has an appropriate start time, but only one value.

It would be more efficient to allow a schedule to define a series of { time intervals, values }


Proposal descriptions

After discussion in the group - general conclusion is that there is a need of additional examples (to be defined in 7-500) that will explain all possible usage of existing Scheduling mechanisms.
If these exercises introduce a need for a extension/change - it will be discussed in 7-500 TF.
Examples from WG17 could be used as a use-cases.

#1

Updated by Tom Berry 11 months ago

  • Standard(s) set to IEC 61850-7-4,7-5
#2

Updated by Carlos Rodriguez del Castillo 11 months ago

  • Due date set to 09/02/2022
  • Category set to Standard extension required
  • Status changed from New to Triage
  • ID set to 2
  • TF Unique ID set to 2 # WG17
#3

Updated by Carlos Rodriguez del Castillo 11 months ago

We need more information due to the complexity of the issue.

#4

Updated by Tom Berry 10 months ago

For example, a single schedule where the time intervals are different

NumEntr = 5
Time1 = 01:00 ValING1 = 1000
Time2 = 06:25 ValING2 = 800
Time3 = 09:05 ValING3 = 700
Time4 = 12:20 ValING4 = 500
Time5 = 13:00 ValING5 = 1000

To do this with the present model requires 5 instances of FSCH

#5

Updated by Vladan Cvejic 10 months ago

  • Category changed from Standard extension required to Standard clarification required
  • Status changed from Triage to Resolved
  • % Done changed from 0 to 100
  • Proposal descriptions updated (diff)
#6

Updated by Vladan Cvejic 10 months ago

  • Proposal descriptions updated (diff)
#7

Updated by Tom Berry 4 months ago

Discussed in WG10 Meeting September 2022

WG17 to provide example of using multiple schedules for inclusion in part 7-5
This technique means an IED could have 100s of schedules - it may be appropriate to propose a naming convention and/or a means of using nested logical devices.

Also available in: Atom PDF