Project

General

Profile

Improvement #5321

Schedules - allow 3 values per time point

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

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

100%

Estimated time:
ID:
1
Source:
WG17
TF Unique ID:
1 # 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).

Several use cases require schedules or forecasts that have several values for each time point.
Examples include:
- Forecast quantities with nominal, lower bound and upper bound values
- Preferred (ideal) setpoint, minimum and maximum limits
- Operational function set point values and activation modes

Today this is only possible by using several FSCH logical nodes. This has the risk that communication failures may leave the set of FSCH nodes with inconsistent information.

This would also help with mapping to CIM based systems.


Proposal descriptions

The modelling has to be resolved before acting on #3098.

Additional discussion: We need new LN that will be a container for those date (necessary for scheduling).
Proposal: WG 17 to create detailed use-case document that will be commented/processed by 7-500 TF for further processing into 7-4 model.


Related issues

Related to IEC 61850 User Feedback Task Force - Improvement #3098: Need to Change 8-1 to allow multiple DOs to be writtenIn Progress08/08/202102/08/2022

Actions
#1

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 1
  • TF Unique ID set to 1 # WG17
  • Discuss in Upcoming Meeting changed from No to Yes

We see the problem on having communication issues on the schedule. We have to see how big is the extension because three could solve a specific problem, but we maight need more.
We need more information from use cases.

#2

Updated by Vladan Cvejic 10 months ago

  • Related to Improvement #3098: Need to Change 8-1 to allow multiple DOs to be written added
#3

Updated by Vladan Cvejic 10 months ago

  • Proposal descriptions updated (diff)
#4

Updated by Tom Berry 10 months ago

Three values is a compromise that matches the markets analysis in progress by WG16 and WG21 in the CIM

#5

Updated by Vladan Cvejic 10 months ago

  • 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 Vladan Cvejic 8 months ago

  • Discuss in Upcoming Meeting changed from Yes to No
#8

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